Agile Methodology<br />David Mann, CIO <br />July 8, 2010<br />
People are more important than any process!<br />2<br />
The most important thing about process is "To Have One" <br /><ul><li>Examples of SDLC processes:
Agile (MSF for Agile, SCRUM, LEAN, …)
Waterfall
Spiral
Extreme Programming
ASD
Rational Unified</li></ul>3<br />
PMI PMBOK (PMP)<br />CMM<br />1969<br />1991<br />MSF 4.0<br />2006<br />MSF<br />CMM<br />1994<br />1991<br />Scrum<br />...
Which one is right for me?<br /><ul><li>Agile is more suitable for new product development where the scope gradually emerg...
Waterfall is more suitable for static models with defined unchangeable scope.  It is appropriate for maintaining mature sy...
Agile Misconception<br /><ul><li>Agile is not about rushing things; but if Agile is applied things gets delivered faster w...
Short Sprints (iterations) - 2 to 3 weeks
Full Customers Involvement to adjust course
Frequent Releases & Check-Points
Multi tracks
Focusing on delivering software (not process)
Upcoming SlideShare
Loading in...5
×

Agile methodology v 4.5 s

2,247

Published on

Published in: Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,247
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
96
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Transcript of "Agile methodology v 4.5 s"

  1. 1. Agile Methodology<br />David Mann, CIO <br />July 8, 2010<br />
  2. 2. People are more important than any process!<br />2<br />
  3. 3. The most important thing about process is "To Have One" <br /><ul><li>Examples of SDLC processes:
  4. 4. Agile (MSF for Agile, SCRUM, LEAN, …)
  5. 5. Waterfall
  6. 6. Spiral
  7. 7. Extreme Programming
  8. 8. ASD
  9. 9. Rational Unified</li></ul>3<br />
  10. 10. PMI PMBOK (PMP)<br />CMM<br />1969<br />1991<br />MSF 4.0<br />2006<br />MSF<br />CMM<br />1994<br />1991<br />Scrum<br />DSDM<br />Extreme Programming<br />Feature Driven (FDD)<br />Adaptive (ASD)<br />Lean<br />Crystal Clear<br />MSF 4.0 for Agile<br />1993<br />1995<br />1999<br />2000<br />2000<br />2003<br />2005<br />2006<br />Rational Unified Process<br />1981<br />MSF 4.0 for CMM<br />2006<br />Some processes are more Adaptive<br />Some processes are more Predictive<br />Adaptive/Predictive Scale<br />ADAPTIVE<br />PREDICTIVE<br />AGILE<br />ITERATIVE<br />WATERFALL<br />
  11. 11. Which one is right for me?<br /><ul><li>Agile is more suitable for new product development where the scope gradually emerges and continues to evolve. It is appropriate for new business model in a changing marketplace
  12. 12. Waterfall is more suitable for static models with defined unchangeable scope. It is appropriate for maintaining mature systems with mature business model</li></ul>5<br />
  13. 13. Agile Misconception<br /><ul><li>Agile is not about rushing things; but if Agile is applied things gets delivered faster with higher quality. Why?
  14. 14. Short Sprints (iterations) - 2 to 3 weeks
  15. 15. Full Customers Involvement to adjust course
  16. 16. Frequent Releases & Check-Points
  17. 17. Multi tracks
  18. 18. Focusing on delivering software (not process)
  19. 19. Agile does not mean chaos:
  20. 20. Think of Agile as many micro-waterfalls
  21. 21. Agile has “change control“ after each sprint (but less formal)
  22. 22. Agile has meaningful short documents; prototypes clarify requirements and design; all team members work in a project-room to reduces documents and meetings; the team must focus on delivering quality software and not just documents</li></ul>6<br />
  23. 23. MSF for Agile Development<br />Agile has tracks not phases; teams dash to the finish-line without waiting for each other<br />Plan<br />QA/Stabilize<br />Envision<br />Build<br />Deploy<br />
  24. 24. What is Agile about?<br /><ul><li>Agile is about putting something in front of the business/customer quickly so that business and IT can adjust course by:
  25. 25. Changing scope & requirements to gain the highest ROI
  26. 26. Changing plan & processes to reduce cost
  27. 27. Changing solution for the best design & performance
  28. 28. Changing QA test for the ultimate quality
  29. 29. Changing the deployment for enhance SLA
  30. 30. Adjusting to the marketplace and competitors
  31. 31. Agile is about embracing change
  32. 32. Agile is about customer’s active participation and not the end-result victim</li></ul>8<br />“The only constant in the universe is change”<br />
  33. 33. Waterfall Development Methodology<br />Start<br />Scope / Requirements<br />Design<br />Build / Coding<br />Quality Assurance<br />Deploy<br />Target<br />What if the Target is changed:<br />Lost Time & Money!<br />Waterfall has poor success rate in the industry<br />New Target<br />
  34. 34. Agile Development Methodology<br />Success !<br />Start<br />Sprint 1<br />Sprint 2<br />Sprint 3<br />Sprint 4<br />Sprint 5<br />Sprint 6<br />Sprint 9<br />Sprint 8<br />Sprint 7<br />Target<br />New Target<br />New Target<br />
  35. 35. Agile Development Methodology<br />Correct the Course<br />
  36. 36. Perceived Challenges with Agile:<br /><ul><li>Moving Deadlines
  37. 37. Over Budget
  38. 38. Difficult ROI Calculation</li></ul>12<br />
  39. 39. Solutions: Agile requires a mind-shift<br /><ul><li>Moving Deadlines: have a strict discipline on the feature list (features diet). Go to market with the minimum set of features and continue your growth (ex. Adobe Reader 9.3, iPhone 4.0, Flash Player 10.1). Standish study shows that:
  40. 40. 45% of features built are never used
  41. 41. 19% are rarely used
  42. 42. 16% are sometimes used
  43. 43. 13% are used often
  44. 44. 7% are always used
  45. 45. Over Budget: IT expenditure as a percentage of the revenue; set a budget for a project and develop within that budget
  46. 46. ROI Calculation: with shorter and frequent release cycle, ROI can be measured against actuals to make better decisions and reduce risk</li></ul>13<br />
  47. 47. 14<br />PMD - Business Analyst<br />Responsibilities: DEFINE<br /><ul><li>Own the Product which means PMD is empowered to make Product decisions on behalf of the business
  48. 48. Buy vs. Build, Competitive Analysis, Customer Research, Product Strategies
  49. 49. Document Vision, High-Level Features, Persona, Market Opportunities, ROI (PDD)
  50. 50. Document Detail Requirements, Business Workflows Diagrams, Use Cases, Reports Mockup (BRD)
  51. 51. Legal and IP Opportunities
  52. 52. Prioritize Features with Business
  53. 53. Approve Solution & Prototypes with Business
  54. 54. Coordinate Users Involvement, UAT with business
  55. 55. Business Rollout Plan including Beta/Pilots
  56. 56. Users Training and Adoption
  57. 57. Manage Cultural Ramifications
  58. 58. Users Surveys, Feature and Usage Matrix and Reports, Product Roadmap</li></ul>QA Tester<br />Responsibilities: TEST<br /><ul><li>Validate Solution which must meet or exceed requirements and quality
  59. 59. Create Test Plan and Provide Estimates
  60. 60. Test Cases including White-Box & Black-Box
  61. 61. Bug-Log and Reports
  62. 62. Test Automation
  63. 63. Regression, Integration and Smoke Tests</li></ul>Architect<br />Responsibilities: DESIGN<br /><ul><li>Select Tools and Technologies, framework, coding standards, source control
  64. 64. Solution Design must meet business vision plus it needs to be easy, fast, and wow
  65. 65. Database Model and Data Dictionary
  66. 66. Design needs to include quality, security, availability, expandability, scalability, and maintainability
  67. 67. Write and Drive TDD
  68. 68. Prototypes
  69. 69. BI
  70. 70. Design Executive Dashboards and Reports</li></ul>PMO - Project Manager<br />MSF for Agile Methodology<br />Roles & Responsibilities<br />Release Manager<br />Responsibilities: RELEASE<br /><ul><li>Technical Rollout Plan
  71. 71. Production Requirements
  72. 72. Operational SLA and Guides</li></ul>Sponsor & Business Responsibilities: VISION<br /><ul><li>Communicate Vision
  73. 73. Provide Financials
  74. 74. Kickoff Meeting
  75. 75. Empower Leaders and Team Players
  76. 76. Support Established Processes
  77. 77. Approve Priorities, Deadlines, & Prototypes
  78. 78. UAT by Business
  79. 79. Celebration</li></ul>PMD<br />Business<br />Analyst<br />Release<br />Manager<br />Sponsor<br />&<br />Business<br />Architect<br />QA<br />Tester<br />Developer<br />Developer<br />Responsibilities: BUILD<br /><ul><li>Write Program Code following best practices
  80. 80. Conduct Unit Testing
  81. 81. Document Work
  82. 82. Fix Bugs</li></ul>PMO - Project Manager<br />Responsibilities: DELIVER<br /><ul><li>Manage Sponsor’s Expectations
  83. 83. Project Plans & Sprint Plans
  84. 84. Team Communication including Project Status, Meetings, Executive Reports
  85. 85. Project Budget Management
  86. 86. Resource Management
  87. 87. Obtain Estimates
  88. 88. Keep trends, Actual vs. Estimates
  89. 89. Work with Managers to Assign Tasks & Hold team members Accountable for the deliveries
  90. 90. Change Control
  91. 91. Risk Management; Lessons Learned
  92. 92. Coordinate Technical Rollout Plan and Business Rollout Plan
  93. 93. Portfolio Management
  94. 94. SDLC & Process Improvements</li></li></ul><li>15<br />PMO - Project Manager<br />MSF for Agile Methodology<br />Foundational Principles - Team<br />PMD<br />Business<br />Analyst<br /><ul><li>Foster open communications
  95. 95. Work toward a shared vision (focus on delivering business value)
  96. 96. Empower team members
  97. 97. Establish clear accountability
  98. 98. Deliver incremental value
  99. 99. Stay Agile & expect change
  100. 100. Invest in Quality
  101. 101. Learn from experiences
  102. 102. Partner with customers</li></ul>Release<br />Manager<br />Sponsor<br />Business<br />Architect<br />QA<br />Tester<br />Developer<br />
  103. 103. 16<br />Production<br />Release<br />PDD<br />Test<br />Complete<br />UAT<br />Adoption<br />BRD<br />Rollout<br />Plans<br />Prototype<br />TDD<br />Test<br />Plan<br />Code<br />Complete<br />Agile Process & Deliverables<br />Repeated for each Sprint<br />Envision<br />Deploy<br />Stabilize (Testing) <br />Plan/Design<br />Build<br />
  104. 104. Q & A<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×