T-76.115 Project Review Groupname [PP|…|DE] Iteration 30.10.2003

T-76.115 Project Review

Groupname[PP|…|DE] Iteration

30.10.2003

2

T-76.115 Project ReviewT-76.115 Project Review

Agenda

Project status (x min) achieving the goals of the iteration project metrics

Used work practices (x min) Completed work (x min)

presenting the iteration’s results demo

Plans for the next iteration (5 min)

This template contains the minimum set of topics covered in the reviews, you may add new slides, but consider the available time

3


Status of planned goals of the iteration

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 …

4


Status of planned deliverables of the iteration

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

5


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)

Tip!• Ctrl+Alt+PrintScrn in Trapoli• Ctrl+V in PowerPoint• Use Crop (Drawing toolbar)

6


Working hours by person

Explain the reasons for major discrepancies in realizations

Explain the reasons for changes in the plan

Real Plan DiffMember1 23 34 -11M2 24 34 -10M3 25 30 -5M4 26 24 2M5 27 23 4M6 26 24 2M7 25 32 -7Total 176 201 -25

Realized hours in this iteration Plan in the beginning of this iteration

PP Subtot I1 I2 I3 DE TotalM1 50 50 34 60 60 50 190M2 22 22 34 60 60 20 190M3 23 23 30 60 60 20 190M4 24 24 24 60 60 20 190M5 25 25 23 60 60 20 190M6 26 26 24 60 60 20 190M7 16 16 32 60 60 20 190Total 119 119 201 420 420 170 1330

Latest plan (inc. realized hours and other updates)

PP I1 Subtot I2 I3 DE TotalM1 50 23 73 75 60 50 190M2 22 24 46 70 60 20 190M3 23 25 48 60 60 20 190M4 24 26 50 60 60 20 190M5 25 27 51 60 60 20 190M6 26 26 52 60 60 20 190M7 16 25 41 60 60 20 190Total 119 176 295 445 420 170 1330

7


Quality metrics

Description of blocker and critical bugs found and open other QA metrics

unit test coverage code reviews source code metrics ...

I1 I2 I3 DE TotalReported 10 75 85Closed 5 45 50Open 5 35

… 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.

Bug metrics

Blockers Critical Major Minor Trivial TotalTotal open 1 2 5 10 17 35This iteration reported

0 1 10 15 49 75

8


Quality assessment

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

Functional area Coverage Quality Comments

File conversions 2 Only few minor defects found, very efficient implementation.

GUI editor 0 Not started

Encoder 3 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:

= quality is good

= not sure

= quality is bad

9


Software size in Lines of Code (LOC)

Any remarks on this metric? lots of new functinality was implemented refactoring reduced LOC

PP I1 I2 I3 DETotal (NCLOC + COM) 0 1000 4000Comments (COM) 0 100 200

PP I1 I2 I3 DETotal – part A 0 1000 4000Com – part A 0 100 200Total – part B

Com – part B

Total – part C

Com – part C

Total 0 1000 4000Comments 0 100 200

… or make a more detailed table, where you can show per module LOCs, or proportion of real code vs. test code

10


Changes to the project

Any other major changes to the project, not yet discussed goals of the project goals of the coming iterations project organization requirements technologies …

11


Risks

How have you done risk management? What is the current situation regarding the risks?

materialized risks? new risks identified?

12


Work practices

How have you been using the planned work practices, what are the experiences of

mandatory practices: time reporting, version control, … personal SE assignments

not all in every review, but when there are some interesting findings etc. other practices

Are you going to adopt some new practices change the use of the current practices stop using some adopted practices

13


Example: Test-first approach (N.N.)

Test-first was adopted by 3 coders after short training by N.N. They used it first for all new code, but later only in modules x,y,z,

because … Metrics

the amount of unit test code is 1000 LOC (20% of total LOC) 80% of test code was written before the real code effort N.N. spent on preparing the adoption (reading about test-first, planning,

training) was 12h effort the team spent on learning the practice was 7h

Positive experiences …

Negative experiences it does not work when xxx because yyy

Overall the practice seems to be useful

In the next iteration the use of the practice will be slightly changed by adopting the JUnit tool

…

14


Results of the iteration

Briefly describe the substance of the major deliverables of the iteration, e.g., the following in the relevant iterations (avoid repeating the stuff you have already told in project status and concentrate on elaborating what was done)

project plan requirements system architecture implemented use cases (will be demonstrated later) user’s manual studies made

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

15


Example: Project plan

Background of the project Project organization Project goals Project resources Project practices and tools Iterations Risk management plan …

16


Example: Demo

System Administrator function X function Y …

Basic user function Z1 function Z2 …

17


Plan for the next iteration

Goals Goal 1 Goal 2 Goal 3 ... Goal N

Deliverables Deliverable 1 Deliverable 2 ... Deliverable N

Priorities between goals Risks / uncertainties

Schedule task dependencies internal deadlines

Documents

T-76.115 Project Review Groupname [PP|…|DE] Iteration 30.10.2003