Document cropping in the agile development process based on cmme

I have been busy recently. Today I am adding to my previous question. This is my personal opinion. I only want to give it a brick. This article is only intended for small and medium-sized enterprises, and there are no mature development process enterprises. For this reason, refer to the standard documents of cmmi3.

 

Everyone has their own experiences in Agile development and cmme management. I will not elaborate on the specific management of each of them, so I will give a close view on document cutting, first, agile development emphasizes communication at the core. However, for today's project development, personal communication is just a difficult issue. Basically, it is impossible to communicate without communication, this is especially true when the development progress is tight. It is more difficult to communicate with developers and tests in the project. In a sense, some of these two employees work in a hostile manner. In addition, the customer is added to the communication list. Therefore, proper documentation can avoid project resource loss and kicking.

 

1. estimation at the beginning of the project is required, but it can simplify the estimation process and documentation, such as various estimation standards and reports.

 

The test plan can be simplified without having to provide detailed project Process plans, because the agile development project process is almost impossible to plan.

 

2. Pre-view meetings should be held frequently, milestone meeting documents can be cropped, and project supervision and control documents can be cropped. However, weekly project reports are required.

 

3. integrated project management documents can be tailored. This is because after many coding projects are completed, the concept of integration is ignored in many projects. Basically, there are few integration management and implementation of integration testing, the report must be closed. It can be summarized as experience on the company's configuration management server as a file material for future queries on this project.

 

4. You can crop baseline creation documents, configuration auditing, and other configuration management documents.

 

5. documents related to risk management can be tailored to a Risk Management list document for tracking and management.

 

6. if the company has independent ppqa personnel, the inspection of the process and product quality assurance can remain unchanged, but if there is no independent personnel, this part can be cropped, but the outline design and detailed design cannot be cropped, at least one document should be provided. Although the demand changes greatly change the two documents, the two documents can avoid the project handover problem caused by the flow of developers and provide a basis for testing, if demand changes are well managed, the overall advantages and disadvantages are greater than the disadvantages. You also need to review and cross-review the development overview design, detailed design documents, and codes.

 

7. The measurement part can be cropped, because the measurement item needs to collect the measurement data based on various documents and personnel in the project development process, without the reliability of the measurement data in the document, there is no credibility, so you can crop it.

 

8. Decision Analysis and solutions can be tailored. Decisions and solutions can be discussed in the walkthrough meeting.

 

9. demand change-related documents cannot be tailored, and management of demand changes should be improved, because agile development emphasizes rapid response to changes, in actual projects, communication between customers and project personnel is insufficient for various reasons, while communication between testers and developers and customers is insufficient, therefore, it is difficult to achieve the core value of agile development for rapid response to changes. Therefore, the management of demand changes should be strengthened, and relevant documents should not be tailored.

 

10. Requirements management documents can be tailored, such as requirement Development Guide and requirement development files. The core value of agile development includes communication with customers over contract constraints, and communication with customers involves all aspects of the problem. Therefore, we must focus on multi-communication and iterative demand research, constantly explore potential demands. Therefore, the various documents of the Demand Survey can be tailored, but the analysis table of customer interview records should be clearly recorded, and a basic requirement specification must be provided at the end.

 

11. The product integration plan, Environment check list, and report can be cropped, but the interface list cannot be cropped, and cross-review should be performed on it.

 

12. In the test phase, the test plan can be cropped into a simple document, and the test cases should not be cropped. If the project is all tested by one person, you can consider cropping the test cases and changing them to the test operation process records. However, if multiple people participate, the test operation records of the same person are poorly reusable. Therefore, it is recommended that you do not crop the test cases of the project where multiple people participate in the test. You can use the Bug management tool to track and manage bugs, test reports cannot be cropped.

 

13. documents related to the OPF and OPD process fields can be cropped, because there is no reliable data to pursue and the documents have no practical significance.

 

14. OT and Sm-related documents can be tailored as appropriate.