ASQ Agile v Waterfall Essay Example for Free

ASQ vigorous v waterfall EssayWaterfall vs. mobile switch directionLisa Sieverts, PMP, PMI-ACPPhil Ailes, PMI-ACPWaterfall vs. brisk bedevil solicitudeAg rarityaWhat is a intentionOverview handed-down throw away care alert Project perplexityThe Differences reaping Life pedal The team ups Requirements WBS/Product Backlog Schedule Risk qualityQA2Lisa Sieverts Phil Ailes1Waterfall vs. straightaway Project solicitudeWhat is a Project? Temporary Goal Constrained3Lisa Sieverts Phil AilesWaterfall vs. spry Project counselingWhat makes projects special? Projects arecharacterized byuncertainty4Lisa Sieverts Phil Ailes2Waterfall vs. energetic Project charge tralatitious Waterfall Projects Traditional Waterfall Projects Dates from the finish up 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 forethoughtTradit ional Waterfall ProjectHighMediumRequirements economic crisisOptionalHigh practiceMedium scurvyOptionalHighDevelopment MediumLowOptionalHighTestingMediumLowOptionalHighDeployMediumLowOptional6Lisa Sieverts Phil Ailes3Waterfall vs. Agile Project ManagementWaterfall Advantages7Lisa Sieverts Phil AilesWaterfall vs. Agile Project ManagementWaterfall Advantages realised Processes- Project Management Body ofKnowledge Management Controls (Apparent) Predictability Great for low uncertainty/high habituation 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 than about the Process than theProduct Keeps the customer at bay by the time they see the end results it may be too late Project teams often be recognize rigid and resistant to diverge Those darn users keep changing theirminds. Long product development time10Lisa Sieverts Phil Ailes5Waterfall vs. Agile Project ManagementAgile Project Management The Agile Way Experiments in the mid-nineties Values self-organizing teams No formal projectmanagement Iterative approach FlexibleLisa Sieverts Phil AilesWaterfall vs. Agile Project ManagementManifestoThe Agile Manifesto for Software Development We are unc everyplaceing fracture ways of developing software by doing it and helping others do it. Through this name we have come to order Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to smorgasbord 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 fuseTestSprints Low Priority FeaturesIntegrateTestIntegrateTestDesi gnTestTestDevelopIntegrateTest express 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 established processes Management resistance to change Reduced (apparent) shoutability Requires culture change Its new there isnt a lot to draw upon17Lisa Sieverts Phil AilesWaterfall vs. Agile Project ManagementProject Life Cycle TraditionalwaterfallInitiatePlanDefineDesignBuildTest Agile Projects reiterativeEnvisionSpeculateExplore varyCloseRepeat asnecessary18Lisa Sieverts Phil Ailes9Waterfall vs. Agile Project ManagementThe Team WaterfallSponsorProductManagerProjectManagerThe Team defined roles AgileSponsorProductproprietorScrumMasterThe Team variableroles19Lisa Sieverts Phil AilesWaterfall vs. Agile Project ManagementThe Requirements Waterfall LargeDocument Formal, foundon analysis Performed byBusinessAnalyst Completed in the first place anydevelopmentbegins Agile Small IndexCards exploiter Stories, ground onconversation Performed bythe ProductOwner Completedjust in time20Lisa Sieverts Phil Ailes10Waterfall vs. Agile Project ManagementThe Foundation DocumentsWaterfall Work Breakdown building100 % of Scope21Lisa Sieverts Phil AilesWaterfall vs. Agile Project ManagementThe Foundation DocumentsAgile The Produc t BacklogRoman Pichler, Agile Product Management22Lisa Sieverts Phil Ailes11Waterfall vs. Agile Project ManagementThe Schedule Waterfall Built before workbegins End date is often Agile Rebuilt every sprint End date evolvesbased on teamvelocity Focused on nearterm accuracy Emphasizes regulardelivery of workingfeatures shape 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 exploiter Acceptanceoccurs at the end ofthe project Testers anddevelopers worktogethersimultaneously User Accep tanceoccurs 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 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 an efficacious 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 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