University of Calgary
Rob Kremer
Iteration 2 Details

SENG 403: Software Development in Teams and Organizations
Winter 2012
Department of Computer Science
Computer
Science

What is to be done?

Identify a number of features that need to be implemented for this iteration. You will have to talk to your customer to know exactly what they want. I.e. you will have to conduct a planning meeting with your customer. Usually you will not be able to deliver everything the customer wants in one iteration. So you will have to prioritize the features. Make sure you write unit tests for the features you decide to implement. You will be evaluated based on the deliverables below, the quality of the system produced, and your adherence to the practices described in class.

As part of this iteration, you will also need to hold a retrospective to discuss the previous two iterations (iterations 0 and 1) and decide on action items to improve this iteration (iteration 2).

Outcomes & Deliverables

(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 in the form of an attached critique of the report (1 to 2 pages).
(c) Each member in the team should submit a peer-evaluation report. See the template in Numbers, Excel, or OpenOffice.

Checklist


UofC
SENG 403: Software Development in Teams and Organizations
Department of Computer Science

Last updated 2012-01-09 12:02
Rob Kremer