Our company is moving towards CMMI Level 3 and we are trying to define the Tailoring Options for small projects. We have work orders/small projects that are equal in effort to 10 - 20 days in total (smetimes more than that up to 2 months). Since following the CMMI Level 3 processes require whole set of documentation followed it becomes inpractical and time-consuming to assign a huge effort to creating documentation.
Could you please advise on what approach should be taken to reduce amount of hours spent on documentation, what documetation could be altered, and yet to ensure that the process is followed?
In my hunble opinion, this is the problem with methodologies, they're just awesome for project level deliverables, but scaling (in this context, the ability to scale down is frequently overlooked).
Anyway, some practical advice would be:
1. Instead of full blown documents, where the frist 15 pages are project preamble and 'cut n paste', just create sections within a single document to represent the lifecycle methodology you use.
2. Example, define, design, build, test, implement are sections within a single document not a seperate document for each. Oversimplified? Probably, but the effect is to maintain and audit trail of the changes.
3. Typically BAU streams of work or discrete peices of functionality and are part of a maintenance release which are 20% enhanced functionality and 80% regression.