Production Support and Scrum: How should Scrum teams plan for support?

by Geoff Watts | 8 Comments | 28 Mar 2008 | sprint planning, velocity, legacy code

Geoff_watts_avatar

Bugs and support issues don't always wait for a new sprint before rearing their ugly heads. What should a Scrum team do to balance feature development with support activities?

Continue Reading…

Keep Your Team Seeing RED

Nimesh-2008jan How focusing on Requirements gathering, estimation, and delivery (RED) can keep your project in the green.

Continue Reading…

Language for Discussing Releases

by Daniel C. LeFebvre | 4 Comments | 02 Apr 2007 | delivery, velocity, estimation

Dan_lefebvre_web "I'm taking off a letter grade because this wasn't turned in on the due date." "Don't be late!" Growing up, we quickly understand that being late is a bad thing. So when a project runs behind, we do whatever it takes to turn it around, even if those behaviors do more harm than good. Agile projects need a to discuss releases in a way that removes the guilt and focuses on appropriate action.

Continue Reading…

What's your sign? Find out what your burndown signature says about your team.

by Kane Mar | 2 Comments | 23 Oct 2006 | velocity, estimation, Scrum Artifacts

Profile Burndown graphs are commonly used in Scrum projects to give the team an understanding of the amount of work remaining for the Sprint (or iteration). In Ken's own words: “As a team works together, it develop its own style of creating ...

Continue Reading…