Sprint 4: Final Review
Your final iteration is meant to complete all of your planned features! You should be code-complete after this, and produce a software release for your final submission.
Requirements
For this sprint, you should complete the following:
- Any remaining requirements from previous demos.
- Feedback from Demo 3 should have been addressed.
- All remaining features that you included in your project proposal.
- Unit tests completed for all features, including anything new you implemented.
- All features required by a software release including documentation.
Submission
After the demo, you will need to ensure that your work is complete so that it can be graded. This means that all documentation should be updated (issues, wiki pages, team meeting minutes), and all source code should be frozen (changes pushed, everything merged to main).
The deadline is 6:00 PM on the listed time and date. You do not need to actually submit anything; we will grade what is posted in your GitLab project at the deadline.
The content that is in GitLab should be the same as what you presented in-class. You are allowed to make small corrections but please avoid making major content changes between the demo and the submission.
Grading
The grading scheme is available in Learn under Resources > Rubrics.
Deliverables are normally graded by the following week’s lecture, and the grade and feedback will be posted under Submit > Dropbox. Any questions related to this should be sent directly to your TA.
See grading policies for more information.
| Component | Items | Marks |
|---|---|---|
| Project | The project builds and runs using ./gradlew from the command-line. |
1 |
| Issues and project documents are up-to-date. | 1 | |
| Features | Sprint goals were met. Details TBD. | 5 |
| Progress was made on custom or advanced features. | 2 | |
| Unit tests were created for new features, and pass. | 1 | |
| Total | / 10 |