Slides from a talk given at #drupalcampnw in Manchester on how to adapt Agile-scrum methodology to meet real-life challenges faced by agencies, particularly when using Drupal.
12. For customers
promises speed
cut out "peripheral" costs for discovery, design,
and testing
allows for change - flexible
client in charge
13. For suppliers
Feels like a good fit with Open Source – fluid,
transparent, organic collaboration
No paperwork is developer heaven
Provide time rather than deliverables
it's a methodology
19. No scope for iterating
The requirements are visible and
finite
The budget is fixed
20. Cost of 10 day sprints
1 x designer @ 500 = 5,000
2 x developer @ 5000 = 10,000
1 x scrum master @ 2,000
Total per sprint : 17,000
3 sprints : 51,000
33. Provide a clear, simple statement of the business
aim
Provide business objectives of how the
application benefits users and consequently the
client
Provide an MVP
Provide an agreed model for how we work and
communicate
Explain the testing model and the definition of
done
Identify the people in each role
Provide a basis for review of progress
50. The Agile manifesto
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
51. 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.
Editor's Notes
Implication that we've moved beyond Agile
Could have titled this Applying Agile in the real World
Implication that we've moved beyond Agile
Could have titled this Applying Agile in the real World