Here s a summary list of things you should do and things you should not do when first starting out on your organization s process improvement journey using CMMI:
Assume that the organization in which you want to make improvement has already evolved some good management and engineering practices that can be incrementally improved using CMMI as a guide.
Identify any existing organizational standards that you can leverage.
Look for evolved business practices in areas of the business that aren t
Find out what the organization s history (if any) for change and process improvement is.
Base the documented processes and procedures first on what people are already doing and then begin the improvements.
Don t assume that the organization already has some good engineering or management practices or standards already in place. (Even if you think this, don t say it
Don t throw away or ignore evolved business practices that can be used as a springboard for CMMI-based improvement.
Don t assume that just because people in an organization have been doing something or doing something a particular way that it still has business value. Legacy practices and standards can sometimes be a
Don t take the attitude that the organization is in terrible shape and the only thing that will save it is you and CMMI ” you will
Now take the post-chapter quiz (Figure 1.7) and think about what you ve learned and how some of your views toward CMMI-based process improvement have changed. Think about what you will do with the information you ve learned (and how it makes you feel).
Figure 1.7: Chapter 1: What Did You Learn? What Will You Do?
I m not asking you what you do, Dave. I m asking you who you are.
” Jack Nicholson as Dr. Buddy Rydell in Anger Management 
This chapter is about defining the roles of people in the organization and the roles of organizations which work together to deliver a system or service. As you will soon learn, it is very easy to make assumptions about roles and responsibilities in an organization. If left unchallenged ” like comparing your assumptions with reality ” the assumptions will soon become hard-held beliefs. Take the quiz in Figure 2.1 to see what kinds of beliefs you may have about organizational roles and then, after reading the chapter, take the quiz in Figure 2.3 to find out what you ve learned.
Figure 2.1: Chapter 2: What Do You Think? What Do You Believe?
 Segal, Peter, Anger Management, Sony Pictures, 2003.
Both SW-CMM and CMMI provide either explicit or implicit guidance for establishing roles and responsibilities in the organization. In SW-CMM, there are Ability to Perform key practices that address establishing certain functions to perform processes and activities such as project management, change control, quality assurance, and training. In CMMI, there are no explicit practices that come right out and say, define your roles and responsibilities, but there are several GPs that heavily depend on some level of established roles. GP 2.3 requires that resources be provided for performing the process, developing the work products, etc. A resource doesn t have to be a person or people in the abstract world of CMMI, but resources are almost always people in the world in which we work. GP 2.4 comes as close as a model should to being explicit about roles and responsibilities. Its
Say you re an analyst and your main job, as you know it, is to perform system tests. A project manager comes to you and
The authors of CMMI did the right thing; they did not prescribe to organizations how they should be structured in terms of departments, functions, roles,
CMMI Survival Guide: Just Enough Process Improvement
CMMI for Development: Guidelines for Process Integration and Product Improvement (3rd Edition) (SEI Series in Software Engineering)
CMMI for Services: Guidelines for Superior Service (2nd Edition) (SEI Series in Software Engineering)
Integrating CMMI and Agile Development: Case Studies and Proven Techniques for Faster Performance Improvement (SEI Series in Software Engineering)