T Project Review (Template for PI and I1 phases) Group name [PI|I1] Phase

T Project review 2 Agenda  Project status (10 min)  goals of the sprints, spent effort, quality, risks, changes  Experiences of work practices and tools (5 min)  Work results (25 min)  presenting the 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 PI/I1 project review. This slide set should also serve as the progress report. It may 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 PI/I1 project review. This slide set should also serve as the progress report. It may contain slides with additional details, that you don’t even intend to show due to limited time allocated for the presentation

T Project review 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 Project review 4 Status of the goals of the sprints  Sprint 1 goal: xxx  OK  Sprint 2 goal: xxx  NOT OK, because …

T Project review 5 Status of the deliverables of sprints  Use cases 1,3,6,12,15 implemented and tested  OK  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

T Project review 6 Effort spent - total  Explain the reasons for major discrepancies in realizations  Explain the reasons for changes in the plan M1M2M3M4M5M6M7SUM PI (s1) I1 (s2) I1 (s3) I2 (s4) Total Original plan (in the beginning of the phase) Realization and updated plan You may present graphs instead of tables! (realized hours and updates) M1M2M3M4M5M6M7SUM PI (s1) I1 (s2) I1 (s3) I2 (s4) Total

T Project review 7 Effort spent - analysis  Which activities / tasks were the main time sinks  Shortly discuss major discrepancies between the sprint plans and realizations

T Project review Status of quality goals and evaluation of the used quality practices Practice Main quality goals functionalityusability maintain- ability xyz test case based manual functional testing ***** unit testing with JUNit **** coding standard *** pair programming ** practice x 8 Quality: green = good yellow = moderate red = bad white = don’t know Effect: *** = large effect ** = moderate effect * = small effect = 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 Project review 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 SubsystemQualityConfi- dence Comments File conversions 21 Only few minor defects found, very efficient implementation. GUI editor 0 Not started Encoder 02 Carefully tested, 2 critical bugs found during last test round, lots of small problems. Admin tools 12 Nothing serious yet Quality: 2 = good 1 = moderate 0 = bad = don’t know Confidence: 2 = high 1= moderate 0 = low

T Project review 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. BlockersCriticalMajorMinorTrivialTotal Reported in Ix Reported total Open

T Project review 11 Software size in Lines of Code (or some better metric)  Any remarks on this metric?  lots of new functinality was implemented  refactoring reduced LOC PII1I2 Total (NCLOC + COM) … of which comments (COM) PII1I2 Part A Total /com 0500 / /100 Part B 500 / /100 Part C Part D Part E Total (NCLOC + COM) … of which comments (COM) … or make a more detailed table, where you can show per module LOCs, or proportion of real code vs. test code

T Project review 12 Changes to the project  Any other major changes to the project, not yet discussed  goals of the project  stakeholders  requirements  technologies  quality practices  other practices  …

T Project review 13 Risks  What is the current situation regarding the risks?  materialized risks?  new risks identified?

T Project review 14 Used work practices  How have you been using the planned work practices, what are the experiences of them  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 Project review 15 Results  Briefly describe the most important results, e.g., the following  project goals, work practices (especially in PI)  system overview, user groups (especially in PI)  system architecture (especially in I1)  QA plan (especially in I1)  implemented requirements (I1-I2)  Demonstrate the developed software  distributing a demo script to the audience helps following the demo Avoid repeating what you have already told in project status and concentrate on showing the concrete results.

T Project review 16 Example: Work practices  Discuss concretely the most important practices and tools you have chosen (what, when, by whom …)  Iterative development, sprint lengths etc.  …

T Project review 17 Example: Demo script  System Administrator  function X  function Y  …  Basic user  function Z1  function Z2  …