CPSC 480-010 Software Engineering (SE) Spring 2023

Continue to determine estimates for your user stories following the procedure from the last Team Meeting. Keep in mind the following:

• Look carefully at the spread as shown in the book, as it is not just a list of numbers, but a number line
• Estimates include everything needed for the user story to be implemented and used by or demonstrated in front of/with the customer. This includes coding, testing, documentation, installation, back-end code, UI, everything. A single-user story may not be enough for the customer to release the product, but it must be ready as soon as other user stories are implemented.
• Never say ".. all we have to do is ". Think carefully about what it would take.
• Do not assume that your customer will pick the user stories in a particular order (iteration plan order) or want to implement all of them. Each user story must be estimated as a standalone feature.
• Do not assume another user story is complete before you do the one in front of you. Dependencies exist, but they should not be to simplify the development of user stories.
• Do not assume that the implementation of a user story is just a slight modification (code-wise) of another user story. Testing, documentation, etc., take just as long in the latter as in the former feature.
• Actions such as "Modify" or "Delete" do not depend on actions such as "Create" or "Add". Often data is prefilled before the user sees it. I.e., you don't have to have "Add" implemented before you "Delete".

If you cannot reach a consensus, discuss and perform another round of planning poker. When the team gets a consensus for the estimate, place the estimate at the bottom of the description on a separate line, e.g., "Estimate: 1 day" or "Estimate: 3 days".

As before, each team member will turn in to Brightspace a separate, new document that includes each round of planning poker:

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

I recommend you take notes as you go along.

The document can be a PDF or a JPG.

Once consensus has been reached, write down the estimate on the user story.