Project 3: Iteration One

Iteration 1 of your project will last for two weeks. Your deliverable is due at 11:55 PM on Friday, April 2nd.

Overview

Over the next two weeks, your team will execute iteration 1 as described in the iteration plan that you submitted for Project 2. This means that you will assign tasks to team members and attempt to complete those user stories that were assigned to this iteration. Keep track of your daily progress using the Burn Down chart technique covered in the textbook. If you encounter tasks and/or user stories that were not in the original plan, be sure to add them and reshuffle your iteration plan accordingly.

Deliverable

You should submit a PDF document as your deliverable with the following sections.

  1. Overview. Describe what your team did in this iteration, what problems you encountered and how you addressed them.
  2. Progress Report: List the tasks/user stories that your team completed and include a burn-down chart showing your team's progress over the course of the two week iteration. (Note: since this iteration spans across Spring Break, you can present this chart as a 3-week iteration if you want.)
  3. Diagrams: Provide UML diagrams, architecture diagrams, etc. that provide information and insight into what you accomplished during this iteration. You could, for instance, provide a class diagram of the classes and relationships of the code completed during this iteration, or show what components of the architecture were worked on, etc..
  4. FSP: (Optional): If you have spent time modeling the concurency in your system using FSP, include the FSP model and any diagrams produced by LTSA that help to explain what you've accomplished or what you are planning.
  5. New Iteration Plan: Describe any new stories and/or tasks that were added to your iteration plan as a result of the work in this iteration. Recalculate your velocity using the formula in Chapter 10 of the Head First Software Development textbook and then include a new iteration plan that covers iteration 2 and iteration 3. Be sure to discuss the implications of this new plan: are you still on track with respect to the goals of the original iteration plan or did you have to re-scope the project based on the results of iteration 1?
  6. Demo: Provide a pointer to an artificat that shows the current state of the system. What can your prototoype do now after the first iteration? If you're developing a Web-based system, send me a URL. If you're developing a desktop application, create a screencast of it in operation. If the system doesn't do much yet, you can also send me a transcript of test cases being run on the code along with the source code for those test cases.

Due Date

Please submit your document via e-mail as a PDF document to Prof. Anderson by 11:55 PM on Friday, April 2nd.

Questions?

Contact Professor Anderson if you have any questions or concerns about this assignment.

© Kenneth M. Anderson, 2010.