ASQ Agile v Waterfall Essay

Waterfall vs. Agile Project Management Lisa Sieverts, PMP, PMI-ACP Phil Ailes, PMI-ACP Waterfall vs. Agile Project Management Agenda †¢ †¢ †¢ †¢ What is a Project Overview –†¯ Traditional Project Management –†¯ Agile Project Management The Differences –†¯ Product Life Cycle –†¯ The Teams –†¯ Requirements –†¯ WBS/Product Backlog –†¯ Schedule –†¯ Risk –†¯ Quality Q&A 2  ©Lisa Sieverts & Phil Ailes 1 Waterfall vs. Agile Project Management What is a Project? †¢Ã¢â‚¬ ¯ Temporary †¢Ã¢â‚¬ ¯ Goal †¢Ã¢â‚¬ ¯ Constrained 3  ©Lisa Sieverts & Phil Ailes Waterfall vs. Agile Project Management What makes projects special? †¢Ã¢â‚¬ ¯ Projects are characterized by uncertainty 4  ©Lisa Sieverts & Phil Ailes 2 Waterfall vs. Agile Project Management Traditional Waterfall Projects †¢Ã¢â‚¬ ¯ Traditional Waterfall Projects –†¯ Dates from the end of WWII –†¯ Grew out of Defense industry –†¯ Based on Deming Cycle of Plan-Do-Check-Act –†¯ Emphasizes heavy up-front analysis –†¯ Lots of documentation –†¯ PMBOK versions 1-4  ©Lisa Sieverts & Phil Ailes Waterfall vs. Agile Project Management Traditional Waterfall Project High Medium Requirements Low Optional High Design Medium Low Optional High Development Medium Low Optional High Testing Medium Low Optional High Deploy Medium Low Optional 6  ©Lisa Sieverts & Phil Ailes 3 Waterfall vs. Agile Project Management Waterfall – Advantages 7  ©Lisa Sieverts & Phil Ailes Waterfall vs. Agile Project Management Waterfall – Advantages †¢Ã¢â‚¬ ¯ Established Processes- Project Management Body of Knowledge †¢Ã¢â‚¬ ¯ Management Controls †¢Ã¢â‚¬ ¯ (Apparent) Predictability †¢Ã¢â‚¬ ¯ Great for low uncertainty/high dependency projects –†¯ Construction –†¯ Update of established product –†¯ Maintenance projects 8  ©Lisa Sieverts & Phil Ailes 4 Waterfall vs. Agile Project Management Waterfall – Disadvantages 9  ©Lisa Sieverts & Phil Ailes Waterfall vs. Agile Project Management Waterfall – Disadvantages †¢Ã¢â‚¬ ¯ Sometimes is more about the Process than the Product †¢Ã¢â‚¬ ¯ Keeps the customer at bay – by the time they see the end results it may be too late †¢Ã¢â‚¬ ¯ Project teams often become rigid and resistant to change: â€Å"Those darn users keep changing their minds.† †¢Ã¢â‚¬ ¯ Long product development time 10  ©Lisa Sieverts & Phil Ailes 5 Waterfall vs. Agile Project Management Agile Project Management †¢Ã¢â‚¬ ¯ The Agile Way –†¯ Experiments in the 1990s –†¯ Values self-organizing teams –†¯ No formal â€Å"project management† –†¯ Iterative approach –†¯ Flexible  ©Lisa Sieverts & Phil Ailes Waterfall vs. Agile Project Management Manifesto †¢ The Agile Manifesto for 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: †¢Ã¢â‚¬ ¯ Individuals and interactions over processes and tools †¢Ã¢â‚¬ ¯ Working software over comprehensive documentation †¢Ã¢â‚¬ ¯ Customer collaboration over contract negotiation †¢Ã¢â‚¬ ¯ Responding to change over following a plan –†¯ That is, while there is value in the items on the right, we value the items on the left more.† 12  ©Lisa Sieverts & Phil Ailes 6 Waterfall vs. Agile Project Management The Agile Way Sprints – High Priority Features Integrate Test Sprints – Low Priority Features Integrate Test Integrate Test Design Test Test Develop Integrate Test Demo & Feedback Develop Requirements Test Test Develop Sprints – Optional Priority Features Demo & Feedback Requirements Design Test Design Test Demo & Feedback Develop Requirements Test Demo & Feedback Requirements Design Test Sprints – Medium Priority Features 13  ©Lisa Sieverts & Phil Ailes Waterfall vs. Agile Project Management Agile – Advantages 14  ©Lisa Sieverts & Phil Ailes 7 Waterfall vs. Agile Project Management Agile – Advantages †¢Ã¢â‚¬ ¯ Shorter development cycles †¢Ã¢â‚¬ ¯ Customer participates, providing direct feedback †¢Ã¢â‚¬ ¯ Team-ownership – developers, testers, analysts and customers work together †¢Ã¢â‚¬ ¯ Process encourages and easily adapts to change †¢Ã¢â‚¬ ¯ Improved quality because testing is continuous 15  ©Lisa Sieverts & Phil Ailes Waterfall vs. Agile Project Management Agile – Disadvantages 16  ©Lisa Sieverts & Phil Ailes 8 Waterfall vs. Agile Project Management Agile – Disadvantages †¢Ã¢â‚¬ ¯ Lack of established processes †¢Ã¢â‚¬ ¯ Management resistance to change †¢Ã¢â‚¬ ¯ Reduced (apparent) predictability †¢Ã¢â‚¬ ¯ Requires culture change †¢Ã¢â‚¬ ¯ It’s new – there isn’t a lot to draw upon 17  ©Lisa Sieverts & Phil Ailes Waterfall vs. Agile Project Management Project Life Cycle †¢Ã¢â‚¬ ¯ Traditional: waterfall –†¯Initiate –†¯Plan –†¯Define –†¯Design –†¯Build –†¯Test †¢Ã¢â‚¬ ¯ Agile Projects: iterative –†¯Envision –†¯Speculate –†¯Explore –†¯Adapt –†¯Close –†¯Repeat as necessary 18  ©Lisa Sieverts & Phil Ailes 9 Waterfall vs. Agile Project Management The Team †¢Ã¢â‚¬ ¯ Waterfall –†¯Sponsor –†¯Product Manager –†¯Project Manager –†¯The Team – defined roles †¢Ã¢â‚¬ ¯ Agile –†¯Sponsor –†¯Product Owner –†¯Scrum Master –†¯The Team – variable roles 19  ©Lisa Sieverts & Phil Ailes Waterfall vs. Agile Project Management The Requirements †¢Ã¢â‚¬ ¯ Waterfall –†¯ Large Document –†¯ Formal, based on analysis –†¯ Performed by Business Analyst –†¯ Completed before any development begins †¢Ã¢â‚¬ ¯ Agile –†¯ Small Index Cards –†¯ User Stories, based on conversation –†¯ Performed by the Product Owner –†¯ Completed â€Å"just in time† 20  ©Lisa Sieverts & Phil Ailes 10 Waterfall vs. Agile Project Management The Foundation Documents †¢ Waterfall –†¯ Work Breakdown Structure 100 % of Scope 21  ©Lisa Sieverts & Phil Ailes Waterfall vs. Agile Project Management The Foundation Documents †¢ Agile –†¯ The Product Backlog Roman Pichler, Agile Product Management 22  ©Lisa Sieverts & Phil Ailes 11 Waterfall vs. Agile Project Management The Schedule †¢Ã¢â‚¬ ¯ Waterfall –†¯ Built before work begins –†¯ End date is often †¢Ã¢â‚¬ ¯ Agile –†¯ Rebuilt every sprint –†¯ End date evolves based on team velocity –†¯ Focused on nearterm accuracy –†¯ Emphasizes regular delivery of working features predetermined –†¯ Strives to predict the future –†¯ Emphasizes delivery of the entire product 23  ©Lisa Sieverts & Phil Ailes Waterfall vs. Agile Project Management Risk †¢Ã¢â‚¬ ¯ Waterfall –†¯ Inherently high-risk based on long product cycles –†¯ Emphasizes the ability to predict the future –†¯ Risk Register †¢Ã¢â‚¬ ¯ Agile –†¯ Inherently low-risk based on customer feedback –†¯ Emphasizes adaptation to changing environment –†¯ Risk Register 24  ©Lisa Sieverts & Phil Ailes 12 Waterfall vs. Agile Project Management Quality †¢Ã¢â‚¬ ¯ Waterfall –†¯ Testing is at the end †¢Ã¢â‚¬ ¯ Agile –†¯ Testing begins before development of the project –†¯ Testers work separately from developers –†¯ User Acceptance occurs at the end of the project –†¯ Testers and developers work together simultaneously –†¯ User Acceptance occurs at end of every sprint 25  ©Lisa Sieverts & Phil Ailes Waterfall vs. Agile Project Management What’s Different? †¢Ã¢â‚¬ ¯ Waterfall –†¯ Plan all in advance –†¯ Work Breakdown Structure –†¯ Functional specs –†¯ Gantt chart –†¯ Status reports –†¯ Deliver at the end –†¯ Learn at the end –†¯ Follow the plan –†¯ Manage tasks †¢Ã¢â‚¬ ¯ Agile –†¯ Plan as you go –†¯ Product Backlog –†¯ User stories –†¯ Release plan –†¯ Story boards –†¯ Deliver as you go –†¯ Learn every sprint –†¯ Adapt everything –†¯ Team ownership 26  ©Lisa Sieverts & Phil Ailes 13 Waterfall vs. Agile Project Management Summary †¢Ã¢â‚¬ ¯ Both Waterfall and Agile have the same goals: –†¯ Delivering a well- tested product that satisfies the customer within an efficient time frame that doesn’t leave the team worn out 27  ©Lisa Sieverts & Phil Ailes Waterfall vs. Agile Project Management Questions 28  ©Lisa Sieverts & Phil Ailes 14 Waterfall vs. Agile Project Management Thank You 29  ©Lisa Sieverts & Phil Ailes Waterfall vs. Agile Project Management Contact Us †¢Ã¢â‚¬ ¯ Lisa Sieverts –†¯ Facilitated Change –†¯ www.lisasieverts.com –†¯ 603.762.0235 †¢Ã¢â‚¬ ¯ Phil Ailes –†¯ Ailes Consulting –†¯ www.ailes-consulting.com –†¯ 603.903.7051 30  ©Lisa Sieverts & Phil Ailes 15