Agile Manifesto

using the SCRUM framework

AGILE DEVELOPMENT USING THE SCRUM FRAMEWORK:

https://www.dropbox.com/s/ya2up57kbfafdq6/purdie_burrows_agile%20application_scrum.pdf

MANIFESTO FOR AGILE SOFTWARE DEVELOPMENT

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

‣ Individuals and interactions over processes and tools

‣ Working software over comprehensive documentation

‣ Customer collaboration over contract negotiation

‣ Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

SCRUM IN 30 SECONDS

1. A product owner creates a prioritized wish list called a product backlog. During sprint planning, the team pulls a small chunk from the top of that wishlist, a sprint backlog, and decides how to implement those pieces.
2. The team has a certain amount of time, a sprint, to complete its work — usually two to four weeks — but meets each day to assess its progress (daily scrum).
3. Along the way, the ScrumMaster keeps the team focused on its goal.
4. At the end of the sprint, the work should be potentially shippable, as in ready to hand to a customer, put on a store shelf, or show to a stakeholder.
5. The sprint ends with a sprint review and retrospective.
6. As the next sprint begins, the team chooses another chunk of the product backlog and begins working again.