CPSC 480-010 Software Engineering (SE) Spring 2023

Reminders

• Every time you look at the set of user stories, you may see improvements. These improvements include wording, grammar, capitalization, terminology, and even if the team should split a user story. The user stories can be updated right up until implementation. So, if you see any improvements, make them.

  In particular, make sure your user story titles are as good as they can be:

  • The title has to complete the sentence "A user should be able to …". Say the title outloud multiple times.
  • I see a lot of missing articles, i.e., "A", "An", "The".
  • Avoid weak words "Info", "Data", "System"

• Remember to take your graded assignments from the folder.

Steps

1. Pick one of the user stories that you already have an estimate for. Create tasks for this user story only. I will provide smaller cards to write the tasks on.
2. Use the estimation process to create an estimate for each task.
3. Total the estimates for the tasks and compare them to the estimate for the user story.

Each team member will turn in to Brightspace a separate document that includes each round of planning poker:

• Title of the user story or task
• The spread of estimates, indicating which one is yours
• The team consensus (if the team was able to reach one in this round)
• If the consensus changes the overall estimate of the user story
• Any assumptions that you made
• Any questions or confusions on the user story or task that is of interest

I recommend you take notes as you go along. If on paper, do this exercise on a new sheet of paper. The uploaded document can be a PDF or a JPG.