5 unspoken rules of Agile / SDLC

5 unspoken rules of Agile / SDLC

(some bullets taken from the agile manifesto)

  Never EVER ask for a scope increase. 
    
    - Increased scope can introduce errors to regressed software. 
    Commit to a topic or feature branch if you have spare time instead.
    
    - Remember, working software is the principal measure of progress
    
    - Keep it simple - the art of maximizing the amount of work not done 
    is essential.



  An app to the consumer, is only as good as the stories given to the developer

    
    - therefore an app is only as good as the product team behind it.


  When asked if you are optimistic about the release of a project, NEVER say yes.
    
    - If something can go wrong with the initial release, 
    it probably will.
    
    - Provide a humbling response instead. 

  
  Leave room for error with regard to intitial release dates
    
    - Working software is delivered frequently (weeks rather than months). 
    An extra week or two to sharpen the saw should be expected and welcomed.

  
  Avoid repetetive meetings 
    
    - some companies have a bad habit of taking something agile 
    and making it the complete opposite. as a developer, I
    hate repetition.  

    - attending the same meetings with the same conversations will 
    suck the motivation lifeblood from me, when I could be working 
    instead. speak up and change things before they change you.