T-76.4115 Iteration Demo

Group name[PP|I1|I2] Iteration

27.7.2010

T-76.4115 T-76.4115 IterationIteration demo demo

2

Agenda Project status (10 min)

goals, tasks, effort, quality, risks, changes Experiences of work practices and tools (5 min) Work results (25 min)

presenting the iteration’s results demo

Comments and questions (10 min) Customer and mentor discuss privately on the evaluation (10min)

This template contains the minimum set of topics for the review. This slide set should also serve as the progress report. It may and should contain slides with additional details, that you don’t even intend to show due to limited time allocated for the presentation

T-76.4115 T-76.4115 IterationIteration demo demo

3

Introduction to the project What is this project about?

3 minute summaryShow this slide when there are new people in the audience.

T-76.4115 T-76.4115 IterationIteration demo demo

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 …

T-76.4115 T-76.4115 IterationIteration demo demo

5

Status of the iteration’s deliverables Project plan

OK, except chapter 1.3, because … Requirements document

OK, all important requirements documented in general level and reqs 1,2,3,... in detail

Use cases 1,3,6,12,15 implemented and tested OK

T-76.4115 T-76.4115 IterationIteration demo demo

6

Realization of the tasks Show status and effort distribution per task or task group

(not on too detailed level) discuss major discrepancies between the plan and realizations unfinished/removed tasks? any unplanned tasks?

Status Realized Planned Diff (Left)DEVELOPMENT

Task X ok 9 20 -11Task X.2* ok 22 0 +22Task Y removed 0 25 -25… … … … …MANAGEMENT

Task Z unfinished 12 10 +2 8Total 176 201 -25

* unplanned task (= a new task added during the iteration)

(A sample table)

T-76.4115 T-76.4115 IterationIteration demo demo

7

Resource usage

Explain the reasons for major discrepancies in realizations

Explain the reasons for changes in the plan

M1 M2 M3 M4 M5 M6 M7 SUMPP 60 60 60 60 60 60 60 420I1 40 40 40 40 40 40 40 300I2 50 50 50 50 50 50 50 500Total

150 150 150 150 150 150 150 1150

Original plan (in the beginning of the iteration)

Realization and updated plan

You may present graphs instead of tables!

(realized hours and updates)

M1 M2 M3 M4 M5 M6 M7 SUMPP 50 50 50 50 40 60 70 370I1 50 50 50 50 60 40 30 350I2 50 50 50 50 50 50 50 500Total 150 150 150 150 150 150 150 1150

T-76.4115 T-76.4115 IterationIteration demo demo

Status of quality goals and evaluation of the used quality practices

Practice Main quality goals

functionality usability maintain-ability x y z

test case based functional testing *** **unit testing with JUNit * ***coding standard ***code review * *

practice x

8

Quality:green = goodyellow = moderatered = badwhite = don’t know

Effect:*** = large effect** = moderate effect* = small effect<empty> = no effect

comments on the goals and practices, and changes to the plan, e.g. code review very useful, but was used only for 3% of code planned usability test was not done

T-76.4115 T-76.4115 IterationIteration demo demo

9

Quality status of subsystems

what can you say about the quality of a particular part based on your quality practices and ’gut feeling’

how reliable is your evaluation of the quality is the number of reported bugs low because of lack of

testing or high because of intensive testing

Subsystem Quality Confi-dence

Comments

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

GUI editor 0 Not started

Encoder 0 2 Carefully tested, 2 critical bugs found during last test round, lots of small problems.

Admin tools 1 2 Nothing serious yet

Quality:2 = good1 = moderate0 = bad<empty> = don’t know

Confidence:2 = high1= moderate0 = low

T-76.4115 T-76.4115 IterationIteration demo demo

10

Defects and other quality metrics

Description of blocker and critical bugs found and open

Other QA metrics performance analysis metrics usability test results source code metrics ...

Use this template 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.

Blockers Critical Major Minor Trivial TotalReported in Ix 0 1 10 15 19 45Reported total 2 2 20 25 25 74Open 1 2 5 10 17 27

T-76.4115 T-76.4115 IterationIteration demo demo

11

Software size in Lines of Code (LOC) (or some better metric)

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

PP I1 I2Total (NCLOC + COM) 0 1000 4000… of which comments (COM) 0 100 200

PP I1 I2Part A Total/com 0 500/90 3000/100Part B 500/10 1000/100Part C

Part D

Part E

Total (NCLOC + COM) 0 1000 4000… of which comments (COM) 0 100 200

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

T-76.4115 T-76.4115 IterationIteration demo demo

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 quality practices other practices …

T-76.4115 T-76.4115 IterationIteration demo demo

13

Risks What is the current situation regarding the risks?

materialized risks? new risks identified?

T-76.4115 T-76.4115 IterationIteration demo demo

14

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

experiences of mandatory practices: time reporting, version control, … any other practices

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

In the presentation you have time to discuss only the most interesting experiences and major changes. The mentor will read the rest of the material from the slides himself later.

T-76.4115 T-76.4115 IterationIteration demo demo

15

Results Briefly describe the most important content 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 plan (especially in I1 review) implemented use cases (I1-I2) user’s manual (I2)

Demonstrate the developed software first tell briefly to the audience what you are going to demonstrate

distributing a demo script to the audience helps following the demo concentrate on new functionality

Avoid repeating what you have already told in project status and concentrate on showing the concrete results.

T-76.4115 T-76.4115 IterationIteration demo demo

16

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 concretely the most important practices

and tools you have chosen, what, why, when, …) Discuss phasing if there are some major plans already

T-76.4115 T-76.4115 IterationIteration demo demo

17

Example: Demo script System Administrator

function X function Y …

Basic user function Z1 function Z2 …