Extreme Programming - Hydrid/Unified Methodologies

Extreme Programming - Hydrid/Unified Methodologies: "Other authors have tried to reconcile XP with the older methods in order to form a unified methodology. Some of these XP sought to replace, such as the waterfall method; example: Project Lifecycles: Waterfall, Rapid Application Development, and All That.

JPMorgan Chase & Co. tried combining XP with the computer programming methodologies of Capability Maturity Model Integration (CMMI), and Six Sigma. They found that the three systems reinforced each other well, leading to better development, and did not mutually contradict, see Extreme Programming (XP) Six Sigma CMMI."

Software development process

Software development process: "A software development process is a structure imposed on the development of a software product. Synonyms include software lifecycle and software process. There are several models for such processes, each describing approaches to a variety of tasks or activities that take place during the process."

Hybrid XP Model for Software Development

"Hybrid/Unified Methodologies: Other authors have tried to reconcile XP with the older methods in order to form a unified methodology. Some of these XP sought to replace, such as the waterfall method; example: Project Lifecycles: Waterfall, Rapid Application Development, and All That.

JPMorgan Chase & Co. tried combining XP with the computer programming methodologies of Capability Maturity Model Integration (CMMI), and Six Sigma. They found that the three systems reinforced each other well, leading to better development, and did not mutually contradict, see Extreme Programming (XP) Six Sigma CMMI."

Thinking About Software Development

The current project I am working on seems to be doing an about-face where software development is concerned. The challenge before me is to be able to articulate a comprehensive review of viable development models, ending with a proposal and implementation plan for a recommended model.

To further my own research, I will be using this blog to publish discoveries, thoughts, etc. Help and feedback welcome!

First off, some insight into the various models I am reviewing:

Waterfall model: The so-called "classic" model adopted widely by the public sector; assumes a set of well-defined requirements at the outset culminating in a cohesive development effort and monolithic testing regimen

RAD: Rapid Application Development; an iterative model that requires some compromises

Spiral: A model that stresses prototyping and provides justification of the iterative process

These are just some initial thoughts and mainly an excuse to get some links down for future reference. More to come...