unitED Sprint 2

The product owner has decided that the graphical user interface in the first increment was awkward to use, and that the product should have the physical keyboard mimic the behavior of the soft keyboard (i.e., when the user presses the physical 1 key the product behaves as if the user clicked on the soft 1 button).

In addition, the product owner has determined that the limited number of features makes it impossible to market and sell the product at this point. Hence, a number of new features have been added to the product backlog.

1 Before the Sprint Planning Meeting

Before the sprint planning meeting you must all read and understand the stories that must be added to the product backlog. They are contained in the following document:

Additions to the Product Backlog After Sprint 1

You should also enter all of the epics and stories (which ScrumBoard calls issues) into ScrumBoard. This will save a lot of time during the planning meeting.

Finally, each member of the team must read and understand the new interaction design document:

Interaction Design Document v2

2 The Sprint Planning Meeting

During the sprint planning meeting you must:

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

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

Obviously, all of your team's code must be in your GitHub repository and all other sprint-related materials must be in the sprint planning/management tool. In addition, on the day of the review your team must have the following:

An executable .jar file (on a USB drive) containing the current increment of the product that works on a lab machine.
Up-to-date printouts of your testing materials and results.

5 Technical Hints and Help

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

5.1 Language Support/Internationalization

You have completed (or are about to complete) a lab on internationalization.

5.2 Creating an Executable .jar File

You have completed (or are about to complete) a lab on creating executable .jar files.

5.3 Testing an Executable .jar File

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

5.4 Copying Resources from a .jar File

The following wiki page might help you load the HTML pages from a .jar file:

Copying Resources to a Temporary Directory

5.5 Printing

The following lecture material from another course might be helpful:

Printing

5.6 Superscripts

Some components, like JLabel objects support HTML. So, for example, the following JLabel:


JLabel label = new JLabel("<html>in<sup>2</sup><html>");

will display the text as in².

One can also use AttributedString objects to accomplish the same thing. To do so, see the following wiki page:

Using AttributedString Objects

Finally, the following lecture material from another course might be helpful if you need to customize existing GUI components: