COS420-Fall24 / TeamG

Money Gremlin, COS 420 F2024
1 stars 0 forks source link

Add relevant tasks to sprint backlog 1 #32

Closed Eric-Jestel closed 1 week ago

Eric-Jestel commented 2 weeks ago

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.