The tP spans ten weeks, and is to be done in breadth-first iterative fashion.
The first portion of the tP will be spent of laying out the foundation for the iterations, as illustrated below. This portion of the tP is light because you will be doing the individual project (iP) in parallel during this time.
Note: that the diagrams above show the relative size of tasks i.e., smaller tasks are shown as shorter bars
Week 3 Kickoff
- Form teams.
- Set weekly meeting times.
Week 4 Set direction
- Decide on a general direction for the project (i.e., target user profile, and problem addressed).
Week 5 Gather requirements
- Gather requirements in the form of user stories.
- Decide which of them will go into the first version.
Week 6 Define MVP, set up repo
- Decide how the MVP version of the product will look like (i.e., v1.0).
- Record that product concept in the form of a user guide.
- Set up the development environment.
The second portion of the tP is divided into multiple iterations, each of which is expected to produce a working version of the product by evolving the product delivered in the previous iteration.
Week 7 Plan the iteration
- Plan the next iteration i.e., decide who will do which parts by when.
- Proceed to start the iteration early, if possible.
W8 W9 Iteration 1 → v1.0
- This is the first proper iteration.
- Aim to deliver an version of the product.
W10 W11 W12 Iteration 2 → v2.0
Note: This iteration is given an extra week, to account for the holidays in the middle.
- This version will be tested by peers, and you will receive the bug reports without any penalty.
- Aim to deliver all so that you can get them tested for free.
W13 Iteration 3 → v2.1
- This iteration is very short (just 2-3 days).
- Recommended to use it only for bug fixing, and wrapping up the final deliverables.