157RE: [XP] RE: [scrumdevelopment] Agile and CMM are contradictory
- Dec 6, 2001
> True agile teams will rely on cycles of inspection, adaptationI agree that teams that have the constraint of CMM will have a very
> and self-organization but to conform to the CMM process framework
> one _must_ conform to an ETVX process description format.
difficult, if not impossible, time reaching what you describe as "true
agile." But again, that is not the decision that people are confronted
with. All projects have constraints of all sorts. Those constraints will
affect the team's ability to achieve "true agile."
>I don't agree that it is a 2 sided fence. It is helpful to polarize things
> This makes it impossible to be on both sides of the fence.
to clarify what we mean, but in practice the world is not that clean. Teams
deal with spectrums of how far they can take something like agile. In
practice, there is no end point or side of the fence that is agile, there
are only relative positions closer to one extreme or the other. Although I
agree that the closer to "true agile" the better, I disagree that a project
that has constraints that push to the other end of the spectrum should not
explore how they can get as close to "true agile" as possible within their
> Until the CMM is allows processes to be self-organizedIn theory, yes. But in practice, there are CMM level 3 teams that are more
> and emergent, we will have two clearly distinct sides,
agile (i.e. self-organizing and emergent) than others. The more agile they
are the better, regardless of the closeness to "true." We should encourage
them to push their boundary, wherever it is.
- << Previous post in topic Next post in topic >>