CMMI or Agile: Why Not Embrace Both!
3 views
Skip to first unread message
agilenature
Oct 29, 2010, 6:44:26 PM10/29/10
to cragile
Recomiendo mucho este artículo publicado en sitio del SEI,
David Anderson (gran promotor de Kanban) es co-autor del artículo.
He aquí el abstract:
______
Agile development methods and CMMI (Capability Maturity Model
Integration) best practices are often perceived to be at odds with
each other. This report clarifies why the discord need not exist and
proposes that CMMI and Agile champions work toward deriving benefit
from using both and exploit synergies that have the potential to
dramatically improve business performance.
________
Y este es un fragmento de ejemplo, de la página 13:
_____
Whether analyzing the CMM or CMMI, there is one thing shared by both
works that makes them unique—they are models, not standards, for
improving product quality and process performance.
However, for nearly two decades, the software industry has experienced
the result of people misusing appraisal ratings as entry criteria,
confusing appraisal ratings for measures of business performance, and
misapplying a model as a standard in an environment in which products
are created to meet contractual requirements.
Used in this way, CMM and CMMI best practices were misinterpreted and
misused. It is not an exaggeration to say that any approach to improve
an organization’s achievement of business objectives in such an
environment would have difficulty overcoming an emphasis on RFP
requirements and keen competition for multi-year contracts.
Does this situation mean that CMMI is wrong for software? Not in the
least. It simply illuminates the following reasons why some perceive
CMMI to be incompatible with Agile ideals:
* The context from which the CMM and CMMI originated was specific to a
particular customer base having unique challenges and characteristics
of high risk and low trust.
* The CMM and CMMI were a new paradigm introduced into a large (and
dominant) industry where paradigms, including the attitudes and
beliefs associated with them, were in place for many years (e.g.,
command and control).
* Agile ideals developed as a backlash against the inefficient
software development patterns that arose in this industry.
_______
De veras léanlo, muy bueno.
David Anderson (gran promotor de Kanban) es co-autor del artículo.
He aquí el abstract:
______
Agile development methods and CMMI (Capability Maturity Model
Integration) best practices are often perceived to be at odds with
each other. This report clarifies why the discord need not exist and
proposes that CMMI and Agile champions work toward deriving benefit
from using both and exploit synergies that have the potential to
dramatically improve business performance.
________
Y este es un fragmento de ejemplo, de la página 13:
_____
Whether analyzing the CMM or CMMI, there is one thing shared by both
works that makes them unique—they are models, not standards, for
improving product quality and process performance.
However, for nearly two decades, the software industry has experienced
the result of people misusing appraisal ratings as entry criteria,
confusing appraisal ratings for measures of business performance, and
misapplying a model as a standard in an environment in which products
are created to meet contractual requirements.
Used in this way, CMM and CMMI best practices were misinterpreted and
misused. It is not an exaggeration to say that any approach to improve
an organization’s achievement of business objectives in such an
environment would have difficulty overcoming an emphasis on RFP
requirements and keen competition for multi-year contracts.
Does this situation mean that CMMI is wrong for software? Not in the
least. It simply illuminates the following reasons why some perceive
CMMI to be incompatible with Agile ideals:
* The context from which the CMM and CMMI originated was specific to a
particular customer base having unique challenges and characteristics
of high risk and low trust.
* The CMM and CMMI were a new paradigm introduced into a large (and
dominant) industry where paradigms, including the attitudes and
beliefs associated with them, were in place for many years (e.g.,
command and control).
* Agile ideals developed as a backlash against the inefficient
software development patterns that arose in this industry.
_______
De veras léanlo, muy bueno.
Reply all
Reply to author
Forward
0 new messages