1 / 20

Extreme Programming: Enhancing NGO Software Development

Explore Extreme Programming (XP) as a methodology for NGO software projects, focusing on small teams facing shifting requirements. Learn how XP principles tackle common software development risks and project variables, promoting agility and responsiveness. Discover how XP practices contribute to improved project outcomes within NGOs by emphasizing small releases, iterative development, and adaptability to change. Review the benefits of chunking down projects, using metaphors and stories, engaging in paired design and testing, and embracing continuous improvements through collective ownership and short feedback loops.

melvinavila
Download Presentation

Extreme Programming: Enhancing NGO Software Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Extreme Programming…chunking down, rubber ducking and waterfalls. Ed Granger-Happ Save the Children April 7, 2003

  2. Some Quotes • ''Software easily rates among the most poorly constructed, unreliable, and least maintainable technological artifacts invented by man.'' --Paul Strassmann, former CIO for Xerox Corp. --Business Week, 12/6/99 • “All told, bad software cost U.S. businesses $85 billion in lost productivity last year,according to Jim Johnson, president of …The Standish Group” --Business Week, 12/6/99

  3. Some Quotes (cont.) • Software bugs, or errors, are so prevalent and so detrimental that they cost the U.S. economy an estimated $59.5 billion annually … although all errors cannot be removed, more than a third of these costs, or an estimated $22.2 billion, could be eliminated by an improved testing infrastructure that enables earlier and more effective identification and removal of software defects.”--National Institute of Standards and Technology (NIST), 6/28/02

  4. Some Quotes (cont.) • “A software mogul … makes a speech. ‘If the automobile industry had developed like the software industry’, the mogul proclaims, ‘we would all be driving $25 cars that get 1,000 miles to the gallon.’ To which an automobile executive retorts, ‘Yeah, and if cars were like software, they would crash twice a day for no reason, and when you called for service, they'd tell you to reinstall the engine.’ --Charles C. Mann July/August 2002

  5. Some NGO Realities • “If the user could just tell us exactly what they want, we could program anything!” • “The scope on our first interactive web project changed so many times we missed our deadline at least six times.” • “If we were to do every project that our users requested we wouldn’t get anything done.” • “I’m moving to Mozambique; at least there it’s my own chaos.”: • “What budget?”

  6. Extreme Programming…What is it? • A definition: “XP is a lightweight methodology for small-to-medium-sized teams developing software in the face of vague or rapidly changing requirements.” • “XP promises to reduce project risk, improve responsiveness to business changes, improve productivity throughout the life of a system, and add fun to building software in teams…” -- Kent Beck • Why “Extreme?” • XP takes common sense practices and turns up the volume to 10 on each.

  7. What Problem is XP Trying to Solve? • Software development risks: • Schedule slips • Canceled projects • Systems going sour • High defect rates • Misunderstood business • Changing business • Feature bloat, scope creep • Staff turnover

  8. Four Project Variables • Four Interrelated Factors • Cost • Time • Quality • Scope • At the most the user can determine 3; the 4th goes to the developers • XP fixes the time (60 day projects max) • What “gives” is the scope… • that feature would really make a nice phase 18 feature

  9. Key Assumption • The cost of change rises slowly over time. • Therefore, make the decision as you go, as late as possible

  10. An evolving plan Small releases Use metaphors, stories to describe systems Keep designs simple Write the tests first Refactor Program in pairs Collective ownership Continuous integration 40-hour work week (avoid burn-out) On-site customer Code to standards Keep meetings short Embrace change XP Practices

  11. Why do XP? • Software project failures are legendary • Traditional software methodologies are unable to: • Handle faster delivery cycles • Nor able to embrace frequent change • They can’t live in web world

  12. The “waterfall” method of development has failed Traditional development methodologies are not working requirements analysis specification design coding testing release

  13. Why should an NGO try XP • NGO’s cannot afford a large project failure. • “When IT makes a mistake here, a child goes hungry.” --Gordon Hodgson, former CIO, World Vision. • Program and other NGO professionals cannot specify what they need. • With limited IT budgets, NGO’s need small, quick successes • The 80% solution sooner

  14. STC Experience • We focused on a few of the practices last year: • Small releases, “chunking down” • We went from one major web release in 2001 to 13 in 2002 • Prototyping everything… you gotta see it to understand what you want • Metaphors, stories to describe systems. • One page application diagrams • Story cards to sort priorities • Paired design & testing teams • “Rubber Ducking”

  15. Project Chunking • CIO Magazine, April 1, 2003, pp. 93-94 • Benefits of chunking down: • Less risk: smaller and less complex, shorter timeframes, learning from preceding phases, changing environment • Benefits realized sooner: putting value in users hands earlier • More frequent decision points: can change project’s course, leverage learning

  16. How Have Things Improved? • In the IS Department, from FY01 to FY02 • Productivity jumped • Project completions grew 99% (697 to 1386) • Project on-time rate improved to 78% (434 to 1086) • Significant turnaround on interactive web development • Phase one – 9 month project, 6 delays • Phase two – 13 3-week phases, 0 delays • User satisfaction grew 10% (CSI of 3.25 to 3.55 on 5 point scale)

  17. And a word from our daily skeptic

  18. Getting Started • Read Kent Beck’s book, Extreme Programming Explained, 166 pp. • See the additional resources listed on the next slides. • Try it… test, tune, throw away!

  19. Resources • Links to articles on Extreme Programming: • http://www.cutter.com/project/ead0002.html • a long article, but good background and treatment • http://www.xprogramming.com/what_is_xp.htm • a good overview, and web site of XP resources • http://www.extremeprogramming.org/map/project.html • a good one-page map of the XP process • also a good reference site—see their home page at http://www.extremeprogramming.org • http://tayek.com/~ray/xptools/ • a superb XP bibliography of web links and tools

  20. Resources (cont.) • Books • Extreme Programming Explained: Embrace Change, by Kent Beck • Questioning Extreme Programming, by Pete McBreen • A Practical Guide to eXtreme Programming, by David Astels, Granville Miller, Miroslav Novak • The Pragmatic Programmer: From Journeyman to Master, by Andrew Hunt, David Thomas, Ward Cunningham

More Related