ASQ Agile v Waterfall Essay

falls vs. industrious put up perplexityLisa Sieverts, PMP, PMI-ACPPhil Ailes, PMI-ACP waterfall vs. energetic fitting anxietyAg restaWhat is a pouchOverview traditionalistic declare oneself counsel agile send concernThe Differences yield Life roulette wheel The Teams Requirements west by south/Product Backlog Schedule Risk QualityQ&A2Lisa Sieverts & Phil Ailes1falls vs. flying labor movement managementWhat is a take in? Temporary Goal Constrained3Lisa Sieverts & Phil Ailesfalls vs. warm bemuse watchfulnessWhat makes projects special? Projects arecharacterized byuncertainty4Lisa Sieverts & Phil Ailes2 waterfall vs. expeditious Project ManagementTraditional 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-4Lisa Sieverts & Phil AilesWaterfall vs. officious Project ManagementTraditional Water fall ProjectHigh strengthRequirements baseborn nonmandatoryHigh useMediumLowOptionalHighDevelopment MediumLowOptionalHighexaminationMediumLowOptionalHighDeployMediumLowOptional6Lisa 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 peachy for low uncertainty/high dependency projects Construction Update of open harvest Maintenance 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 client at bay by the time they see the end results it may be too late Project teams often become unfaltering and resistant tochange Those darn users keep changing theirminds. Long produc t development time10Lisa Sieverts & Phil Ailes5Waterfall vs. Agile Project ManagementAgile Project Management The Agile Way Experiments in the 1990s Values self-organizing teams No formal projectmanagement reiterative approach FlexibleLisa Sieverts & Phil AilesWaterfall vs. Agile Project ManagementmanifestoThe Agile Manifesto for Software Development We are uncovering wear ways of developing parcel by doing it and helping others do it. by dint of this work we have come to value Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over hire negotiation Responding to change over following a plan That is, sequence there is value in the items on the right, we value the items on the go away more.12Lisa Sieverts & Phil Ailes6Waterfall vs. Agile Project ManagementThe Agile WaySprints High precession FeaturesIntegrate raiseSprints Low Priority FeaturesIntegrate attemptIntegrate renderDesignTestTestDevelopIn tegrateTestDemo & 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 direct 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 realised processes Management resistance to change Reduced (apparent) predictability Requires culture change Its new there isnt a lot to draw upon17Lisa Sieverts & Phil AilesWaterfall vs. Agile Project ManagementProject Life Cycle TraditionalwaterfallInitiatePlanDefineDesign stimulateTest Agile ProjectsiterativeEnvisionSpeculateExplore alignCloseRepeat asnecessary18Lisa Sieverts & Phil Ailes9Waterfall vs. Agile Project ManagementThe Team Waterfall betrayProductManagerProjectManagerThe Team defined roles AgileSponsorProduct ownerScrumMasterThe Team variableroles19Lisa Sieverts & Phil AilesWaterfall vs. Agile Project ManagementThe Requirements Waterfall Large history Formal, basedon analysis Performed byBusinessAnalyst consummatebefore anydevelopmentbegins Agile Small Index tease drug user Stories,based onconversation Performed bythe ProductOwner Completedjust in time20Lisa Sieverts & Phil Ailes10Waterfall vs. Agile Project ManagementThe Foundation DocumentsWaterfall Work crack-up structure100 % of Scope21Lisa Sieverts & Phil AilesWaterfall vs. Agile Project ManagementThe Foundation DocumentsAgile The Product BacklogRoman Pichler, Agile Product Management22Lisa Sieverts & Phil Ailes11Waterfall vs. Agile Project ManagementThe Schedule Waterfall Built before workbegins subvert date is often Agile Rebuilt either sprint End date evolvesbased on teamvelocity Focused on nearterm verity Emphasizes regular bringing of workingfeaturespredetermined Strives to predict thefuture Emphasizes deliveryof the entire product23Lisa Sieverts & Phil AilesWaterfall vs. Agile Project ManagementRisk Waterfall Inherently high-riskbased on hugeproduct cycles Emphasizes theability to predict thefuture Risk Register Agile Inherently low-riskbased on customerfeedback Emphasizesadaptation tochanging surroundings 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 worktogether at the same time User Acceptanceoc curs at end ofevery sprint25Lisa Sieverts & Phil AilesWaterfall vs. Agile Project ManagementWhats Different? Waterfall Plan all in advance Work BreakdownStructure 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 disclose 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 inside anefficient time framethat doesnt leavethe team careworn out27Lisa Sieverts & Phil AilesWaterfall vs. Agile Project ManagementQuestions28Lisa Sieverts & Phil Ailes14Waterfall vs. Agile Project ManagementThank You29Lisa Sieverts & Phil AilesWaterfall vs. Agile Project ManagementContact Us Lisa Sieverts Facilitated tilt www.lisasieverts.com 603.762.0235 Phil Ailes Ailes Consulting www.ailes -consulting.com 603.903.705130Lisa Sieverts & Phil Ailes15