July 2009
Su Mo Tu We Th Fr Sa
1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31
Due Friday, July 17th, 2009 at 10:00am sharp.
The initial product backlog has been created. In this phase, your group will do your first sprint. There are two sprints in total.
You will be filling out and submitting a form for each of your team members, including yourself. This form will rate team members on citizenship: did they attend meetings, did they participate, did they do what they said they were going to do, and so on. We will post a final version before the deadline. Your Phase II will receive a grade, and these evaluations will be used to make individual adjustments to that grade. These are meant to be private: each team member will hand these in separately, and you are not required to show each other your forms. In the case of serious disagreement, or if you request it, we will hold a team meeting to discuss the results, but we will never reveal individual ratings.
In tutorial on July 7th, you will work out your sprint backlog: the list of items you and your group think you can accomplish in this phase. The sprint backlog contains everything related to the sprint: questions you need answered, a detailed breakdown of items from the product backlog, stuff you need to learn or set up, and so on. By the end of the day, you should have made a page on the wiki for your sprint backlog.
The sprint backlog gives you a way to measure progress. Make a page on the wiki for the sprint backlog Remember to include estimated difficulties. Also, this page should have two separate lists: one for tasks that still need doing, and one for tasks that are done.
In Scrum, you and your team would normally start every workday with a 10-minute meeting and give status reports. Since you and your team are almost never all in the same room, you'll use the wiki instead.
As discussed in lecture, the point of this is to let your teammates and ScrumMaster know what you are doing and what your plans for the immediate future are.
Make another page where you'll be keeping track of who's done what each day. Here are wiki-formatted tables for each day; you can copy and paste this into your wiki. Replace "m1", "m2", and so on with your CDF usernames. Every day, answer these questions:
For the obstacles, don't list other classwork or other time pressures; instead, list things specific to the project, like "I can't get RecordStores to work." and "I'm having trouble getting NetBeans on CDF to save my project settings.".
Whenever you have an obstacle, send email to your group list and your ScrumMaster will try to help, and if they can't, they'll let Paul know.
We understand that your schedule will probably prevent you from doing much on most days, and "nothing" is a perfectly fine answer to these questions. However, you must answer the questions every Monday, Wednesday, and Friday, even if you just write "nothing" most of the time. This will let you and your group keep track of each other and know that everyone is keeping up.
At the end of the sprint, your team should have a working version of an application that does a substantial part of the product backlog. You should, of course, have Javadoc comments for all your code, and a user should have a way to get help information about your game.