Page Comparison

...

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

  • Parent (previously 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.

...

Backlog Buckets

Parents (Epics)

An ‘Epic’ A 'Parent’ is a category in Jira that can be assigned to a story. We are using Epics Parents to categorise our Projects and therefore link our stories to Projects for future reporting.

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

...

• Stories

  • <project description> - <brief work description>
    eg Mobile App - promotional video
    eg Savings base build - UI designs
    eg Broker CRM - User Journeys

• Epics Parents

  • UX - Broker : <Project Name>
    eg UX - Broker : CRM

  • UX - Connect : <Project Name>
    eg UX - Connect : Broker ID

  • UX - Lenders : <Project Name>
    eg UX - Lenders : Apprivo Savings Base Build

  • UX - Group : <Project Name>
    eg UX - Group : Finova Website

• Components

  • UX : <ID> : <Activity>
    eg UX : 01 : Discovery