ASQ Agile v Waterfall Essay

f wholes vs. bustling understand careLisa Sieverts, PMP, PMI-ACPPhil Ailes, PMI-ACP waterfall vs. brisk calculate guidanceAg repealaWhat is a pick upOverview Traditional design Management flying shed ManagementThe Differences return Life Cycle The aggroups Requirements WBS/ harvest-tide Backlog Schedule Risk QualityQ&A2Lisa Sieverts & Phil Ailes1falls vs. ready Project ManagementWhat is a Project? Temporary Goal constrain3Lisa Sieverts & Phil AilesWaterfall vs. restless Project ManagementWhat makes projects special? Projects arecharacterized byuncertainty4Lisa Sieverts & Phil Ailes2Waterfall vs. Agile Project ManagementTraditional Waterfall Projects Traditional Waterfall Projects Dates from the block off of WWII Grew out of Defense industry Based on Deming Cycle of program-Do-Check-Act Emphasizes heavy up-front analysis Lots of sustenance PMBOK versions 1-4Lisa Sieverts & Phil AilesWaterfall vs. Agile Project ManagementTraditional Waterfall ProjectHighMediumRequirem ents measly nonmandatoryHighDesignMedium depressive disorderOptionalHighDevelopment Medium woefulOptionalHigh runningingMediumLowOptionalHighDeployMediumLowOptional6Lisa Sieverts & Phil Ailes3Waterfall vs. Agile Project ManagementWaterfall Advantages7Lisa Sieverts & Phil AilesWaterfall vs. Agile Project ManagementWaterfall Advantages Established Processes- Project Management Body ofKnowledge Management Controls (Apparent) Predictability Great for low uncertainty/high dependency projects Construction Update of established output bread and butter projects8Lisa Sieverts & Phil Ailes4Waterfall vs. Agile Project ManagementWaterfall Disadvantages9Lisa Sieverts & Phil AilesWaterfall vs. Agile Project ManagementWaterfall Disadvantages Sometimes is more about the Process than theProduct Keeps the customer at bay by the time they see the end results it may be too late Project team ups often become rigid and resistant to castrate Those darn users keep changing theirminds. Long crop de velopment time10Lisa Sieverts & Phil Ailes5Waterfall vs. Agile Project ManagementAgile Project Management The Agile Way Experiments in the 1990s Values self-organizing teams No formal project oversight Iterative approach FlexibleLisa Sieverts & Phil AilesWaterfall vs. Agile Project Management pronunciamentoThe Agile Manifesto for Software Development We are uncovering better ways of developing software by doing it and dowery 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 quest a plan That is, while there is value in the items on the right, we value the items on the left over(p) more.12Lisa Sieverts & Phil Ailes6Waterfall vs. Agile Project ManagementThe Agile WaySprints High anteriority FeaturesIntegrateTestSprints Low Priority FeaturesIntegrateTestIntegrateTestDesignTestTestDevelopIntegrateTe st read & FeedbackDevelopRequirementsTestTestDevelopSprints Optional Priority FeaturesDemo & FeedbackRequirementsDesignTestDesignTestDemo & FeedbackDevelopRequirementsTestDemo & FeedbackRequirementsDesignTestSprints Medium Priority Features13Lisa Sieverts & Phil AilesWaterfall vs. Agile Project ManagementAgile Advantages14Lisa Sieverts & Phil Ailes7Waterfall vs. Agile Project ManagementAgile Advantages Shorter development cycles Customer participates, providing lead feedback Team-ownership developers, testers, analysts andcustomers work together Process encourages and easily adapts to change Improved quality because testing is continuous15Lisa Sieverts & Phil AilesWaterfall vs. Agile Project ManagementAgile Disadvantages16Lisa Sieverts & Phil Ailes8Waterfall vs. Agile Project ManagementAgile Disadvantages Lack of established processes Management resistance to change Reduced (apparent) predictability Requires culture change Its new there isnt a lot to draw upon17Lisa Sievert s & Phil AilesWaterfall vs. Agile Project ManagementProject Life Cycle TraditionalwaterfallInitiatePlan set upDesignBuildTest Agile ProjectsiterativeEnvisionSpeculateExploreAdapt shuttingRepeat asnecessary18Lisa Sieverts & Phil Ailes9Waterfall vs. Agile Project ManagementThe Team Waterfall condescendProductManagerProjectManagerThe Team defined roles AgileSponsorProductOwnerScrumMasterThe Team variableroles19Lisa Sieverts & Phil AilesWaterfall vs. Agile Project ManagementThe Requirements Waterfall LargeDocument Formal, groundon analysis Performed byBusiness analyst Completedbefore anydevelopmentbegins Agile Small IndexCards User Stories, base onconversation Performed bythe ProductOwner Completedjust in time20Lisa Sieverts & Phil Ailes10Waterfall vs. Agile Project ManagementThe Foundation DocumentsWaterfall Work Breakdown social organisation100 % of Scope21Lisa Sieverts & Phil AilesWaterfall vs. Agile Project ManagementThe Foundation DocumentsAgile The Product BacklogRoman Pichler, A gile Product Management22Lisa Sieverts & Phil Ailes11Waterfall vs. Agile Project ManagementThe Schedule Waterfall Built before workbegins End date is often Agile Rebuilt every flair End date evolvesbased on teamvelocity Focused on nearterm accuracy Emphasizes regulardelivery of workingfeaturespredetermined Strives to predict thefuture Emphasizes deliveryof the entire product23Lisa Sieverts & Phil AilesWaterfall vs. Agile Project ManagementRisk Waterfall inherently high-riskbased on longproduct cycles Emphasizes theability to predict thefuture Risk Register Agile Inherently low-riskbased on customerfeedback Emphasizesadaptation tochangingenvironment Risk Register24Lisa Sieverts & Phil Ailes12Waterfall vs. Agile Project ManagementQuality Waterfall Testing is at the end Agile Testing begins beforedevelopmentof the project Testers workseparately fromdevelopers User Acceptanceoccurs at the end ofthe project Testers anddevelopers worktogethersimultaneously User Acceptanceoccurs at end ofe very sprint25Lisa Sieverts & Phil AilesWaterfall vs. Agile Project ManagementWhats Different? Waterfall Plan all in advance Work BreakdownStructure Functional specs Gantt chart Status reports quit 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 ownership26Lisa Sieverts & Phil Ailes13Waterfall vs. Agile Project ManagementSummary Both Waterfall and Agilehave the same goals Delivering a well-tested product thatsatisfies thecustomer within anefficient time framethat doesnt leavethe team worn out27Lisa Sieverts & Phil AilesWaterfall vs. Agile Project ManagementQuestions28Lisa Sieverts & Phil Ailes14Waterfall vs. Agile Project ManagementThank You29Lisa Sieverts & Phil AilesWaterfall vs. Agile Project Management concern Us Lisa Sieverts Facilitated Change www.lisasieverts.com 603.762.0235 Phil Ailes Ailes Consulting www.ailes-consulting.com 603.90 3.705130Lisa Sieverts & Phil Ailes15