Key Points of Process Overview

Key Points of Process Overview

Process describes our level of quality. Without having a defined process, there is nothing to manage against. Process and quality are not free. There is a cost in establishing a managed, repeatable process. As project managers, we must continue to ask ourselves, "Why is quality important?" and "What is our optimum level of quality?" What is "good enough?" As shown in the following figure, 99.9% sounds like a really high quality rating, but when human life or health is at stake, it may not be good enough.

The Software Project Managers Network has developed a list of 16 best practices. These are the management and technical practices with the highest return on investment (ROI) in developing and sustaining large-scale software-intensive systems, as ranked by the U.S. Department of Defense:

 1.     Formal risk management
 2.     Empirical cost and schedule estimation
 3.     Metrics-based project management
 4.     Earned value tracking
 5.     Defect tracking against quality targets
 6.     People-aware program management
 7.     Configuration management
 8.     End-to-end requirements tracing
 9.     System-architecturebased software design
10.    Data and database interoperability
11.    Formal definition and control of interfaces
12.    Visible and inspectable design
13.    Cost-justified and quality-justified reuse
14.    Formal inspections
15.    Managing tests as assets
16.    Frequent compile and smoke testing

These 16 best practices are addressed in this blog. This section looks at how all of them are integrated into the management of a process.

what is good enough


project manager, process, software project
The contents available on this website are copyrighted by TechPlus unless otherwise indicated. All rights are reserved by TechPlus, and content may not be reproduced, published, or transferred in any form or by any means, except with the prior written permission of TechPlus.
Copyright 2017 SPMInfoBlog.
Designed by TechPlus