Project: | PROJECT-NAME |
---|---|
Status Report Date: | YYYY-MM-DD |
Next Internal Release Number: | X.Y.Z |
Release Date: |
Original estimate: YYYY-MM-DD
Current estimate: YYYY-MM-DD
Change Since Last Report: No change
Change Since Last Report: Slipped 2 days
Change Since Last Report: Saved 4 days
|
Resources used this period: |
PERSON-NAME: 18 hours.
PERSON-NAME: 15 hours.
PERSON-NAME: 10 hours.
PERSON-NAME: 12 hours.
|
Status Summary: |
Project completed. This is the final status report.
Low risk. Project on track.
Medium risk. Problems are being dealt with.
High risk. Advice from management and stakeholders needed.
Project canceled. This is the final status report.
|
Related Documents: |
This week we focused on...
Two major problems have been uncovered...
We are approximately 30% of the way through the project plan, and running about 2 days ahead of schedule...
The reason for the change in estimated release date is...
We recommend changing the schedule or WBS to add...
To stay on schedule, we have slipped enhancements issue 92, issue 101, and issue 129 to a later release. These issues were selected because ...
Completion of COMPONENT is on hold until we hear back from DEPARTMENT-TEAM-OR-VENDOR.
This week team members spent a total of 6 hours on TIME-WASTING-TASK and were re-tasked to work on COMPETING-PROJECT for 8 hours.
Metric | Description | Expected Value at Release | Current Value | Comments |
---|---|---|---|---|
Open issues | Known issues requiring developer work | No high priority issues | ||
Resolved issues | Fixed issues that must still be verified | No high priority issues | ||
Closed issues | Issues completely done | N/A | ||
Code written | New code for new features | 100% | 80% | |
Unit test coverage | Statements exercised in unit tests | 100% | 30% (up 9%) | Starting with business objects first |
Unit tests passed | Unit tests that we currently pass | 100% | 90% (up 17%) | Still failing some file import tests |
Performance results | Seconds needed for 1 million records | 20 | 57 | Only simple optimizations have been done so far. |
QUALITY-GOAL | DESCRIPTION | CRITERIA-FROM-SRS-OR-QA-PLAN | CURRENT-VALUE | NOTE, QUESTION |
Step | Description | Planned Hours | Spent To-Date |
---|---|---|---|
1. | Preparation | ||
1.1. | Developer training | 60 | 0 |
2. | Inception | ||
2.1. | Requirements gathering | 60 | 0 |
2.2. | Requirements specification | 40 | 0 |
2.3. | Requirements validation | 20 | 0 |
3. | Elaboration | ||
3.1. | High-level design | 10 | 0 |
3.2. | Low-level design (break down by component) | ||
3.2.A. | Object design | 20 | 0 |
3.2.B. | User interface design | 20 | 0 |
3.2.C. | Database design | 6 | 0 |
3.3. | Design review and evaluation | 10 | 0 |
4. | Construction | ||
4.1.A. | System implementation | ||
4.1.A.1. | Implement Component 1 | 50 | 0 |
4.1.A.2. | Implement Component 2 | 50 | 0 |
4.1.A.3. | Implement Component 3 | 50 | 0 |
4.1.A.4. | Implement Component 4 | 50 | 0 |
4.1.A.5. |
Integrate Components
(mostly done during component implementation)
| 5 | 0 |
4.1.B. | Technical documentation (break down by component) | 20 | 0 |
4.1.C. | User documentation (break down by component) | 40 | 0 |
4.1.D. | Testing | ||
4.1.D.1. | Test planning | 20 | 0 |
4.1.D.2. | Test code implementation (break down by component) | 60 | 0 |
4.1.D.3. | Test execution | 30 | 0 |
4.2. | Implementation review and evaluation | 20 | 0 |
5. | Transition | ||
5.A. | Release packaging | 8 | 0 |
5.B. | Documentation for other groups | 6 | 0 |
6. | Reflection | ||
6.1. | Postmortem report | 20 | 0 |
Total |