Project Review Team name 26 10 2017 Agenda

  • Slides: 11
Download presentation
Project Review Team name 26. 10. 2017

Project Review Team name 26. 10. 2017

Agenda q Sprints q q q q q Sprint Goals Product Backlog Items, other

Agenda q Sprints q q q q q Sprint Goals Product Backlog Items, other results Main findings from the Sprint Retros Software demo Software quality Spent and remaining effort person per Sprint Realized project scope (Final report only) Complicating and simplifying factors (Final report only) Used work practices and tools (Final report only) Presentation: max. 35 minutes. This template contains the minimum set of topics for a Project Review. These slides should also serve as the Progress/Final report. You may include slides with additional details, that you don’t even intend to show during the max. 35 min presentation. 2

Introduction to the project q What is this project about? q Max. 3 minute

Introduction to the project q What is this project about? q Max. 3 minute summary Show this slide when there are new people in the audience. 3

Sprint N q Sprint Goal: “xxx” (OK / NOT OK & why? ) q

Sprint N q Sprint Goal: “xxx” (OK / NOT OK & why? ) q Product Backlog Items chosen to this Sprint q q x, y, z (OK) w (NOT OK & why? ) q Other notable achievements q Main findings from the Sprint retro q If time allows, you can present some content of the Other notable achievements. What worked, what didn’t work, what will be changed Present only the Sprints that have been completed after the previous Project Review. 4

Sprint N+1 q See previous slide If you have had many short Sprints, you

Sprint N+1 q See previous slide If you have had many short Sprints, you can present them as larger wholes instead of separately. 5

Software Demo q Demo script that helps the audience to follow the demo q

Software Demo q Demo script that helps the audience to follow the demo q q q System Administrator q function X 1 q function X 2 q … Basic user q function Z 1 q function Z 2 q … Some screenshots of the demo for people, who do not participate the review, but read these slides 6

Software Quality q List of the most important quality attributes q q q Definition

Software Quality q List of the most important quality attributes q q q Definition of Done q q main content how well it has been followed? has it changed? What has been done to achieve high quality? What is the current state of quality? Quality metrics q q q e. g. performance, usability, compatibility, … possibly some quantification of the desired level Which aspects of quality are most important for this software? e. g. known defects, test coverage metrics status of the important quality attributes q and is the status evaluation based on some measured data? Peer team’s feedback (Final report) 7

Spent and Remaining Effort M 1 M 2 M 3 M 4 M 5

Spent and Remaining Effort M 1 M 2 M 3 M 4 M 5 M 6 M 7 SUM Sprint 0 40 35 35 20 20 35 35 Xxx Sprint 1 20 40 40 55 55 40 40 Xxx . . . . 20 40 40 25 25 40 40 xx 100 225 225 225 xxxx … Sprint N Total (realized hours and remaining hours) You may present graphs instead of tables! 8

Realized Project Scope vs. Original/Updated Product Vision (Final Report) 9

Realized Project Scope vs. Original/Updated Product Vision (Final Report) 9

Complicating and Simplifying Factors (Final Report) q Compare your project to those of the

Complicating and Simplifying Factors (Final Report) q Compare your project to those of the other teams q Complicating factors q q used technologies were new to all team members understanding the problem domain took lots of time … Simplifying factors q q most of the team members knew each other before the course … 10

Overall Evaluation of the Used Work Practices and Tools (Final Report) q Which practices

Overall Evaluation of the Used Work Practices and Tools (Final Report) q Which practices and tools worked well, which didn’t? Why? In the presentation you have time to discuss only the most interesting experiences. The Coach will read the rest of the material from the slides. 11