Being Agile

1,912 views

Published on

"Being Agile" presents an introduction to Scrum, an Agile software development methodology. In addition to the basics of the iterative development process and roles, this talk explores Agile concepts related to requirements, documentation, communication, planning, and overall business strategy.

Presented to Cedar Rapids IIBA 2/10/2010

Published in: Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,912
On SlideShare
0
From Embeds
0
Number of Embeds
18
Actions
Shares
0
Downloads
52
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Being Agile

  1. 1. being agile David Sturtz david@davidsturtz.com twitter: @sturtz
  2. 2. Hi. I’m David. Product Manager, Geonetric Information Architect / UX Designer Certified Scrum Master
  3. 3. Many denominations Agile Unified Process, Crystal, Dynamic Systems Development, Extreme Programming (XP), Feature Driven Development (FDD), Lean Software Development, Scrum, etc. I will generally be talking from a Scrum perspective.
  4. 4. Why Agile?
  5. 5. Waterfall… Requirements Design Implementation Verification Maintenance
  6. 6. …or other ‘methods’.
  7. 7. Q: Ought form to derive from the analysis of function? A: The great risk here is that the analysis may not be complete. — Charles Eames
  8. 8. Why Agile? Change is constant. Development is design. Human interactions. Collaboration. Inspect & adapt. Build quality in. Demonstrable value. Aligned with goals.
  9. 9. What is Agile? Project Management Process Leadership Philosophy Engineering Practices Business Approach Jon Strickler, Defining Agile Development
  10. 10. How will we get there? Agile is a project management process. Jon Strickler, Defining Agile Development
  11. 11. Resources Scope Quality Time
  12. 12. Resources Scope Quality Time
  13. 13. Team Backlog ‘Done’ Iteration
  14. 14. Team Backlog 2 weeks to 30 days ‘Done’ fixed goalpost Iteration
  15. 15. Scrum Stand-up 24 hours Product Backlog Sprint/Iteration 2 weeks to 30 days Sprint Potentially Backlog Shippable Increment Adapted from Mountain Goat Software
  16. 16. planning Team Backlog daily stand-up ‘Done’ review Iteration retrospective
  17. 17. The Scrum Board To Do ∂ In Progress ∂ Complete ∂ Accepted
  18. 18. The Burndown
  19. 19. Who is in charge? Agile is a leadership philosophy. Jon Strickler, Defining Agile Development
  20. 20. Team Backlog team members ‘Done’ scrum master product owner Iteration
  21. 21. 7±2 Team Backlog committed ‘Done’ co-located cross-functional Iteration self-organizing
  22. 22. Inspect and adapt “Agility might be said to be about encountering all the problems so early and so often that the e fort to fix them is less than the pain of enduring them.” — Ron Jeffries
  23. 23. When are we finished? Agile is a set of engineering best practices. Jon Strickler, Defining Agile Development
  24. 24. Team Backlog demonstrable value ‘Done’ definition of ‘done’ team owns quality Iteration
  25. 25. Slices, not layers
  26. 26. Done-done. “If we’re not shipping our software when it’s ready, it’s poor business practice. If we’re not sure whether our software is ready, it’s poor software practice.” — Ron Jeffries
  27. 27. What are your priorities? Agile is a business approach. Jon Strickler, Defining Agile Development
  28. 28. Team Backlog user stories ‘Done’ acceptance criteria prioritized Iteration
  29. 29. The User Story As a USER I want GOAL so that VALUE
  30. 30. Strategy Executive Years Team Portfolio Product Product Management Planning Release Months Iteration Development Team Daily Hours Adapted from Rich Mironov/Enthiosys Planing Time Horizons
  31. 31. Fail early, fail often. “By far the dominant reason for not releasing sooner was a reluctance to trade the dream of success for the reality of feedback.” — Kent Beck
  32. 32. Team Backlog ‘Done’ Iteration
  33. 33. What is Agile? Project Management Process Leadership Philosophy Engineering Practices Business Approach Jon Strickler, Defining Agile Development
  34. 34. What is Agile? “Simplicity does not precede complexity, but follows it.” — Alan Perlis
  35. 35. being agile David Sturtz david@davidsturtz.com twitter: @sturtz
  36. 36. Recommended Reading
  37. 37. Photo Credits Sekitei Garden by mrhayata Handful of Frogs at Coba by deanj http://www.flickr.com/photos/mrhayata/ http://www.flickr.com/photos/deanj/67607256/ 100841819/ Zen Gravel by Seldom Scene Photography 1/2 Kishu Roll by Geoff Peters 604 http://www.flickr.com/photos/old_dog_photo/ http://www.flickr.com/photos/gpeters/ 4227016718/ 3453508591/ Busy sprint by drewgstephens Zen garden - Ginkakuji by Stéfan http://www.flickr.com/photos/dinomite/ http://www.flickr.com/photos/st3f4n/ 3219513356/ 2750491245/ eames shell chair by back garage Cascade by vandelizer http://www.flickr.com/photos/ http://www.flickr.com/photos/jeremy_vandel/ back_garage/3650087649/ 208714007/ WikiData User Stories by psd http://www.flickr.com/photos/psd/3731275681/

×