Skip to main content

CMMI Level 2 Implementation

  • Chapter
  • First Online:
  • 2141 Accesses

Part of the book series: Undergraduate Topics in Computer Science ((UTICS))

Abstract

This chapter is focused on the implementation of maturity level 2 in an organization. A CMMI level 2 organization has policies for managing a project, and procedures to implement these policies have been established. Practices are in place to ensure that the process is planned, performed, and controlled, and the process is enforced with independent audits.

This is a preview of subscription content, log in via an institution.

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   29.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   39.95
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Notes

  1. 1.

    It is mandatory to implement the supplier agreement management process when there is outsourcing of product development.

  2. 2.

    Unless Fred is the name of the estimation methodology or the estimation tool employed.

  3. 3.

    The actual deliverables required for the project management process area will depend on its approach to implementation and its current maturity. Some organizations may have a lot of the expected deliverables in place. Further, the use of tools to support the process may reduce the need for deliverables (e.g. the risk and issue logs may be automated). Some organizations may implement some of the level 3 process areas associated with project management (e.g. risk management) at this stage. The deliverables in Fig. 5.3 are an example of what may be produced.

  4. 4.

    This process area is not applicable to companies that are not using a third-party supplier.

  5. 5.

    The actual deliverables required will depend on its current approach to supplier selection and management.

  6. 6.

    The deliverables potentially include plans, system requirements, design and test deliverables.

  7. 7.

    This is typically done with a Requirements Traceability Matrix.

  8. 8.

    The terminology employed will vary from organization to organization. It may also be called the Business Requirements Specification (BRS).

  9. 9.

    Validation is often explained as “Are we building the right system?” Verification is explained as “Are we building it right?”

  10. 10.

    This may just be a simple Excel spreadsheet.

  11. 11.

    These procedures may be defined in the Configuration Management procedure and referenced in the CM plan.

  12. 12.

    The project manager may perform the CM manager role for small organizations and projects.

  13. 13.

    This will also describe how the change control board will function.

  14. 14.

    This may also be implemented by a test management tool for tracking defects (e.g. PV Tracker, Bugzilla).

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Gerard O’Regan .

Rights and permissions

Reprints and permissions

Copyright information

© 2011 Springer-Verlag London Limited

About this chapter

Cite this chapter

O’Regan, G. (2011). CMMI Level 2 Implementation. In: Introduction to Software Process Improvement. Undergraduate Topics in Computer Science. Springer, London. https://doi.org/10.1007/978-0-85729-172-1_5

Download citation

  • DOI: https://doi.org/10.1007/978-0-85729-172-1_5

  • Published:

  • Publisher Name: Springer, London

  • Print ISBN: 978-0-85729-171-4

  • Online ISBN: 978-0-85729-172-1

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics