Product backlog - team S0
By the date indicated on your class schedule do the following as a team:
- Review the board that your instructor copied to your Trello team. Read over the User Stories and
that are in the Sprint Backlog list. You will begin handling these for Sprint 1.
- Post any requirements questions to the Slack or Discord channel for your team.
- Clean these user stories up, put them into the format prescribed in our Defining Project Requirements lecture. The final result should be a prioritized list of User
Stories and Epic cards. Provide a short title for each card, and the story text written in the standard format. At this point, you do not have to define Story Points, Acceptance
Criteria, or Solution Tasks for User Stories that will be implemented in later sprints (*although beginning to think/talk about them will give your team a huge advantage). Epic cards
should have all of the associated User Story cards linked to the Stories list by copying the URL for each constituent User Story and pasting it as a checklist item in the
Stories list. See the Defining Project Requirements lecture
for details.
-
Click here
for a sample of a good Epic/Story hierarchy and a few good Stories to demonstrate
the level of detail expected.
Your instructor will review your Trello board at the end of Sprint 0 and evaluate it using
the rubric Product Backlog.
