Customer finds that it is waste of effort in preparing documents adhering to the processes. He just pays for the hours for the time spent on product/Services. Convincing him has gone down the drain. Being CMM level 5 company, the organization requires documents. The development team says if customer does not want, why should they waste time on it? How do i handle this situation?
Sunday, June 1, 2008
Subscribe to:
Post Comments (Atom)
1 comment:
CMM does not mandate documentation. You need to decide the appropriate life cycle (waterfall, iterative, agile etc.) approach based on size, complexity etc. to meet customer's goals (Cost, Schedule and Quality) and use tailoring guidelines to meet objectives. For example - You may not need separate requirements, design, test plan, test cases etc. for Projects with small size (<100 hours). All these can be combined in a single document to save effort and improve productivity. Organizations need to develop / improve processes to meet customer cost/schedule/ quality goals and not just to acheive CMM level 4 or 5.
Talk to your SEPG and find out how they would like you to respond to such scenerios. If you and management are not able to convince your customer by showing historical data on productivity improvement, cost savings, defect prevention etc. explain the risks of lack of key deliverable documentation like requirements documents, design documents and transfer the risk to the customer.
Post a Comment