|
|
©2004, by Hillel Glazer, Entinex, Inc.
CMMI and Tools
In trying to achieve any advanced CMMI levels (3 or above), you need to demonstrate maturity in software process management. However companies who don’t understand CMMI often make the mistake of slapping tools in place like a band-aid to solve their process short-comings or lack of discipline. That’s failure and frustration in the making.
This is like a problem faced by most software teams: Isn’t it true that to achieve the client’s desired results, business processes must be defined and "correct" before automating them with software? Physician, heal thy self!
However, if you’ve defined a process and understand the goals of that process, the right tool can save tremendous effort and time. Consider the CMMI process areas of requirements management, and project monitoring and control, two early process areas required for being appraised to CMMI Level 2 (staged). With these two process areas implemented properly, software teams can minimize scope creep by ensuring there is a process that captures and communicates agreed-upon requirements, and manage expectations by keeping their clients abreast of project status without the unpleasant surprises.
A common theme in both of these process areas is communication. That’s where a tool can help. Just as e-mail and Web sites improved many aspects of communication, the role of tools in pursuit of CMMI is in their ability to improve communication among developers and with their clients. Tools allow developers to avoid "reinventing the wheel" once they’ve figured out what processes work best for them.
Where Artifact Comes In
Some tools come with basic processes in anticipation of best or common practices. Artifact is such a tool. In terms of supporting CMMI, it facilitates communication, streamlines workflow, provides a repository for project documents and a place to keep a record of decisions and track issues to closure. It does so without presuming your process, but also comes with a nascent process based on years of successful distributed development.
Like any tool, Artifact does not make companies "compliant to CMMI". Rather, it gives an edge to companies who have, or are working toward, mature processes. It facilitates the key goals found throughout CMMI of involving relevant stakeholders, monitoring progress against plans, and keeping track of changes to work products and plans as the project goes forward. To emulate CMMI, it’s important to first understand the role of processes in managing development. Look at Artifact when you need a tool that supports CMMI.
<<< Back to page 1
Printer-Friendly
Copyright Notice and Reproduction Permission
All Contents © Copyright Entinex, Inc. All rights reserved. These works may be freely reproduced, distributed, or transmitted solely for non-commercial, personal, or educational purposes, provided that they are not modified and any reproduction or transmission contains this copyright notice and the author’s complete bio and company information as provided. Nothing else may otherwise be used, reproduced, published, or disseminated without prior written permission.
|
|