Process Maturity

The majority of assessment models (including the two described in the preceding sections) enable an organization to compute its process maturity. Management must then know how to use this number.

All too often, a senior manager decides that a specific process maturity level should become an organization goal. That is, an organization that currently has a process maturity of 1.0 is chartered with becoming a 3.0 organization within 24 months. Although there is nothing inherently wrong with setting process maturity goals, focusing solely on improving the process maturity value misses the point. The goals of every software development organization should be to improve the quality of the applications it builds, to satisfy its customers and users, and to accomplish work on time. Improving process maturity helps in achieving these goals, but it should not become the goal.

In general, process maturity (and process attribute grades) should be used in the following ways:

■ To target areas of strength and weakness

■ To raise management consciousness

■ To define areas in which further investigation (e.g., assessment meetings with relevant staff) may be needed

■ To provide a comparison to industry common and best practice

■ To serve as a baseline for reassessment later in the transition life cycle

Using process maturity in these ways, an organization can establish a foundation on which the technology transition plan is built.

Project Management Made Easy

Project Management Made Easy

What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.

Get My Free Ebook


Post a comment