Information Technology Reference
In-Depth Information
CAUTION
If you implement agility through a Developer's Guide approach, make sure
your process identifies clearly the limits allowed through your tailoring
guidelines. Otherwise, you are likely to fall into the common trap of losing
fundamental practices (e.g., Systems Engineering critical practices) that
are necessary
12
[10].
An example of a potential lost fundamental systems engineering practice is
the appropriate degree of requirements analysis.
13
When I was asked to help RAVE develop their Agile Developer's Guide, one
of the first questions I asked related to how their tailoring process works.
While they were explaining the process to me, I asked:
What is the minimum everyone must do?
They were unable to provide an answer because they had no clearly defined
limits.
When Agile approaches are implemented appropriately together with
CMMI processes, effective implementation of required practices results, not
their deletion.
CAUTION
If you implement agility through a Developer's Guide approach, be aware of
the potential consequence of redundant efforts.
While the Agile Developer's Guide approach can be sound, it also presents
the risk of process redundancy and extra work when we are seeking the
reverse. A common tailoring mistake I have observed is to add the Agile
approach not as an implementation alternative, but rather on top of existing
required traditional practices. Specific areas in which to be on the lookout for
this costly mistake relate to product reviews and progress reporting.
12. See reference for a related article with more examples. In Chapter 4, I discuss a CMMI process asset
structure that supports agility and can help avoid the common trap described previously.
13. The subject of appropriate degree of requirements analysis when using an Agile approach is dis-
cussed in the DART case study.
