Content Comparison

...

• The aim of working in Jira is to document a list of tasks:

  • were What we have yet to start

  • are What is in progress

  • are What is completed

• Jira is not being implemented to track the time taken for a team member to complete a task. There is a time element to the process but this is used to ensure so that we understand the teams usual capability in completing work how much work the team can typically complete within a set period...and then this metric (gathered from historic data) aids future work planning.

Managing Tasks

• Tasks to be done are categorised in Jira as 'Issues'.

• In Jira, there are 3 issue types (Story, Task, Bug), however all issues that we will create in Jira should be defined as a ‘Story’ as this type has more functionality than the other types.

• When a story is created the following information is added to it:

  • Name

  • Description

  • Unique ID (Auto created)

  • Epic Category (Project ID - select from list)

  • Component Category (Work Type - select from list)

  • Assignee (Team Member doing the work)

  • Story Point (A value indicating the estimated time to complete the task) - See separate section

• Stories are created in the ‘Backlog’ by anyone (typically the person that knows most about the task).

• The 'Backlog' contains a number of buckets used to sort stories by status (planned / unplanned) and priority. Stories can be dragged from bucket to bucket… for further details see the list of backlog buckets below.

...

• Stories are worked on during a ‘Sprint’ (a period of time with a start and end date). UX team sprints are of 2 weeks duration (starting on a Monday and finishing on a Friday).

• Prior to the sprint starting, the stories to be added are agreed during a short ‘Sprint Planning’ meeting involving team members.

• Each team member will have an agreed number of story points that can be added to a sprint and this determines the number of stories that are added to each sprint.

Story Points

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

Agreed story points per sprint

...

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.

Epics are created as we first learn about projects… if you need an Epic created for a ticket you have created please contact Mike or Matt O.

Components

A ‘Component’ is a category in Jira that can be assigned to a story. We are using Components to categorise our work Activities and therefore link our stories to Activities 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.

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

...

Task (Story) Creation

Sprint Planning

...

• 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.

Naming Conventions

• Stories
  fewgerg

• Epics
  jhvewfkjwbf

• Components
  khfbewjkfb