Release judgment criteria・To check the development management, first look at the development plan
The quality of the development management process is judged by comparing the plan and the actual results.
What kind of items should be viewed from what point of view in order to judge the quality of the development management process in the release judgment? If you have good metrics, you can quantify them to judge whether the development management process is good or bad, but there are not many convenient metrics. Therefore, Gutara’s father becomes a qualitative method, but he decides on six important development management processes, and looks at the status of those process from the following two perspectives, and whether there are any problems or not. I was judging badness.
- Are there any omissions or problems in the development plan?
- Are the planned individual management processes implemented successfully?
Plans and performance are confirmed in six important development management processes
As an important development management process, Father Gutara was paying attention to the following six processes.
- Development planning
- Software design and implementation
- Test planning
- Management of concerns and risks
- Baseline management
- Maintenance system and maintenance contract
- Implementation status of the gate process
Also, although it overlaps with the important management process, the fact that the gate process is being carried out steadily was also a point to be careful when checking the status of the management process. I will explain the gate process later, so let’s first introduce the important development management process in order, what points were confirmed in terms of both planning and implementation.
1. 1. Development planning
The most important thing for software development is the development plan . If there is no development plan, it will be a problem before considering the quality of the process, so here we will proceed on the assumption that there is a development plan. In reality, some projects may not have a development plan, but in such cases, please do your best to make a development plan.
Since the contents of a development plan are usually written out as a development plan, the quality of the development plan planning process can be judged by looking at the development plan. Then, what kind of items should be included in the development plan?
There are various ways to write a development plan, so this is not the correct answer, but Father Gutara checked whether the following items were specifically written in the development plan.
(1) Scope of development, division and responsibility
In the development plan, the scope of this development must first be described concretely. There are various processes in software development. To give an example along the software wife cycle, product planning / requirement specification design / structural design / functional design / detailed design / implementation / unit test / integration test / system test / validity verification / release / maintenance. Is it?
In these processes, it is not possible to know what to do unless it is clearly stated which ones are included and which ones are not included in this software development project .
It is also important that the person in charge is clear about important processes such as required specifications and basic software design and testing.
(2) List of concerns and risks
Have noticed at the stage you are considering a development plan pending ( already occurred to have problems) and the risk it is also important (to occur in the future problems) have been written have been organized. As development progresses, it is important to take measures against concerns and risks in parallel with individual development work, so first we checked whether the concerns and risks were written out in the development plan.
(3) Process chart that shows milestones that are points of cooperation with other departments
A process chart is indispensable , but it is not possible to manage the progress of a process with a process chart that has only one line for development work. The process chart should have at least the important milestones , and the particle size should be such that the progress or delay of the progress can be seen in the achievement status of the milestones .
For example, what month and what day will the basic design be completed, what month and what day will the implementation be completed, what time will the system test start, and what month and what day will the release be determined? It is necessary to know the specific schedule for milestones such as “Is it?"
At the same time, it is important to clarify the milestones that align with other departments related to software development . For example, in the case of a software development plan for products manufactured at a factory, the date when the final version of the software is provided to the factory production line affects the processes of other departments, so it is also important as a milestone in software development. ..
Also, when hardware and software development are in parallel, such as in the initial development of a new product, the timing and quantity at which the first hardware product is provided to the software development team is very important. This milestone will be the starting point for starting real-world testing and will have a significant impact on the testing and debugging process.
The itinerary must also specify milestones to work with these other departments . We were checking to see if these important milestones were also specified in the line chart showing the start and end of the process.
(4) Method and purpose of process control and quality control
Process and quality are important controls. For these two, specific management methods and target values must be written in the plan.
In the process progress management example, if it is not clear at the beginning what tool is used to manage the process , the progress of the work cannot be known.
Gantt chart or make, the work list, such as those in Table WBS (Work Breakdown Structure) should I use, some kind of whether to use the progress management system, have been described is the selection of tools to use for progress management, it what Frequently (weekly or biweekly), it would be better if there was a concrete plan of who would fill in the process results, who would check the process progress, and who would take measures when a delay occurred. It is safe.
In the quality control example, what quality control metrics (software quality indicators) should be used for quality control should be clear at the beginning of development.
For example, what metrics are used in each development phase, such as monitoring the rate of review indications in the design stage, monitoring the number of code modifications in the implementation stage, and checking the bug density in the testing stage. It must be decided whether to monitor the quality of the software.
Then, as with process progress management, at what frequency (weekly or biweekly), who collects quality performance, who confirms quality performance, and who takes measures in the event of quality deterioration ? It is more secure if the plan is described.
(5) Outsourcing management method
In software development, we often outsource part or all of the development process . It is often referred to as outsourcing , or outsourcing for short . We may outsource a part of the design, implementation, testing, etc., or we may outsource the entire development process from the creation of the required specifications to the testing.
It would be good if the outsourced work was delivered without any problems in terms of delivery time and quality, but it would be difficult if the outsourced work was not completed or the quality was insufficient at the time of delivery. So as not to be that way, work with subcontractors monitor and manage the status of the progress and the quality Tsutomu you need to.
In order to management and monitoring of the subcontractors to function properly is, between a contractor and a commission source their organization outsourcing, mutual responsibility is clear and has become, specific monitoring and management The method must be decided.
There are various methods for monitoring and managing outsourced operations. For example, you can hold a regular meeting once a week to have the business status reported on the process chart or issue management table, or have the business status report submitted once a month . Various methods can be considered depending on the rules and customs.
It doesn’t matter what method you use , but the business plan must state what method you will use to monitor and manage the outsourced business .
As mentioned above, if the important items for the software development project are specifically described in the development plan, it can be judged that the plan is being considered properly.