(a) You should have a working system that the customer as well as
the instructor and the TAs can run without complications. You will be
asked to show your code and the tests you wrote for the implemented
features. You will present the system to your customer on-demand.
(b) Submit a report that includes the following items:
- An updated version of the identified stories/tasks and their new
priorities. Highlight stories/tasks that were implemented, and
stories/tasks that are yet to be implemented. Show how your
velocity was calculated and how you used it to plan for this
iteration.
- Pictures of your story board at different points in the
iteration (weekly snapshot).
- The results of the retrospective. List the issues identified,
and provide a discussion of the main issue you selected to
address. Elaborate on your action items and whether they
contributed to improving this iteration. Take a picture for every
stage in the retrospective.
- The individual efforts of each member. For example, John
implemented stories A and B, wrote the tests for stories A, B, C
and D, wrote section 3.1 in the report and reviewed sections 1 and
2.
- As usual, the report should be targeted to your customer and
should have already been "signed off" by the customer (your TA) in
the form of an attached critique of the report.
(c) Each member in the team should submit a peer-evaluation report.