Whenever I am asked to help a small Agile organization improve its process
maturity, I always recommend we start with a gap analysis against the
CMMI model.2 The purpose of a gap analysis is to assess where an organization
currently is from a process perspective and identify gaps based on the
CMMI model. The result is a strengths and weaknesses report and an initial
set of recommendations to help the organization achieve its current process
goals.
When I present weaknesses I have observed based on the CMMI model practices,
I always stress that these might or might not be actual weaknesses in
the organization that require actions. Part of the follow-on plan always
includes more analysis of these “potential weaknesses” to determine the
proper course of action given the organization’s business situation and
process needs.
Executing a gap analysis is important for any organization initiating a
process improvement effort because it facilitates the most effective plan
based on the correct priorities for that particular organization. I now want to
share the key points on how I conduct a gap analysis for an Agile organization,
and why the approach you use when doing a gap analysis is crucial
when it comes to agility. This will lead to a discussion of additional techniques
I use to help Agile