...
1 story point should equate to the work that a team member can complete during a typical workday including meetings. So for example if you a story is created and the task described would take one and a quarter normal working days to complete.. then that Jira story would be given 1.25 story points.
The story points assigned to a Jira story should be agreed with the person doing the work during sprint planning.
Story point values to be used: 0.25, 0.5, 0.75, 1, 1.25, 1.5, etc
Each team member will have a maximum number of story points that they can reasonably be expected to complete during a sprint which excludes holidays.
Agreed story points per sprint
...
Backlog Name | Ticket Type |
|---|---|
Sprint # | Current sprint (at top) |
Sprints # | Next planned sprints |
--Templates– BACKLOGS -- | Task templates ready to clone to create new task (story)Separator |
Backlog - High Priority | Backlog - High Priority |
Backlog - Non Project | Backlog - Non Project Work |
Backlog | Backlog - General Low Priority |
...
Please feel free to create items in the backlog and place them in the ‘High Priority’, ‘Non Project’ or Backlog - General Low Priority buckets
Please feel free to progress your own tickets through the current sprint’s Kanban board
Please feel free to add to the description of a story assigned to you or add a comment
Please feel free to link a document link to a story assigned to you
Please feel free to flag a story as blocked and add a comment as to why
Please do not add or remove stories from the current sprint without agreement with Mike or Matt O. It won’t break anything but it does affect the sprint metrics and reporting.
Please do not adjust the story point values assigned to a Jira story in the currently running sprint without agreement with Mike or Matt O. It won’t break anything but it does affect the sprint metrics and reporting.
...