Average Reviews:
(More customer reviews)I am in a very large organization that is making all of our projects (at the least) CMMI Maturity level-3 compliant. We have Level-5 software factories (offshore centers), some Level-4 programs/projects, and 1,000s of Level-3 compliant (internally appraised) projects.
However, we have "custom" project management document templates that still rely tremendously on the author's (project manager) previous experience writing these references or LUCK (b/c a lower level grunt is actually writing the document!).
The IEEE project management documents (project management approach, risk and issue management plan, change management plan, etc.) are not perfect, but they ARE based on hundreds of project experiences and years or experience and input from 100s of IEEE member organizations.
This book provides the table of contents from the IEEE documents but Not 100% of the text (you have to spend a few $100usd to be a IEEE member to get the actual templates).
BUT, if you are starting a SEPG (software engineering process group) or Quality Management System (QMS) team dont waste time trying to create your templates from scratch. Step-1, get this book and create the ourline of the documents, step-2 harvest the best examples from your projects and insert the best sample sections into the templates.
Remember that 60-80% of these documents are essentially "boiler-plate" that apply to most of your projects, or projects of a certain type.
I RECOMEND that you fill in your templates with as much of the "boilerplate" as possible and make these management documents as close to "fill in the blank" as possible.Using the IEEE standards as a baseline for the structure and content will help you significantly.
CAVEATS: IEEE standards, like way too many I.T. documents, includes the Glossary section in the beginning of the document. Although this may be helpful to define key words before they are encountered, I find the least obtrusive location for the Glossary is as an Appendix. This is not only a common location for documents in many many other fields, it encourages the glossary to be as small or large as it needs to be, rather than drowning the reader with terms they may already know in the beginning of the document.
DITTO for large Tables and Diagrams. I suggest they are located either in the Appendix or as a separate external file that is maintained separately (and is easily referenced by several documents - something dificult to do if they are buried in a single document).
Click Here to see more reviews about: Practical Support for CMMI-SW Software Project Documentation Using IEEE Software Engineering Standards
Product Description:
Software process definition, documentation, and improvement should be an integral part of every software engineering organization. This book addresses the specific documentation requirements in support of the CMMI-SW® by providing detailed documentation guidance in the form of:
Detailed organizational policy examples.
An Integrated set of over 20 deployable document templates.
Examples of over 50 common work products required in support of assessment activities.
Examples of organizational delineation of process documentation.
This book provides a set of IEEE Software Engineering Standards-based templates that support the documentation required for all activities associated with software development projects. The goal is to provide practical support for individuals responsible for the development and documentation of software processes and procedures. The objective is to present the reader with an integrated set of documents that support the requirements of the CMMI-SW® Levels 2 and 3. This book is meant to both complement and extend the information provided in Jumpstart CMM®/CMMI® Software Process Improvement Using IEEE Software Engineering Standards. Jumpstart provides a detailed mapping of both the CMM® and the CMMI-SW® to the IEEE standards set and provides a logical basis for the material contained within this text.
It is hoped that this book will provide specific support for organizations pursuing software process definition and improvement. For organizations that do not wish to pursue CMMI® accreditation, this document will show how the application of IEEE Standards can facilitate the development of sound software engineering practices.It also comes with a CD-Rom.
Get 16% OFF
Want to read more honest consumer review about Practical Support for CMMI-SW Software Project Documentation Using IEEE Software Engineering Standards now ?
0 comments:
Post a Comment