Document Controls
For Application Development Professionals
| Primary Analyst Photo | Document Information | Rate this Document |
|---|---|---|
|
August 23, 2004 Avoiding Scrum Pitfalls On Agile Development Projectsby Liz Barnett with Carey Schwaber |
|
This is an excerpt
Executive Summary
Agile processes offer development teams the ability to more quickly respond to customer requirements and collaborate to solve complex problems. Scrum, an Agile approach to managing software development projects, is one of the more popular Agile processes and is particularly focused on self-managed teams. Development teams that use Scrum are responsible for delivering working code that meets a set of customer requirements (the "product backlog") over the course of an iteration (a "Sprint"). Adopting Scrum — or any other Agile process — requires teams to significantly change the way they build software and work together. Organizations using Scrum must be prepared to address the nature of team interactions, the transition from legacy practices, and the development of new metrics.
This is an excerpt
Buy Risk-Free
Price: US $499
Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.
Already a Forrester Client?
Log in to read this document.
