Code Enigma
Web services plus sweets
Post-agile project
development
We base our ISO
9001 certification
on Agile-scrum
What is Agile (scrum)
A philosophy
Work done by self-managing,
co-located teams in rapid
iterations
What is it in practice
Building an extension
We have some issues
Costs
●Specifications
●Role of design
●Delivery plans
●Ownership
●
Why is it popular?
For customers
promises speed
cut out "peripheral" costs for discovery, design,
and testing
allows for change - flexible
cl...
For suppliers
Feels like a good fit with Open Source – fluid,
transparent, organic collaboration
No paperwork is developer...
The problems in practice
Lack of product ownership
Owner doesn't want to
Owner isn't allowed to
Owner doesn't know how to
Can't write stories
Can't say no or stop
Thinks an estimate is a
guarantee
Bad judge of business value
Prioritising
Lack of prioritisation
Means
A fixed specification
No scope for iterating
The requirements are visible and
finite
The budget is fixed
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 ...
Sizing the work
Working out business value
expressed in user stories
sized in t-shirts
User story
As anon I can view videos from the previous
year's event so that I can judge the calibre of
presenters
Developer response
No BDUF?
Cross-disciplinary, colocated, self-managing teams
Our responses
Decide if the project is Agile
Business plan
Or
Specification
Provide a clear, simple statement of the business
aim
Provide business objectives of how the
application benefits users an...
Product owner coaching and
mentoring
Communication plan
document all communications
avoid email
shared documentation
Project leader
The Real Owner
Project mentor
Client relationship manager
Time and task based
estimating
Detailed time-tracking
Analyze the time
Prototype designs
Change requests
Are we still Agile ?
The Agile manifesto
We are uncovering better ways of developing
software by doing it and helping others do it.
Through thi...
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collabora...
Post agile project management
Post agile project management
Post agile project management
Post agile project management
Post agile project management
Post agile project management
Post agile project management
Post agile project management
Post agile project management
Upcoming SlideShare
Loading in …5
×

Post agile project management

770 views

Published on

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.

Published in: Design, Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
770
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
10
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • 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
  • Post agile project management

    1. 1. Code Enigma Web services plus sweets
    2. 2. Post-agile project development
    3. 3. We base our ISO 9001 certification on Agile-scrum
    4. 4. What is Agile (scrum)
    5. 5. A philosophy
    6. 6. Work done by self-managing, co-located teams in rapid iterations
    7. 7. What is it in practice
    8. 8. Building an extension
    9. 9. We have some issues
    10. 10. Costs ●Specifications ●Role of design ●Delivery plans ●Ownership ●
    11. 11. Why is it popular?
    12. 12. For customers promises speed cut out "peripheral" costs for discovery, design, and testing allows for change - flexible client in charge
    13. 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. 14. The problems in practice
    15. 15. Lack of product ownership
    16. 16. Owner doesn't want to Owner isn't allowed to Owner doesn't know how to
    17. 17. Can't write stories Can't say no or stop Thinks an estimate is a guarantee Bad judge of business value
    18. 18. Prioritising Lack of prioritisation Means A fixed specification
    19. 19. No scope for iterating The requirements are visible and finite The budget is fixed
    20. 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. 21. Sizing the work
    22. 22. Working out business value expressed in user stories sized in t-shirts
    23. 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. 24. Developer response
    25. 25. No BDUF?
    26. 26. Cross-disciplinary, colocated, self-managing teams
    27. 27. Our responses
    28. 28. Decide if the project is Agile
    29. 29. Business plan Or Specification
    30. 30. 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
    31. 31. Product owner coaching and mentoring
    32. 32. Communication plan document all communications avoid email shared documentation
    33. 33. Project leader The Real Owner
    34. 34. Project mentor Client relationship manager
    35. 35. Time and task based estimating
    36. 36. Detailed time-tracking
    37. 37. Analyze the time
    38. 38. Prototype designs
    39. 39. Change requests
    40. 40. Are we still Agile ?
    41. 41. 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:
    42. 42. 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.

    ×