Sprint Planning

Prior to the customer meeting, the team should do the following:
  1. Forecast how much time each team member will have during each of the next two weeks for working on the project
  2. If you have historical data, look at your velocity (velocity defined)
During the customer meeting, the team and customer should do the following:
  1. Determine if you will have a one or two week sprint
  2. Write a sprint goal
  3. Write user stories (likely driven from the SRS use cases)
  4. Estimate effort to complete the user stories
  5. Negotiate which user stories fit in the sprint
  6. Identify "stretch goals" for the sprint if you get done early
  7. Agree on acceptance criteria for accepted user stories
After the customer meeting, the team should do the following:
  1. Enter the user stories in JIRA using Greenhopper (typically use Agile tab to create a board (also manage board and change estimation to Original Time Estimate), add sprints, user stories/sub-tasks, and tasks)
  2. Assign tasks, owners, and estimates in JIRA
  3. Start your Iteration Report by posting your sprint goal, and accepted user stories, stretch goals, and acceptance criteria
  4. Get to work on the tasks, conduct daily stand-up meetings, communicate issues and/or progress to Dr. Janzen and/or your customer as needed