...
Agreed story points per sprint
Team Member | Story Points |
|---|
Mike | ||
Matt |
KSeniya |
Other |
Backlog Buckets
Backlog Name | Ticket Type |
|---|---|
Sprint # | Current sprint (at top) |
Sprints # | Next planned sprints |
– BACKLOGS -- | Separator |
Backlog - High Priority | Backlog - High Priority |
Backlog - Non Project | Backlog - Non Project Work |
Backlog | Backlog - General Low Priority |
Epics
An ‘Epic’ is a category in Jira that can be assigned to a story. We are using Epics to categorise our Projects and therefore link our stories to Projects for future reporting.
...
Components have been created for the work we are currently undertaking… if you need a Component created for a ticket you have created please contact Mike or Matt O.
Component | Activities |
|---|---|
UX : 01 : Discovery | |
UX : 02 : User Insight | |
UX : 03 : Information Architecture | |
UX : 04 : User Journeys & Process Flows | |
UX : 05 : Wireframe Design / Prototype | |
UX : 06 : UI Design / Prototype | |
UX : 07 : User Testing | |
UX : 20 : Design System Development | |
UX : 21 : Promotional Video | |
UX : 90 : Process & Tool Configs | |
UX : 91 : Training |
Using Jira
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.
...