|
|
| Saturday, 04 September 2010 |
| Books for the Practicing Programmer |
Ken Schwaber, Mike Beedle
Agile Software Development with Scrum
2001 (Prentice Hall); 158 pages
A good description of scrum and how to apply it.
Under the scrum process, the product owner maintains a product backlog, a prioritized list of product requirements maintained. Development by the scrum team is broken into 30 day sprints. During the sprint, the team works off of a sprint backlog of tasks, which is taken from the highest-priority requirements in the product backlog. Each team member presents his/her status/needs at a daily scrum overseen by a scrum master, who is the primary interface between the technical team and business representatives. The sprint backlog may be modified during a sprint to reflect current reality. At the end of the sprint, the product increment is unveiled at a sprint review meeting.
The key to the success of scrum is the constant feedback which it gives to both programmers and the business client, both through incremental development and, on a more frequent scale, the daily scrums. This avoids the the surprises (late delivery, misunderstood business needs, changed requirements) which befall many traditional development products.
|
|