martes, 15 de noviembre de 2016

(some) Agile antipatterns

This is a list of (some) agile antipatterns, mostly around performance or velocity concepts:

Related with Burndown Chart:
  • The team finishes early sprint after sprint because they aren't committing to enough work. 
  • The team misses their forecast sprint after sprint becase they're committing to too much work. 
  • The burndown line makes steep drops rather than a more gradual burndown because the work hasn't been broken down into granular pieces.
  • The product owner adds or changes the scope mid-sprint.
Related with Velocity:
  • Are there unforeseen development challenges we didn't account for when estimating this work? How can we better break down work to uncover some of these challenges?
  • Is there outside business pressure pushing the team beyond its limits? Is adherance to development best practices suffering as a result?
  • As a team, are we overzealous in forecasting for the sprint

References


No hay comentarios:

Publicar un comentario