anchor.diff:  # Agile methods and where (not) to find them
   
   Being Agile is popular these times. But what "being Agile" really mean for us, as software people?
  +More than that, are we actually acting accordingdly to the Agile principles?
  +
  +In this article we will try to understand and reflect about some of our day-to-day situations and analyse if we're doing it the Agile Way.
   
   ## Definitions, definitions...
   
  
positive.code: 
  So, let's look at them with a little more care.
  
  ### Individuals and iteractions
  
  This means we have to communicate and interact with other **people**. Yeah, people.
  
  
negative.code: 
  **Situation #3.** The Sprint ended up too big and the team is overworked with the features, you call the team and suggests to remove automatic testing from this last tasks so we can deliver on time. The team agrees and the sprint was a success, but on the next Sprint you couldn't convince everyone that the team should take less tasks this time. The team ended up developing lesser tests and, after 3 Sprints, the code starts brake at almost everywhere, so now you advise for a "Unit Testing Sprint", the problem is that the code created with no test has to be refactored and it should take at least 2 Sprints and the budget can't handle it. The team will have to do it in 1 Sprint only, making you call an internal "I told you!" and think on how awesome it would be if they listened to you for a change.
  
  Believe it or not... **You are not being Agile!**
  
  Everyone has to be concerned on having a stable software after every increment. Your good individual work means nothing if the product increment does not run. Fitting more features means nothing if the team has to neglect testing hoping the bugs doesn't get found by at the Sprint Review.
  
  