Agile, then CMMI

Agile, then CMMI

• Guillermo Proano MSFT

  you might be interested in the following:
  
  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
  
  

• Dominic99Rus

  Hi Harry,

  Did you get the answer to your question

  How do you go about starting the CMMi process

  Did you get any consulting advice to get this underway

  Any inputs would be highly appreciated.

  Thanks

  -Advait

  
  

• Dennis Van Dyke

  I don't see any issues with starting out with Agile. You can run one team project with Agile and another with CMMI to see what fits you best. I think we are going to start out with CMMI because Agile is a little too lax on process for our taste. (I think our management will be more willing to purchase this product if we can enforce more stringent processes.) We'll customize the CMMI process and end up with our own flavor tailored for our needs.

  
  
  

• Vishwa

  Yes, it is the recommended practice. Why would it be a recipe for confusion The CMMI method builds incrementally on the Agile method. Note: This is a unique innovation to the MSF offering from Microsoft. To our knowledge no one esle has released an agile method that complies with CMMI model level 3.

  See my paper on the topic from last year's Agile conference
  http://www.agilemanagement.net/Articles/Papers/StretchingAgiletoFitCMMIL.html

  Regards,

  David

  
  
  

• Andy Boura

  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

  
  
  

• printerpro

  In message 
  , 
  David@J.Anderson.invalid writes
  >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.
  
  Is this a recommended practice (starting with Agile, then moving to 
  Formal) 
  
  It seems to me, at first sight, that this might be a recipe for 
  confusion - teams used to do things one way, now it's suddenly 
  different 
  
  I'm slightly confused over this recomendation.
  
  Comments 
  
  -- 
  Thomas Lee
  Microsoft Regional Director Europe
  (tfl@psp.co.uk)
  
  
  
  
  
                                              
  

• Sibusiso

  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.

  
  
  

• Scott Phibbs - MSFT

  Our CMMI method is designed to allow an easy transition from the Agile method. In fact the CMMI process reuses a great deal of the agile content and has a basic agile structure.
  
  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
  
  
• Agile, then CMMI