Chasingwindmills agile success
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Chasingwindmills agile success

on

  • 265 views

 

Statistics

Views

Total Views
265
Views on SlideShare
265
Embed Views
0

Actions

Likes
0
Downloads
5
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Chasingwindmills agile success Presentation Transcript

  • 1. Chasing Windmills? Getting Agile Success in Government Paul M. Boos
  • 2. Which do we see?
  • 3. Why should we care?
  • 4. Value
  • 5. Speed
  • 6. Why doesn’tthe Gov’tuse Agile?
  • 7. Ahhh… Software EngineeingWhat’s your Success Rate?
  • 8. 78% feel biz reqmts out of sync with project reqmts75% of Software Projects: DOOMED from Start ≅55% of projects have clear biz objectives Source: 2011 Geneca Survey
  • 9. % Application Features Used 7% 13% Rarely/Never Occasionally 16% Often 64% Always Only 20%!! Source: 2002 Standish Report
  • 10. Business Software is a Craft
  • 11. It takes skill… …and
  • 12. Creativity
  • 13. So… Certainly SOMEONE has created a better way
  • 14. Yep, some really, really, really Smart People gathered in Snowbird, Utah and created the …
  • 15. Manifesto for Agile Software DevelopmentWe are uncovering better ways of developing
software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration overcontract negotiation
Responding to change over following a planThat is, while there is value in the items on
the right, we
  • 16. Where does Agile fit? >Understanding Waterfall Of Problem Agile or Agile Agile and < < Understanding > Of Solution
  • 17. Challenges
  • 18. Bureaucracy?
  • 19. Gov’t OrganizationsTend to be here! (almost by sheer size) This model courtesy of Jurgen Appelo; please visit his blog at http://noop.nl
  • 20. Policy?
  • 21. Brings Order?
  • 22. Gov’t PoliciesTend to be here! (in theory) This model courtesy of Jurgen Appelo; please visit his blog at http://noop.nl
  • 23. Complexity orComplication?
  • 24. TeamsTend to be here! (in reality) This model courtesy of Jurgen Appelo; please visit his blog at http://noop.nl
  • 25. Complicated + Complex Overrides Ordered + Simple + =Process Team Result
  • 26. 12 Best Case3 …n Worse Case
  • 27. We don’t take timeto read (or write)our policies…
  • 28. We let others tell uswhat the policiesmean…
  • 29. What about…
  • 30. Systems Development Life-Cycle (SDLC)SimplifySimple Process = Easy AuditingFocus on Delivering Business ValueAlign Milestones w/Releasable Software
  • 31. Top Down Support Agile SuccessGrass Roots Motivation
  • 32. Strive to decomplicate…Help teams operate as simple and ordered as possible. This model courtesy of Jurgen Appelo; please visit his blog at http://noop.nl
  • 33. Perfection is achieved, not whenthere is nothing more to add, butwhen there is nothingleft to take away. -Antoine de Saint-Exupery
  • 34. Apply the pants principle…Simple process adopted by theteam doing the work. + Process Team
  • 35. “…reducing costs requires abetter way to organize work, notbetter cost information.” -H. Thomas Johnson (paraphrased)
  • 36. Hesitate Δingfor 1 problem
  • 37. Enterprise Architecture
  • 38. Graft and Prune EA Components
  • 39. The Iron Triangle Agilified
  • 40. An Approach for Executing Projects w/Agility Scope Prioritized Epics Scope Epic 1 Epic 2 Epic 3 Estimate Work to… Epic 4 Epic 5 …Budget Schedule > Budget Schedule Budget/Schedule + Mgmt Reserve
  • 41. Execute onsmall slices!
  • 42. Classic EVM Deploy$ Develop 01001101 11101000 10010010 Design Analyze
  • 43. Scrum ProcessRelease Plan Release
  • 44. Scrum-based EVM$ Release
  • 45. Manifesto for Agile Software DevelopmentWe are uncovering better ways of developing
software by doing it and helping others do it. Through this work we have come to value: those Reward building the Individuals and interactionsproduct in over processes and tools
Working software over comprehensive working documentation
Customer collaboration over together overcontract negotiation
Responding to change following a planThat is, while there is value in the items on
the right, we
  • 46. Manifesto for Agile Software DevelopmentWe are uncovering better ways of developing
software by doing it and helping others do it. Reward risk-taking/innovation; Through this work we have come to value: penalize only non-contained Individuals and interactions over processes failuresand tools
Working software over comprehensive documentation
Customer collaboration overcontract negotiation
Responding to change over following a planThat is, while there is value in the items on
the right, we
  • 47. Manifesto for Agile Software Development We are uncovering better ways of developing
software by doing it and helping others do it. Through this work we have come to value:Reward product meeting needs Individuals and interactions over processesover on-time/on-schedule comprehensive and tools
Working software over documentation
Customer collaboration overcontract negotiation
Responding to change over following a planThat is, while there is value in the items on
the right, we
  • 48. Manifesto for Agile Software Development We are uncovering better ways of developing
software by doing it and helping others do it.Reward working product to value: Through this work we have come Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration overcontract negotiation
Responding to change over following a planThat is, while there is value in the items on
the right, we
  • 49. Set a vision… and
  • 50. There’s nothingto fear.
  • 51. http://coactivate.org/projects/agile-influencers-of-dc Paul Boos @paul_boospaul.boos@santeon.com