Do we need a policy for each Generic Practice?

Should policies (Gp2.1) address every Generic Practice (Gp2.1-GP2.10) in a given Process Area?

Hold on a second while I consult my 3725 page policy manual . . . hmmm here it is, policy number 1634111a.7....

I don't mean to make fun of your question, but its circular nature sure gave me a headache!

The purpose of GP2.1 "Establish an organizational policy" is to set the expectation that the processes that are adopted by the organization are to be used. If you have a mature, self-disciplined organization then maybe something very limited is all that is necessary. We test this on appraisals by asking people how they know they're supposed to use a certain process. There answer SHOULD be that management has set that expectation in some way. Sometimes for a less mature organization more detail is needed, but if they need a policy for each practice then you have bigger problems!

GP2.1 i specific to a process area - not the practices in the process area. Sure, we test the institutionalization of a process at the practice level, but it is almost never performed at the practice level. A Process may have practices from many different PA's represented in it, so it's a little tough to set the expectation that a specific practice be performed in a vacuum.

And, since most of the GPs are mirrors of the PAs anyway (GP2.2-2.4 is like PP, GP2.6 is iike CM, GP2.8 is like PMC, etc) then does it really make sense to have policies for each GP?

There is no requirement for this level of granularity in the CMMI - and if it doesn't make sense for your business then there is no reason to do it.

That's what I think. Good luck!

www.broadswordsolutions.com

What is the best way to satisfy Generic Practice GP2.1?

We are just getting started and right away we're struggling! What is the best way to satisfy GP2.1 for all of the process areas?

The Generic Practices are foundational to the success of any or all of the process you deploy, and GP 2.1, "Establish and Maintain an Organizational Policy for planning and performing the process" is one of the most important.

GP2.1 is intended to set the expectation, for all practitioners, that they are to plan for AND perform the process that has been established, and that management wants them to do just that. It is an unambiguous request to plan and perform the process as intended.

Now, this set of policies should mirror your process, not the CMMI, and should clearly let everyone know what management's expectations related to performing the process are.

Not every policy is called "a policy" and some may not even exist in a "policy manual."

I have one client that created such a manual, a 100 page document with a detailed policy (bordering on process) and signatures for all the relevant stakeholders contained within its pages. Did this meet the CMMI requirements? Sure, and then some. The problem with this approach is that a) it's too much work to establish and maintain; b) it's not that valuable and c) no one will read it.

Policies can often be effectively communicated in training materials, on posters, in emails, and via word of mouth. In fact, a combination of all of these is often required to get everyone on the same page!

Good luck,

www.broadswordsolutions.com