Here are my tips on practical implementation of CMMI as I experienced in my first appraisal:
1) In CMMI 1.2 PP (Project Planning), you have to create Project Plan, however the GP (Generic Practice) 2.2 require you to “Plan the Process”. It sounds like you have to create a plan to create the project plan. In my experience it is sufficient to include planning tasks in the plan, as example of planning tasks:
– Create detailed WBS (Work Break-Down Structure)
– Determine and analyze risks
– Discover and plan for data management
– Research for needed resource and skills
….
– Meet to review the plan
– Modify the plan (according to the meeting)
– Final meeting to get plan commitments
The same concept apply on GP 2.8 “Monitor and Control the Process”, it is sufficient to include tracking tasks like milestone review and weekly progress review. These two generic practices gives the organization detailed information about how much planning and tracking cost you in the project.
2) In PP, Specific Practice (SP) 2.3 “Plan for the management of project data”, it was sufficient to put this planning as part of the CM (Configuration Management) Plan.
3) It was a weakness to let the CM baseline creator to audit that baseline. As he will not be objective as he is biased to his creation. It is accepted to let a project team member to make the baseline audit, or make two project managers to review for each other.
4) In PP, SP 2.1 “Establish and maintain the project’s budget and schedule”, It is accepted to have the project effort as the budget!. Why?, the senior manager – as the organization is very small – don’t share the cost details with the project managers. However it is recommended to the organization to document the procedure of converting effort to cost.
5) The PMC SP 1.6 and 1.7 dictate to review periodically and on milestone the project. However it was accepted to align the milestone with the periodic review to be the same.
6) All MA (Measurements and Analysis) planning and tracking activities are stated in the project plan, however the measures will be collected and analyzed in a separate documents.
6) Regarding using tools, we can just use office and file server to do all what you need. Configuration management system is useful when developing source code, if the project is just migration or conversion of legacy source code, then the use of CM system can be dropped.
7) There is no paper based sign required, all the documentation and approvals accepted to be emails or just MOM (Minutes Of Meeting) documents.
8) Even not required in L2, the creation of templates is very helpful as there exist many details that can be forgotten.
9) In PIIDs (Practice Implementation Indicator Descriptions), it was not necessary to write many indirect artifacts, as affirmation through interview can be almost sufficient, except in case it is hard to get that affirmation.
10) You can easily plan the appraisal and meet your plan (without too much overtime) and even have fun.