robertyac
commented
5 months ago - [ ] - How many of your initial requirements that your team set out to deliver did you actually deliver (a checklist/table would help to summarize)? Were you able to deliver everything or are there things missing? Did your initial requirements sufficiently capture the details needed for the project?
- [ ] - If you have any requirements unimplemented, you will want to include an extra section showing those requirements have not been implemented.
- [ ] - If you have a requirement that is partially working but feel that there's enough you don't want to call the whole requirement as incomplete, then break it up into two requirements, with one shown as tested and working, while the other is shown as not working.
- [ ] - How many tasks are left in the backlog?
- [ ] - What is the architecture of the system? What are the key components? What design patterns did you use in the implementation? This needs to be sufficiently detailed so that the reader will have an understanding of what was built and what components were used/created. You will need to reflect on what you planned to build vs what you built.
- [ ] - What degree and level of re-use was the team able to achieve and why?
- [ ] - Indicate any known bugs in the software.
- [ ] - Explain how these bugs can be fixed.