Regular Project Status Review

Regular Project Status Review

The Software Project Status Review (sometimes referred to as the management evaluation) can provide necessary information for the relevant parties of the project to make further decisions or approvals based on the situation, and track the implementation of previous reviews. For a project that is restarted after the rescue, the project status review is part of the EWS for the same purpose. This review can provide information about the project status, identify and monitor existing problems and their solutions, and ensure that key problems are resolved.

Project Reviews are mainly based on data, which can explain the importance of data collection for development metrics. If data collection is missing, project evaluation becomes worthless. This is from12.1The first evaluation in the case above can be seen (the only value of this evaluation is to ensure that the next evaluation can be done better ).

Project evaluations should be conducted periodically, usually once a month. In special cases, however, the frequency can be increased (for example, once every two weeks) or occasionally decreased (once every two or three months ). Too many project evaluations impose additional burden (each evaluation and preparation work requires considerable time and effort). However, if the evaluation frequency is too low, the problem backlog cannot be effectively solved.

How should the evaluation be conducted? There are many related standards in this regard. One of the examples isIEEE Std 1028This standard covers a broad range of project evaluations (including management evaluations and technical evaluations ). Although these different types of evaluations can be customized flexibly based on the situation, for a development organization that only has a limited software development process, if a variety of different types of evaluations are introduced, that would be a heavy burden. Fortunately, the project that has gone through the disaster recovery process and restartedEWSSystem not requiredIEEEAll evaluation content specified in the standard.

In the previous section, we have discussed how to introduce metrics in a disaster-prone project, and how to review the introduction of technologies: you only need to introduce the elements that are essential for the successful completion of the saved project during the review process (of course, if the current development organization is already using an effective and more comprehensive evaluation technology, so continue to use them ).

Next, we will discuss how to integrate a General Project Evaluation Standard (for exampleIEEEProject evaluation criteria) changed to the version (other criteria, suchISOThe project evaluation standards can also be customized and modified ).

1 . Project Status (Management) Review

IEEEThe standards cover various types of software project reviews: management evaluation, technical evaluation, review, inspection and audit. For a project that falls into a disaster, itsEWSThe minimum requirement of the system is management evaluation. The purpose of the management evaluation is clearly defined in this standard: "To monitor the software development process, identify the status of the implementation of the current plan, and confirm the Needs and Resources configured for them, evaluate the effectiveness of the current management method. Management evaluation can effectively support decision-making on corrective actions, resource configuration changes, or project scope changes ." This goal is fully in line with the project that falls into disasterEWSSystem needs.

2 . Review participants

The current project review requires the participation of the following parties.

Key management decision makers

Reviewer (person presiding over the review process)

Recorder (record major events and decisions during review)

Project Manager

Technical staff

Other project members

Customer or customer representative (optional)

Other individuals can also be invited to participate in the discussion based on actual needs.

3 . Duration of evaluation

Based on the project scale and status, the evaluation should take two hours to one day.

A large project or project with many problems may take a whole day to complete the evaluation, but for small projects (less15Person/Year) or a project that has no major problems, the evaluation may take about two hours.

4 . Agenda for evaluation

IEEEThe standards cover various topics in the evaluation. For a saved and restarted project, these topics can be reduced to the following.

1. Overview: includes the evaluation overview, scope, and objectives.

2. The progress report of the operations identified by previous evaluations.

3. Discuss existing urgent issues.

4. Project status and progress, including:

Progress

Budget

Staffing

Development Progress

Software defects

Other related questions

5. Problems and Solutions of project management, including risks.

6. Resolution and approval.

7Measures to be taken (including actions, executors, and deadlines for completion ).

5 . Prepare

IEEESoftware Evaluation Criteria1028It is both a standard and a guide. It includes preparations before the evaluation (for example, an appropriate place should be provided for the evaluation), evaluation plans (such as schedules and conference presentations, distribution of relevant materials ), and Evaluation execution (for example, establishing an evaluation lead and recording the evaluation process ).

 

This article is excerpted from disaster recovery--Bringing software projects back to track

[Us] Bennatan(Benana) By

Translated by Hou yanfei, Hou yufang, and Li Meng

Book details: Http://blog.csdn.net/broadview2006/article/details/7719723