CS-C2130 - Software Project 1, Lecture, 6.9.2023-1.12.2023
This course space end date is set to 01.12.2023 Search Courses: CS-C2130
Project Reviews
Overview
The course arranges three Project Reviews, where the student team presents the project status (see the Progress/Final report) and results (software demo and any other results) to the course personnel (Coach and teacher), PO, and possibly other stakeholders. After the review, the Coach and PO will evaluate the team according to the Evaluation principles.
The teacher will create the schedule for the Project Review days several weeks before the reviews. The schedule limitations of the students and POs must be listed on the "CS-C2130 Google Sheet" before that. The absence of some students is accepted, if the participants can answer all project related general questions.
Agenda
- Presentation (35 min), Students
- Questions and feedback (10 min), PO & Course personnel & Students
- Private discussion on evaluation (10 min), PO & Course personnel
- Points and further feedback from PO (5 min or more), PO & Students
Content of the Presentation
The team must create a presentation according to the Progress/Final report slide set template. It must contain at least:
- summary of the results of the Sprints: Sprint Goals, Product Backlog items, and other results
- main findings from the Sprint Retros
- a script for and some screenshots of the software demo
- evaluation of software quality
- spent effort per person per Sprint
Furthermore, in the last Project Review the presentation must contain also:
- peer team's feedback
- realized project scope vs. original/updated product vision
- complicating and simplifying factors compared to other projects on this course
- evaluation of the used work practices and tools
Submitting Materials before Project Reviews
The team must submit certain materials before each Project Review. Collect the required materials to a web page both separately and as a zip package. Send the web page link by e-mail at the latest 24 hours before the review to the 1) teacher, 2) Coach, and 3) PO.
Do not include any confidential material to the web page, because the link will be published in MyCourses.
If some materials cannot be linked to the web page (e.g. the backlogs are in some tool, if a document is confidential etc.), mention the reason, and provide instructions to the Coach for accessing it.
Ending one of the Sprints close to a Project Review simplifies reporting.
The required materials are:
- Product vision (see Template)
- Product Backlog
- Sprint Backlog of the current Sprint
- Process overview (see Template)
- Definition of Done
- Technical overview
- Progress / Final report slides (see Template)
- Test session charters and logs related to peer testing (when needed)
- Learning diary (submitted individually by each student to MyCourses)