T Iteration Demo Group name [PP|I1|I2] Iteration

T Iteration demo 2 Agenda  Project status (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 and should contain slides with additional details, that you don’t even intend to show due to limited time allocated for the presentation 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 Iteration demo 3 Introduction to the project  What is this project about?  3 minute summary Show this slide when there are new people in the audience.

T Iteration 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 Iteration 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 Iteration 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 RealizedPlanned Diff(Left) DEVELOPMENT Task Xok Task X.2*ok Task Yremoved …… ……… MANAGEMENT Task Zunfinished Total * unplanned task (= a new task added during the iteration) (A sample table)

T Iteration demo 7 Resource usage  Explain the reasons for major discrepancies in realizations  Explain the reasons for changes in the plan M1M2M3M4M5M6M7SUM PP I I Total Original plan (in the beginning of the iteration) Realization and updated plan You may present graphs instead of tables! (realized hours and updates) M1M2M3M4M5M6M7SUM PP I I Total

T Iteration demo 8 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. BlockersCriticalMajorMinorTrivialTotal Reported in Ix Reported total Open

T Iteration demo 9 Quality dashboard  Evaluate the quality of the parts of the system  how much effort has been put on QA practices  what is the coverage of testing  what can you say about the quality of a particular part 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 Part of the systemQualityConfidenceComments File conversions 2 Only few minor defects found, very efficient implementation. GUI editor  0Not started Encoder  3 2 critical bugs found during last test round, lots of small problems Admin tools  1Nothing serious yet Legend Confidence: (use your own scale) Quality: (use your own scale e.g.: 3 = quality is good 2 = not sure 1 = quality is bad

T Iteration demo 10 Quality goals  Evaluation of the status of the project's quality goals

T Iteration 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 PPI1I2 Total (NCLOC + COM) Comments (COM) PPI1I2 Part A Total /com 0500 / /100 Part B 500 / /100 Part C Part D Part E Total (NCLOC + COM) Comments (COM) … or make a more detailed table, where you can show per module LOCs, or proportion of real code vs. test code

T Iteration 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  …

T Iteration demo 13 Risks  What is the current situation regarding the risks?  materialized risks?  new risks identified?

T Iteration demo 14 Results of the iteration  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 Iteration demo 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

T Iteration demo 16 Example: Demo script  System Administrator  function X  function Y  …  Basic user  function Z1  function Z2  …

T Iteration demo 17 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.