TR 9:15 - 10:30 pm Arts & Sciences (CAS) 143
Week 5 Class 9 Tue Sep 26 Posted: Sep 26
Announcements:
Tasks should be brief. For one thing, they need to fit on a post-it note. Secondly, that extra detail does not help; you would never have enough.
Class
Unless stated otherwise, all exercises are due by 3:30 pm on Wed Sep 27
As a team, create estimates for the user stories by playing planning poker using the procedure described on pages 48-49 of the book.
First, pick a user story that you have an estimates. Estimate each task for that user story. Indicate if the sum of the task estimates agrees with the previous user story estimate. Update the user story estimate if needed.
When the team reaches a consensus for the estimate, place the estimate at the bottom of the User Story on a separate line, e.g., "Estimate: 1 day" or "Estimate: 3 days".
Individually, each team member will turn in to Brightspace individual notes that include for each round of planning poker:
If the team cannot reach a consensus, table that User Story and go on to another one.
Modify the above when you estimate a task instead of a user story.
The notes are due by the end of class. They can be a PDF (print to file from a computing device) or a JPG (picture taken via phone). The notes are for today only. Do not start with the notes from the previous team meeting.
The more you work with the user stories, the more you will find improvements to them. Be sure to make those improvements.
Project 1 is due 11:59:59 pm Thursday, Sep 28, in the file Requirements.md in a GitHub Classroom repository. You will need a GitHub account. Once you have an account, an invitation link to create the repository is on the Brightspace course page.
Description
At your place of work, you need to submit a formal report describing the project's current state. Write a report of your individual and team activities, including:
In other words, all the work and processes followed while creating the user stories and their estimates. The details of the process and procedure and the general observations are in the form of a narrative, i.e., describe what you did, how you did it, and the result, ordered by time. The report's tone is professional, with a clear, consistent presentation.
The team created the User Stories and Estimates, but this report is an individual project. In your account, make changes to User Stories if they do not follow the guidelines given in the book. These changes are especially crucial for the Title and the Description. Split User Stories if the Estimate is too large. Explain any changes in your report.
Format
Score
The report content, format, and involvement in team activities are all considered for your score.
Think very carefully about the presentation of the report, including how you are using Markdown. Remember, the User Stories are an unordered set not an ordered list.
TA: Ms. Pavithra Desam pd83@uakron.edu