Agile, then CMMI

Starting with MSF for Agile Software Development and then migrating in a future project to MSF for CMMI Process Improvement sounds like a great way to mature the capabilities in your organization. Good luck with that.

David

DavidJ.Anderson at 2007-9-9 >

http://www.sei.cmu.edu/publications/articles/paulk/xp-from-a-cmm-perspective.html

This sentiment is also echoed by Mark Paulk, one of the authors of CMM. Paulk has compared CMM and XP, and suggests that XP methods can be helpful in providing the "how to" for many CMM practices

SEI considered XP largely satisfies the lower three levels of CMM.

You also need to ask whether your organisation is looking for a production process or a design process.

Will

Wills at 2007-9-9 >

Agile mindset is a way software producers server better to their software consumers.

Agile mindset includes many practices for how the software producer team behave internally, enabling them to have an external behavior that fits better the expectations of their software consumers.

If those software consumers want CMMI, just fine, the software producer team satisfy those requirements as any other requests from their consumers.

The software producer team behave internally with the agile mindset.

In other words, agile mindset and CMMI are not mutually exclusive. In fact, they serve complete different purposes.

MarcoDorantes at 2007-9-9 >

We are using Agile for now to establize then we are planning to move to CMMI for maturity. Anyhow even after we move to CMMI as framework of porcess optimization I will be willing to revert back to Agile when certain project seems to work better with Agile development.

I look at CMMI as a process optimizatoin and benchmarking framework rather than a development framework and methodology like MSF and RUP.

Ibrahim

brhoom at 2007-9-9 >