The Definitive List of Software
Development Methodologies

Words by Jurgen

<ul><li>Scrum </li></ul>

<ul><li>Scrum </li></ul><ul><li>agile software development </li></ul><ul><li>Created
by Ken Schwaber and Jeff Sutherland </li></ul><ul><li>Scrum is a skeleton that includes a small set of practices and predefined roles. </li></ul><ul><li>Scrum is becoming a de facto standard for managing agile software development projects. </li></ul><ul><li>One reason for Scrum's popularity is that it consists of only a few common sense practices that can be applied in many situations. This also means that Scrum by itself is never enough, and that development teams have to shop in other methods (usually XP) for additional practices. </li></ul>

<ul><li>Extreme Programming (XP) </li></ul>

<ul><li>Extreme Programming (XP) </li></ul><ul><li>agile software
development </li></ul><ul><li>Created by Kent Beck </li></ul>XP is a set of best practices of which some are taken to an &quot;extreme&quot; level. As with other agile methods, XP regards ongoing changes to requirements as a natural and desirable aspect of software development. In the selection of its practices XP leans towards the daily software engineering activities of developers. XP is often seen as complementary to Scrum, filling most of the holes that Scrum leaves wide open.

<ul><li>Lean Software Development </li></ul>

<ul><li>Lean Software Development </li></ul><ul><li>agile software
development </li></ul><ul><li>Originally promoted by Mary and Tom Poppendieck </li></ul><ul><li>Translated from lean manufacturing to the software development domain. </li></ul><ul><li>Lean Software Development is adapted from the Toyota product development system, and it is the embodiment of the &quot;lean&quot; subculture that exists within the agile community (and that has by now become big enough not to be able to call itself lean anymore). </li></ul><ul><li>It is said that the lean and agile concepts form a perfect match. </li></ul>

<ul><li>Unified </li></ul>Process

<ul><li>Unified Process </li></ul><ul><li>software engineering framework
</li></ul><ul><li>Created by Ivar Jacobson, Grady Booch and James Rumbaugh. </li></ul><ul><li>The USDP is an extensible framework that should be customized for specific organizations and projects. </li></ul><ul><li>It aims to be a complete solution, which means that the full framework is far too big for all but a few projects. </li></ul><ul><li>However, stripping the framework to its bare essentials is like turning a plane into a bicycle. It might be easier simply to select another more lightweight method. </li></ul>

<ul><li>Rational Unified Process (RUP) </li></ul>

<ul><li>Rational Unified Process (RUP) </li></ul><ul><li>software
engineering framework </li></ul><ul><li>Created and maintained by the people at Rational Software (now owned by IBM), including Philippe Kruchten. </li></ul><ul><li>It is a commercial product delivered as a more detailed version of the Unified Software Development Process (which is presented as a generic public domain process). </li></ul><ul><li>This also means that the RUP suffers from the same problem as the USDP, being bloated and too costly to customize for small projects. </li></ul>

<ul><li>D </li></ul><ul><li>S </li></ul><ul><li>D </li></ul><ul><li>M </li></ul>

<ul><li>Dynamic Systems Development Method (DSDM)
</li></ul><ul><li>agile project management </li></ul><ul><li>created and maintained by the UK-based DSDM Consortium, which includes both vendors and experts. </li></ul>It was originally based upon the concepts of Rapid Application Development . DSDM finds itself on the same level as Scrum, meaning that it lists a small number of practices for project management of software development, while leaving the details of the real work (building a product) to be filled in by the development teams.

<ul><li>Prince2 </li></ul>

<ul><li>Prince2 </li></ul><ul><li>( Projects in Controlled
Environments) </li></ul><ul><li>project management methodology </li></ul><ul><li>Developed by the UK’s Office of Government Commerce (OGC). </li></ul><ul><li>Prince2 describes many processes and activities covering the management, control and organization of projects, and is deliberately not restricted to IT projects. </li></ul><ul><li>Even though Prince2’s popularity makes it a de facto standard for project management (particularly in Europe), it is criticized (by many including me) for being too prescriptive, too big and not easily customizable. </li></ul>

<ul><li>PMBOK </li></ul>

<ul><li>Project Management Body of Knowledge
(PMBOK) </li></ul><ul><li>project management methodology , </li></ul><ul><li>Developed by the US-based Project Management Institute (PMI). </li></ul>It is an internationally recognized standard providing the fundamentals of project management, not limited to IT-projects. Similar to Prince2, the PMBOK describes many processes and activities, though the PMBOK can be seen as being descriptive (what), while in contrast Prince2 is more prescriptive (how) . Their main similarity is that both are criticized for not being agile.

<ul><li>CMMI </li></ul>

<ul><li>Capability Maturity Model Integration (CMMI)
</li></ul><ul><li>software engineering model , </li></ul><ul><li>Developed by Watts Humphrey </li></ul>The CMMI aids in the definition and understanding of an organization’s processes and was originally intended as a tool for assessing the maturity of an organization’s processes. These days it is also used as a roadmap for process improvement . The CMMI is heavily criticized for focusing on processes rather than people, and it may lead organizations down the road of bureaucracy.

Pictures CC from Flickr Check
the slide notes for source details

<ul><li>Want to comment? </li></ul><ul><li>Leave a
note below or click the links to our blog posts. </li></ul><ul><li>Jurgen - Noop.nl </li></ul><ul><li>Craig - Betterprojects.net </li></ul>