Document clipping of agile development process based on CMMI

I've been busy lately, and I'm going to add to the last question today. Purely personal point of view, only throw bricks, hoping to lead Jade. This article is intended for small and medium-sized enterprises, and does not have a mature development process enterprise, so the clipped documents refer to the standard documents of the CMMI3 level.

About Agile Development and CMMI Management Everyone has experience, I am not on their own specific management to do the elaboration, close to the document cutting point of view, the first Agile development stressed that the core of things is communication, but for today's project development, personal communication is just a difficult point, do the development of the basic can not communicate without communication , especially when development schedules are tense, and it is more difficult to develop and test communication in a project, part of which is hostile in some sense. Not to mention the addition of customers to the list of exchanges, so the appropriate documentation can avoid the loss of project resources and buck practices.

1. The project starts with an estimate that is needed, but can simplify the process and documentation of the estimate, such as various estimation criteria and reports.

The test plan can be simplified without having to give a detailed project process plan because the project process for agile development is almost impossible to plan.

2. Walkthrough meetings are often open, milestone meeting documents can be cropped, and project supervision control documents can be cropped. But the project weekly needs.

3. Integrated project management documents can be cropped. Because many projects coding completed, basically completed, the concept of integration in many projects are ignored, there is little integration management, integration testing of the specific implementation of the report needs. It can be used as an experience summary on the company's configuration Management Server as a file material for later query issues on the project.

4. Baseline Setup documents can be cropped, configuration audits and other related configuration management documents can be cropped.

5. Risk management related documents can be cropped to a risk management checklist document for tracking management.

6. If the company has independent PPQA personnel, process and product quality assurance inspection can remain unchanged, but if there is no independent personnel, the part can be cropped, but the outline design, and detailed design can not be cut, at least also to come out a document, although the change in demand for these two documents changed greatly, These two documents can avoid the project handover problem that the developer flow brings, also can provide the basis for the test, if the requirement change is properly managed, the overall benefit is greater than the disadvantage, also needs to develop the outline design, the detailed design document, the code carries on the review and the cross-examination.

7. The measurement section can be cropped, because the measure needs to collect the measured data according to various documents and people in the project development process, and without the reliability of the document metrics data, it can be cropped.

8. Decision analysis and solutions can be cropped, decisions and solutions can be discussed in the walkthrough meeting.

9. Requirements change related documents can not be cropped, and should increase the management of demand change, because agile development emphasizes the rapid response to change, and the actual project for a variety of reasons for the customer and project personnel communication is not enough, and testers and developers, customer communication is not enough, So it's hard to reach the core value of agile Development's rapid response to change. Therefore, we should increase the management of demand changes, the relevant documents can not be cropped.

10. Requirements management related documents can be cropped, such as requirements Development Guide, requirements development documentation, etc. The core value of agile development involves the communication with the customer is more than the contract constraint, and the communication with the customer involves all aspects of the problem, so we should pay attention to multi-exchange, iterative demand research, and constantly tap the potential demand. Therefore, the various documents of demand research can be cropped, but the Customer interview record Analysis table should be clearly recorded, and a basic requirement specification must be given at last.

11. Product Integration Plan, Environment checklist, report can be cropped, but the interface list cannot be cropped, and it should be cross-examined.

12. During the test phase, the test plan can be cropped to a simple document, and the test case should not be cropped, because if the project is a person doing the test, you can consider tailoring the test case to the test operation process record. However, if more than one person participates, the same person's test operation record reusability is poor, so many people participate in testing the project test case is best not to crop, bug tracking management can be implemented with the bug management tool, the test report can not be cropped.

OPF,OPD process field related documents can be cropped, because no reliable data can be traced, and the document has no real meaning.

The OT and SM related documentation can be tailored to fit the situation.