Dl Context For The Case Study

I worked full time on the CCPDS-R project for 6 years, so this appendix is written from firsthand experience. My responsibilities included managing the development of the foundation technologies, developing the technical and cost proposals, conducting the software engineering exercise, and managing the software engineering activities through the early operational capability milestone.

I have tried to provide an accurate portrayal of the CCPDS-R project. While the data presented are mostly historical fact, all the subjective comments and value judgments are mine. The data were derived from published papers, internal TRW guidebooks, contract deliverable documents—all available from the actual artifacts of the CCPDS-R project—and my own personal experience. In a few minor cases, I have edited the data to remove unnecessary precision and eliminate inconsistencies within source documents produced at different points in the life cycle. My goal was to produce a relatively consistent description while excluding some of the minutia that would require detailed and irrelevant explanation.

Although the software industry can claim many successful projects (not enough, but many), good case studies are lacking. There are very few well-documented projects with objective descriptions of what worked, what didn't, and why. This was one of my primary motivations for providing the level of detail contained in this appendix. It is heavy in project-specific details, approaches, and results, for three reasons:

1. Generating the case study wasn't much work. CCPDS-R is unique in its detailed and automated metrics approach. All the data were derived directly from the historical artifacts of the project's process.

2. This sort of objective case study is a true indicator of a mature organization and a mature project process. The absolute values of this historical perspective are only marginally useful. However, the trends, lessons learned, and relative priorities are distinguishing characteristics of successful software development.

3. Throughout previous chapters, many management and technical approaches are discussed generically. This appendix provides in a real-world example at least one relevant benchmark of performance.

| My comments on relevance with the techniques, disciplines, and opinions discussed in j | previous chapters are provided in shaded boxes.

Was this article helpful?

0 0
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