Iteration 2
Overview¶
Update on Mar 11
The deadline for Iteration 2 is moved to Mon, Mar 23, 2020, at 11:00 AM.
Note
For this iteration, we want you to get a bit more done compared to the last one; you need to pick up pace and build momentum.
These are the deadlines for this iteration.
| Day | Date | Time | |
|---|---|---|---|
| Update Requirement Specification Document | Sun | Mar 01 | 11:00 PM |
| Retrospective for iteration 1 | Sun | Mar 01 | 11:00 PM |
| Upload Design and Planning Document | Mon | Mar 02 | 11:00 PM |
| Revise Design and Planning Document | Thur | Mar 05 | 11:00 PM |
| Deliverable (source code of a working app) | Mar |
11:00 AM |
Update Requirement Specification Document¶
After iteration 1, you may want to update the Requirement Specification Document. This is a common practice; after each iteration you will go back and refine the User Stories. If you are going to make a critical change (that affects the scope of your work), please make sure the instructor (As well as your advisor) is aware of it.
Note
You only need to update the Requirement Specification Document if you want to make any changes to the specification of your proposed software project. That is, you can leave it as is, if you are happy with it.
Retrospective for iteration 1¶
You must add a "Retrospective" section to the end of your "Design and Planning Document" for iteration 1. The retrospective is an opportunity for your team to inspect itself and create a plan for improvements to be enacted during the next iteration. Review what you had done in iteration 1; note things that you have and have not delivered, note the challenges you had, and reflect on how you shall proceed in the next iteration to do a better job.
The "Design and Planning" Document¶
Add it2_dap.md file to your repository. The file contains the same sections as it2_dap.md, namely:
- A UML class diagram reflecting the "model" for iteration 2.
- A wireframe of your user interface (only what you will build in iteration 2)
- Iteration Backlog (list the User Stories that you will implement in this iteration).
- Tasks (a tentative list of the "to do" in order to successfully complete this iteration).
When you meet again with your group on Thur, Mar 05, you may want to update the "Design and Planning" document to reflect the changes you make.
Final Deliverable¶
At the end of iteration 2, you must deliver a software that does what you have listed in the iteration backlog.
You must always keep your group repository updated with the latest changes; we will consider your last commit by Thur, Mar 12, 11:00 AM as your submission.