WaterFall
Anti-Pattern: non-Iterative Software Development (and other Project) model. The term was introduced in 1970 by W. W. Royce; ironically, Royce himself advocated an Iterative approach to software development. Royce originally proposed what is now known as the waterfall model as an example of a system that he argued "is risky and invites failure". http://en.wikipedia.org/wiki/Waterfall_model
Edited: | Tweet this! | Search Twitter for discussion
BackLinks: 2003-06-30-IterativeAndIncrementalDevelopmentABriefHistory | 2006-01-28-WaterfallConference | 2006-10-02-YeggeAgileGoogle | 2006-11-03-SierraEducatingKidsScience | 2008-04-29-CaganHighfidelityPrototypes | 2012-09-19-AgileEnterpriseCultureHacking | 2013-11-19-ShirkyHealthcaregovManagementFailure | 2014-10-14-CaganProductVsItMindset | 2015-03-04-BowkettJeffriesScrumArgue | 2015-06-05-CaganProductFail | 2017-08-31-AlternativesForAgileAndLeanRoadmappingPart1ThinkInFeatureSets | 2017-12-03-RunningInCircles | 2018-02-01-GiladWhyYouShouldStopUsingProductRoadmapsAndTryTheGistFramework | 2019-07-10-FriedAnnouncingShapeUpADeepDiveIntoHowWeWork | 2019-08-29-CaganProductVsFeatureTeams | 2020-02-08-TaylorAgileAsTrauma | 2021-01-18-WayneAreWeReallyEngineers | 2022-02-03-JeffriesExtremeprogrammingThoughts | 2025-01-06-HeusserAgileAlliancePmiPartnership | 3X | Backlog | BigDesignUpFront | CaganInspired | DataInformedProductManagement | GardeningYourProductProcess | InventToLearn | KanBan | MaryPoppendieck | PMI | ProductManagementTheater | ProjectManagementSoftware
TwinPages: RalfBarkow | WikiWikiWeb