Project 2: Iteration Plan Posted: September 28, 2020

Project 2 is due by 4 pm on Wed, Oct 14 with updates allowed through 11:59:59 pm on Fri, Oct 16, submitted via a GitHub Classroom repository. An invitation link to create the repository is on the Brightspace course page.

For Project 2, take all the user stories from Project 1 and create a series of iteration plans.

Use the examples in the book to show which parts of the user story you should show in your iteration plan (e.g., do not restate descriptions). Also, for each plan, clearly state the entire new iteration plan, not just the changes. However, make sure to thoroughly discuss what the change was and what effect it had.

This is an individual project. Each member of a team has different user-story priorities. To get individual priorities for Project 2, select the number of user stories:

User Stories: 30

Put these in the Priority field in the order that you listed the user stories. In the report, do not discuss how you generated your report’s priorities, i.e., pretend that the customer gave them.

The following plans may have you add additional user stories. This violates our rule that only the development team can create estimates. However, as as part of the exercise.

Plan 1

Create an initial iteration plan:

Plan 2

The customer adds two new user stories of the highest priority at the very end of the first iteration. For the two new user stories, one is a new feature, and one is an emergency. Create for them a non-trivial estimate (i.e., an estimate that makes the planning interesting).

Plan 3

A user story with a non-trivial estimate is taking three times as long. Assume this occurred right before the last iteration.

Plan 4

At the beginning of the last iteration of your current plan, the other developer leaves for another project, and it is up to you to finish the project.