- Set up the project repo during the tutorial
- Plan the next iteration
1 Set up the project repo during the tutorial
- Set up the team org, the team repo, and individual forks as explained below:
2 Plan the next iteration
- Plan the next iteration. As you know, you should follow the breadth-first iterative process. Therefore, first you must decide what functionalities should be in the product if you had only two weeks to implement it. You have done that already when you chose user stories for v1.0, translated that to features, and even drafted the UG based on those features. You can tweak that plan further at this point if you wish, given that you now have some idea of how fast the team can work when using the prescribed workflow.
- Aim to produce a working MVP at the end of this iteration even if the functionalities are not polished (polishing can be done in a later iteration).
- [Recommended, Optional] Break the iteration into two increments i.e., aim to produce an even simpler but working version after one week.
- Avoid depth-first implementations: "I'll do the back-end part of feature X in this iteration" is not acceptable as that is not in the spirit of breadth-first iterative process. Remember, we are pretending this to be the last iteration; why would you implement the back-end part of a feature in the last iteration?
It is OK to add simpler versions of bigger features, but not OK to add partial features that can't be used yet.
- Divide the work among the team members i.e., the work required for the current iteration.
- Reflect the above plan in the issue tracker by assigning the corresponding issues (create new issues if necessary) to yourself and to the corresponding milestone. For example, the user story pertaining to the increment
show a place holder for photo, showing a generic default imageshould be assigned to Jake and to milestonev1.0
If you split the iteration into two smaller iterations of one-week each (recommended), name the first onev1.0and the second onev1.0bso that the dashboard can track them accurately. The reason for naming the earlier milestone asv1.0is so that even if you fail to finish the second one, you can still get credit for reachingv1.0(which is the milestone tracked by grading scripts) -- think of the first iteration as minimal deliverables forv1.0and the second one as containing do-if-there-is-time improvements.