Download
agile development n.
Skip this Video
Loading SlideShow in 5 Seconds..
Agile Development PowerPoint Presentation
Download Presentation
Agile Development

Agile Development

368 Views Download Presentation
Download Presentation

Agile Development

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Agile Development Presented to PMAG L. Lowe, G. Mays and J. Skinner April 19,2010

  2. Agenda • What Is Agile Development • Why Use Agile (WIFM) • Agile vs. Waterfall • Agile & PPM • State Agency Experience • Next Steps • References

  3. What is Agile Development Agile is a team driven iterative approach to development where the users and product owner are constantly involved with the development team during the entire project life cycle. • Uses simple adaptable processes • Continuous communication with stakeholders • Empowers people to collaborate and make decisions quickly • Relies on continuous planning, testing and integration • Uses iterations, incremental delivery and continuous feedback to refine and deliver the product • Methodologies include Extreme Programming (XP), Scrum, Crystal, Dynamic Systems Development Method (DSDM), Lean Development & Feature-Driven Development (FDD)

  4. Agile Manifesto for Software Development Agile Manifestowww.agilemanifesto.org

  5. Agile Principles • Customer satisfaction is #1 priority • Deliver early, continuous value • Embrace change and uncertainty • Business and developers work together • Provide motivated individuals the work environment and support they need to succeed • Communicate face to face (co-locate if possible) • Best architectures, requirements, and designs emerge • Trust the team to get job done

  6. Why Use Agile (WIFM)

  7. Agile: Better Productivity Source: http://www.shinetech.com/attachments/104_ShineTechAgileSurvey2003-01-17.pdf

  8. Agile: Better Quality Source: http://www.ambysoft.com/surveys/agileFebruary2008.html

  9. Agile: Better All Around Source: http://www.versionone.net/pdf/AgileDevelopment_ResultsDelivered.pdf

  10. Agile Vs. Waterfall

  11. Agile Vs. Waterfall

  12. Agile Vs. Waterfall

  13. Agile Vs. Waterfall

  14. Agile & PPM Agile is Easy…. Implementing it is Hard… …Must change Processes and Values…

  15. Agile & PPM: Lifecycle

  16. Agile & PPM: Artifacts

  17. Agile & PPM: Artifacts NOTE: See handout that shows mapping/XRef that relates PPM artifacts with corresponding Agile artifacts.

  18. State Agency Experience

  19. The Pig’s Point Of View • Pig – Someone occupying one of the three Scrum Roles (Team, Product Owner, Scrum Master) who has made a commitment and has authority to fulfill it.

  20. On the Job Training- Real Experience • Terminology is different; processes are different but the goals are the same. • Meet the requirements, on time, and if possible under budget. • The Product Backlog provides the overall game plan and replaces the requirements document. • The Sprint Backlog sets the pace and determines the work or tasks to be done. • Expect the first Agile project and first few sprints to be “Lessons Learned”.

  21. Sprint Backlog The Sprint Backlog is similar to the Gantt Chart

  22. Very First Sprint • The First Agile Project – First Sprint 2008

  23. Current Agile Project Most recently completed Sprint of our 4th Agile Project

  24. State Agency Experience: Lessons Learned • Build time in for training and learning curve • Planning and real life don’t always match – getting hands dirty up front saves time and effort over long run • Very little time to “explore” different possibilities in a SPRINT if one did not work • SCRUM does not fit all projects - best system development methodology depends on nature of the project, organization and other factors • Harder to use pure SCRUM methods in database centric projects • There are tradeoffs to simplifying the workflow too much - more detail gets more information, but takes too long • Useful to forge ahead in spite of unexpected obstacles • Prioritizing what was important helped a lot

  25. State Agency Experience: Lessons Learned • Very talented, focused people can move along very quickly, given opportunity to do so • Fully dedicated resources are essential for optimal work product • Daily meetings were very useful to keep momentum going, and information flowing • SCRUM Master stays very busy removing obstacles and keeping team focused • Useful to keep documentation to a minimum, yet documentation of process and decisions was important • Detail in documentation is critical for future recall and decision making • Team found delivery of implementable product in a short period of time very satisfying • Media capability may enhance virtual team efficiency when co-location is not viable – e.g. collaborating with websites and video conferencing

  26. Next Steps • The Enterprise Project Management Office Improvement Plan for FY09-11addresses items identified in our recent agency survey. Comments indicated the need to review the project approval processes for system development life cycles other than SDLC. • An agency workgroup will be formed to develop best practices for systems development life cycles (SDLCs) such as waterfall, agile and infrastructure projects.

  27. References: Websites

  28. References: Books

  29. Conclusion • Being Agile Is Our Favorite Thing

  30. Questions