Swhynot99
commented
1 week ago Check ID in Product backlog to make sure they all match
Closed JaydenScottL closed 1 week ago
Swhynot99
commented
1 week ago Check ID in Product backlog to make sure they all match
Use this template. See example(s) here.
Contains only the stories (user stories and technical and non-technical stories) you commit to working on and delivering for this Deliverable. Should reflect the product backlog. That is, all the user stories that are assigned to this Sprint in the product backlog, should be shown in this Sprint Backlog.
For any missing user story, deduct -2 points.
If the Sprint Backlog 1 does not reflect the product backlog, deduct -5 points.
You should also have other tasks in the backlog, like documentation, requirements, UI mockups, etc. As covered in class sessions, these are called non-technical stories.
You don’t need to have all the tasks for all future Deliverables for the project, just the ones for the sprint that you planned to do (and perhaps completed) See the sprint backlog in the examples All columns based on the projects’ details document should be in the product backlog and must be filled out. For any missing column or missing information deduct -2 points.
If using the "regularly export this from Github Projects" option for this, your sprint backlog items should have the milestone field set to your current deliverable. For the sprint backlog you must make two exports during each sprint/deliverable, 1) right after your sprint kickoff meeting where everything is assigned, and 2) at the end of the deliverable. (This will also show if people are being assigned work then not doing their work, using the assignee field.) Be sure you have the milestone set to the appropriate deliverable so these show up on the export correctly, i.e.