KILowBites Sprint 2

1 Before the Sprint Planning Meeting

After having several people use the initial increment of the product, a number of features have been added to the Product Backlog. They are contained in the following document:

Additions to the Product Backlog After Sprint 1

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).

2 The Sprint Planning Meeting

During the sprint planning meeting you must:

Move any stories/tasks that were not completed during the last sprint to this one.
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 "Executable .jar File" and the additional epic "Flexibility in Ingredients" are both non-negotiable. That is, whatever other features you include in Sprint 2 (including those that were promised for Sprint 1 but are not in the product), these two features must be included in the product in Sprint 2.

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, recipes, etc.) it needs to run. It must not contain the HTML files for the user documentation. 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.

5.1 Internationalization

Localization/internationalization (i.e., supporting multiple languages) seems like a difficult task but is actually fairly straightforward if you plan ahead. This is described in one of the labs.

5.2 Opening an External WWW Browser

A Java application can run other programs. For example, one can open an external WWW browser using the process described on the Departmental Wiki

5.3 Executable .jar Files

There is a lab on how to create an executable .jar files.

If you just click/double-click on an executable .jar file and the code throws an exception you (typically) won't see it. Hence, when testing it is often useful to run the application from the command line. To do so, open a command shell, change the working directory to the directory that contains the .jar file, and then execute the application as follows:

    java -jar filename.jar

There are times when you can read resources directly from an executable .jar file and there are times when you must copy them to a temporary directory first (e.g., when HTML pages need to be loaded into an external browser). Help is available on the Departmental Wiki.

5.4 Printing

Help on printing is available in a lecture from another course.

5.5 Creating HTML Javadocs

Though you have included javadoc-compatible comments in your code all semester, you may never have created HTML documents from them. The process for doing so is described on the Departmental Wiki