1. Groupname [PP|…|FD] Iteration 1.11.2004
T Project Review
Groupname
[PP|…|FD] Iteration

2. Agenda Project status (x min) Work results (x min)
achieving the goals of the iteration
project metrics
Work results (x min)
presenting the iteration’s results
demo
Used work practices (x min)
This template contains the minimum set of topics for the review.
This slide set should also serve as the progress report. It may contain slides with additional information, that you don’t even intednd to show due to limited time allocated for the presentation

3. Introduction to the project
Show this slide when there are new people in the review.
What is this project about?

4. Status of the iteration’s goals
Goal 1: Specify the goals of the project from all perspectives OK
Goal 2: Select and adapt work practices to be used in the project
NOT OK, because …
Goal 3: Make the contract with the customer
DISCARDED/ MOVED LATER, because …

5. Status of the iteration’s deliverables
Project Plan
OK, except chapter 1.3, because …
Requirements document
OK, most important requirements in general, and sub system X in detail
Use cases 1,3,6,12,15 implemented and tested OK

6. Realization of the tasks
Explain the reasons for major discrepancies
estimation problems
new/deferred tasks
unplanned work
Tip!
Ctrl+Alt+PrintScrn in Trapoli
Ctrl+V in PowerPoint
Use Crop (Drawing toolbar)

7. Working hours by person
Realized hours in this iteration
Real
Plan
Diff
Member1 23 34
-11 M2 24
-10 M3 25 30 -5 M4 26 2 M5 27 4 M6 M7 32 -7
Total
176
201
-25
Explain the reasons for major discrepancies in realizations
Explain the reasons for changes in the plan

8. Working hours by person
Realized hours in this iteration
Plan in the beginning of this iteration
Real
Plan
Diff
Member1 23 34
-11 M2 24
-10 M3 25 30 -5 M4 26 2 M5 27 4 M6 M7 32 -7
Total
176
201
-25 PP
Subtot I1 I2 FD
Total M1 50 34 60
190 M2 22 20 M3 23 30 M4 24 M5 25 M6 26 M7 16 32
119
201
420
170
1330
Latest plan (inc. realized hours and other updates)
Explain the reasons for major discrepancies in realizations
Explain the reasons for changes in the plan PP I1
Subtot I2 FD
Total M1 50 23 73 75
190 M2 22 24 46 70 20 M3 25 48 60 M4 26 M5 27 51 M6 52 M7 16 41
119
176
295
445
170
1330
Use may present graphs instead of tables!

9. Quality metrics
Bug metrics I1 I2 I3 DE
Total
Reported 10 75 85
Closed 5 45 50
Open 35
Blockers
Critical
Major
Minor
Trivial
Total
Total open 1 2 5 10 17 35
This iteration reported 15 49 75
… or make a more detailed table/graph, where you show per module bugs, and/or classifications per criticality, origin (own system testing, code reviews, customer, peer group) etc.
Description of blocker and critical bugs found and open
other QA metrics
unit test coverage
code reviews
source code metrics
...

10. Quality assessment J K L
Functional area
Coverage
Quality
Comments
File conversions 2 J
Only few minor defects found, very efficient implementation.
GUI editor K
Not started
Encoder 3 L
2 critical bugs found during last test round, lots of small problems
Admin tools 1
Nothing serious yet
Legend
Coverage:
0 = nothing
1 = we looked at it
2 = we checked all functions
3 = it’s tested
Quality:
J = quality is good
K = not sure
L = quality is bad
Evaluate the quality of the different functional areas of the system
how much effort has been put on test execution
what is the coverage of testing
what can you say about the quality of the particular component based on your test results and ’gut feeling’ during testing
is the number of reported bugs low because of lack of testing or high because of intensive testing
Assess the quality status of the system against the goals of the iteration

11. Software size in Lines of Code (LOC)PP I1 I2 I3 DE
Total (NCLOC + COM)
1000
4000
Comments (COM)
100
200
… or make a more detailed table, where you can show per module LOCs, or proportion of real code vs. test code PP I1 I2 I3 DE
Part A Total/com
500/90
3000/100
Part B
500/10
1000/100
Part C
Part D
Part E
Total (NCLOC + COM)
1000
4000
Comments (COM)
100
200
Any remarks on this metric?
lots of new functinality was implemented
refactoring reduced LOC

12. Changes to the project
Any other major changes to the project, not yet discussed
goals of the project
goals of the coming iterations
stakeholders
requirements
technologies …

13. Risks What is the current situation regarding the risks?
materialized risks?
new risks identified?

14. Results of the iteration
Briefly describe the most important substance of the major deliverables of the iteration, e.g., the following
project plan (especially in PP review)
requirements (especially in PP review)
system architecture (especially in I1 review)
QA approach (especially in I1 review)
implemented use cases (I1-FD)
user’s manual (especially in I2 review)
Demonstrate the developed software
first tell briefly to the audience what you are going to demonstrate (perhaps distribute a demo script to the audience)
concentrate on new functionality in each review
Avoid repeating what you have already told in project status and concentrate on showing the concrete results.

15. Example: Project plan Present the following
Stakeholders and staffing (a diagram?)
Project goals (discuss most important goals and verification criteria)
Project resources (already shown in the project status?)
Project practices and tools (discuss most important practices and tools you have chosen, what, why, when, …)
Discuss phasing if there are some major plans already

16. Example: Demo script System Administrator Basic user function X
function Y …
Basic user
function Z1
function Z2

17. Used work practices
How have you been using the planned work practices, what are the experiences of
mandatory practices: time reporting, version control, …
SEPAs
other practices
Are you going to
adopt some new practices
change the use of the current practices
stop using some adopted practices
Short explanation of all important practices, tell more if is something very interesting has been found.