Here is a textbook case of applying the Capability Immaturity Model
. My suspicion is the US Marshals Service
is Level 0, but for the paranoid among us, Level -2 seems reasonable.
According to CMU-SEI data, over 70% of all software organizations are at Level 1 (Chaotic) of the Capability Maturity Model. In reality many may lie below the merely chaotic, but no lower levels exist in the CMM.
defines and describes lower maturity levels and their associated Kounter Productive Attitudes (KPAs). Of course in the SEI's CMM, KPA stands for Key Process Area.
The 4 levels of Immaturity:
- Level 0: Negligent (Indifference) - Failure to allow successful development process to succeed. All problems are perceived to be technical problems. Managerial and quality assurance activities are deemed to be overhead and superfluous to the task of the software development process.
- Level -1: Obstructive (Counter Productive) - Counter productive processes are imposed. Processes are rigidly defined and adherence to the form is stressed. Ritualistic ceremonies abound. Collective management precludes assigning responsibility. Status quo "über alles" (more important than anything else).
- Level -2: Contemptuous (Arrogance) - Disregard for good software engineering institutionalized. Complete schism between software development activities and software process improvement activities. Complete lack of a training program.
- Level -3: Undermining (Sabotage) - Total neglect of own charter, conscious discrediting of peer organization's software process improvement efforts. Rewarding failure and poor performance.