SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 286 | Next

Margaret K. Kulpa, Kent A. Johnson

"Interpreting the CMMI: A Process Improvement Approach, Second Edition"

Running projects quantitatively is not an overnight
transition.
118 n Interpreting the CMMI
A bad example of collecting data and using them follows. Most organizations
simply ask, ???How many years must we go to prove that we have met the criteria
for historically accurate data???? Wrong question. One organization collected data
for 15 years about their projects. The data collected for 14 years were simply when
the project started and when it ended. Each project took about seven years to complete.
We find it difficult to imagine any real value that was added to these projects
by simply collecting start and end dates. The fifteenth year of data collection
included the start of each phase of software development and the end??”Requirements
start and end, Design start and end, Code start and end, Test start and end,
and Installation start and end. Although we can find much more value in these
types of data and their collection, we believe that having only one year of the data
was not enough, especially since each project ran almost seven years, and most of
the projects were only in the Requirements phase.


Pages:
274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298