ASQ Agile v Waterfall Essay Example for Free

ASQ wide awake v falls Essay waterfall vs. Agile foresee circumspectionLisa Sieverts, PMP, PMI-ACPPhil Ailes, PMI-ACP waterfall vs. Agile formulate circumspectionAgendaWhat is a ProjectOverview tralatitious Project Management Agile Project ManagementThe Differences Product Life Cycle The Teams Requirements WBS/Product cumulate Schedule Risk QualityQA2Lisa Sieverts Phil Ailes1 waterfall vs. Agile Project ManagementWhat is a Project? Temporary Goal Constrained3Lisa Sieverts Phil Ailes waterfall vs. Agile Project ManagementWhat makes projects special? Projects arecharacterized byuncertainty4Lisa Sieverts Phil Ailes2Waterfall vs. Agile 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. Agile Project ManagementTraditional Waterfall ProjectH ighMediumRequirementsLowoptionalHigh creationMediumLowoptionalHigh maturement MediumLowOptionalHigh testMediumLowOptionalHighDeployMediumLowOptional6Lisa 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 product Maintenance projects8Lisa Sieverts Phil Ailes4Waterfall vs. Agile Project ManagementWaterfall Disadvantages9Lisa Sieverts Phil AilesWaterfall vs. Agile Project ManagementWaterfall Disadvantages Sometimes is more about(predicate) the Process than theProduct Keeps the customer at bay by the time they see the end results it may be too late Project teams much become rigid and resistant tochange Those darn users keep changing theirminds. Long product development time10Lis a 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 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 encyclopaedic 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.12Lisa Sieverts Phil Ailes6Waterfall vs. Agile Project ManagementThe Agile WaySprints High Priority Features unifyTestSprints Low Priority FeaturesIntegrateTestIntegrateTestDesignTestTestDevelopIntegrateTestDemo FeedbackDevelopRequirementsTe stTestDevelopSprints 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 established processes Management shelter to change Reduced (apparent) hazardability Requires culture change Its new there isnt a lot to draw upon17Lisa Sieverts Phil AilesWaterfall vs. Agile Project Manage mentProject Life Cycle TraditionalwaterfallInitiatePlanDefineDesignBuildTest Agile Projectsiterative run intoSpeculateExploreAdaptCloseRepeat asnecessary18Lisa Sieverts Phil Ailes9Waterfall vs. Agile Project ManagementThe Team WaterfallSponsorProductManagerProjectManagerThe Team defined roles AgileSponsorProductOwnerScrumMasterThe Team inconstantroles19Lisa Sieverts Phil AilesWaterfall vs. Agile Project ManagementThe Requirements Waterfall LargeDocument Formal, basedon analysis Performed byBusinessAnalyst endbefore anydevelopmentbegins Agile Small IndexCards User Stories,based onconversation Performed bythe ProductOwner establishedjust in time20Lisa Sieverts Phil Ailes10Waterfall vs. Agile Project ManagementThe Foundation DocumentsWaterfall Work BreakdownStructure c % of Scope21Lisa Sieverts Phil AilesWaterfall vs. Agile Project ManagementThe Foundation DocumentsAgile The Product BacklogRoman Pichler, Agile Product Management22Lisa Sieverts Phil Ailes11Waterfall vs. Agile Pr oject ManagementThe Schedule Waterfall Built before workbegins End date is often Agile Rebuilt all(prenominal) sprint 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 tochangingsurround 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 acceptationoccurs at the end ofthe project Testers anddevelopers worktogethersimultaneously User Acceptanceoccurs 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 equal 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 raddled 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 Change www.lisasieverts.com 603.762.0235 Phil Ailes Ailes Consulting www.ailes-consulting.com 603.903.705130Lisa Sieverts Phil Ailes15