Agile Tour DC Chasing Windmills: Agile in the Government

1,287 views

Published on

This is the presentation for the Agile Tour DC Conference 22 October.

Published in: Technology, Business

Agile Tour DC Chasing Windmills: Agile in the Government

  1. 1. Chasing Windmills? Getting Agile Success in Government Paul M. Boos
  2. 3. Which do we see?
  3. 4. Why should we care?
  4. 5. Transparency
  5. 6. Speed
  6. 7. Value
  7. 8. Why doesn’t the Gov’t use Agile?
  8. 9. Software Engineering
  9. 10. Understanding
  10. 11. Perceived Barriers
  11. 12. Challenges
  12. 13. Bureaucracy?
  13. 14. Gov’t Organizations This model courtesy of Jurgen Appelo; please visit his blog at http://noop.nl Tend to be here! (sheer size)
  14. 15. Policy?
  15. 16. Brings Order?
  16. 17. Gov’t Policies This model courtesy of Jurgen Appelo; please visit his blog at http://noop.nl Tend to be here! (in theory)
  17. 18. Complexity or Complication?
  18. 19. Complicated + Complex Overrides Ordered + Simple + = Process Team Result
  19. 20. … 1 2 3 n Worse Case Best Case
  20. 21. We’re lazy…
  21. 22. We don’t take time to read (or write) our policies…
  22. 23. We let others tell us what the policies mean…
  23. 24. Some basics
  24. 26. Grass Roots Motivation Top Down Support Agile Success
  25. 27. Strive to decomplicate… This model courtesy of Jurgen Appelo; please visit his blog at http://noop.nl Help teams operate as simple and ordered as possible.
  26. 28. Apply the pants principle… Simple process adopted by the team doing the work. + Process Team
  27. 29. Hesitate Δ ing for one problem
  28. 30. What about… E A V M E B E D G U P R A S S D L C T
  29. 31. Simplify Simple Process = Easy Auditing Focus on Delivering Business Value Align Milestones w/Releasable Software Systems Development Life-Cycle (SDLC)
  30. 32. Enterprise Architecture
  31. 33. Graft and Prune EA Components
  32. 35. Estimate Scope Budget Work to… Schedule Scope Budget Schedule Prioritized Epics Epic 1 Epic 2 Epic 3 Epic 4 Epic 5 … Budget/Schedule + Mgmt Reserve > An Approach for Budgeting Agile Projects
  33. 36. Classic EVM Design Analyze Develop Deploy $ 01001101 11101000 10010010
  34. 38. Scrum Process Release Release Plan
  35. 39. Release $ Scrum-based EVM
  36. 40. Personnel Annual Review System
  37. 42. Advanced Wizardry
  38. 43. Clean the Windows! Demand and Give Transparency
  39. 44. Retrospect
  40. 45. Experiment!
  41. 46. Set a vision… and
  42. 47. help your teams see it!
  43. 48. Remove the blame culture It’s not the rebel alliance!
  44. 50. There’s nothing to fear.
  45. 51. Paul Boos @paul_boos [email_address] http://coactivate.org/projects/agile-influencers-of-dc

×