1 Before the Sprint Planning Meeting

After a long meeting, Upper management has decided to fund one more sprint and they have added a number of features to the Product Backlog. They are contained in the following document:

You should enter all of the epics and stories (which ScrumBoard calls issues) into ScrumBoard prior to the sprint planning meeting (to save time during the meeting).

In addition, every member of the team must read and understand the interaction design document.

Finally, before the sprint planning meeting each member of the team must read the descriptions of the:

and add appropriate items into the sprint backlog. (Also, you should probably agree on a firm date/time when these tasks will begin, and think about what tasks are on the critical path before these tasks.)

2 The Sprint Planning Meeting

During the sprint planning meeting you must:

1. Move any stories/tasks that were not completed during the last sprint to this one.
2. Apply the sprint planning process to those stories/tasks and any remaining stories in the product backlog. (See sprint 1 if you've forgotten the process.)

The Product Owner has determined that the story "User Documentation" is non-negotiable. That is, whatever other features you include in Sprint 3 (including those that were promised for Sprint 3 but are not in the product), these two features must be included in the product in Sprint 3.

3 The Remainder of the Sprint

After the sprint planning meeting is over, each member of the team must complete the tasks that they took responsibility for and record their progress in the Scrum tool.

4 What You Will Need for the Review

In addition to what you needed for the Sprint 1 review, you must have a thumb drive that contains your executable .jar file(s) and whatever files (configuration files, histories, etc.) it needs to run. It must not contain the HTML files for the user documentation (i.e., help files). Those files must be in the .jar file.

Remember that your product must run correctly on a lab machine.

5 Technical Hints and Help

The following hints might help you add some of the functionality described in the stories or create some of the deliverables.