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.

1. Code Enigma
Web services plus sweets

2. Post-agile project
development

3. We base our ISO
9001 certification
on Agile-scrum

4. What is Agile (scrum)

5. A philosophy

6. Work done by self-managing,
co-located teams in rapid
iterations

7. What is it in practice

8. Building an extension

9. We have some issues

10. Costs
●Specifications
●Role of design
●Delivery plans
●Ownership
●

11. Why is it popular?

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

14. The problems in practice

15. Lack of product ownership

16. Owner doesn't want to
Owner isn't allowed to
Owner doesn't know how to

17. Can't write stories
Can't say no or stop
Thinks an estimate is a
guarantee
Bad judge of business value

18. Prioritising
Lack of prioritisation
Means
A fixed specification

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

21. Sizing the work

22. Working out business value
expressed in user stories
sized in t-shirts

23. User story
As anon I can view videos from the previous
year's event so that I can judge the calibre of
presenters

24. Developer response

28. No BDUF?

29. Cross-disciplinary, colocated, self-managing teams

30. Our responses

31. Decide if the project is Agile

32. Business plan
Or
Specification

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

34. Product owner coaching and
mentoring

35. Communication plan
document all communications
avoid email
shared documentation

36. Project leader
The Real Owner

37. Project mentor
Client relationship manager

38. Time and task based
estimating

40. Detailed time-tracking

42. Analyze the time

47. Prototype designs

48. Change requests

49. Are we still Agile ?

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.