Agile and continuous integration
Adopting Agile Development
Design vs Knowledge Creation: Attacking risk early along with early and continuous integration improves development.
Agile attitude: Transparency
Forget Burn-down, Use Burn-up charts: graph both total and completed, that way you can see when backlog was added or removed along with iteration velocity. It is then obvious why decreases in remaining occurred - whether due to backlog changes or velocity changes. I would recommend adding annotations with links to notes indicating what changed. What was added/removed to backlog? Were there less team members due to vacations, etc? Were team members shuffled?
Agile Anti-patterns
Design vs Knowledge Creation: Attacking risk early along with early and continuous integration improves development.
Agile attitude: Transparency
Forget Burn-down, Use Burn-up charts: graph both total and completed, that way you can see when backlog was added or removed along with iteration velocity. It is then obvious why decreases in remaining occurred - whether due to backlog changes or velocity changes. I would recommend adding annotations with links to notes indicating what changed. What was added/removed to backlog? Were there less team members due to vacations, etc? Were team members shuffled?
Agile Anti-patterns
Comments