Epic

  • An Epic captures a large body of work. It is essentially a large user story that can be broken down into a number of smaller stories. It may take several sprints to complete an epic.
  • Big, coarse-grained
  • Large themes, overall goals
  • Epic is created by PTL
  • Epic is never entered as a reference in Gerrit Commit to a Jira Issue ID. (because Epic is very big, and can't be implemented within 1 single commit)
  • It may takes multiple Sprint to implement an Epic

Story

  • A Story or user story is a software system requirement that is expressed in a few short sentences, ideally using non-technical language
  • Non-technical language, Story expresses user needs using the syntax below
User Story Syntax
As a <user> = who
I want to <be able to do ABC> = what
So that <XYZ can be done> = why
  • Story is created by PTL
  • The scope of a Story should be addressed within a single Sprint
  • Story is rarely entered as a reference in Gerrit Commit to a JIRA Issue ID

Task

  • A Task represents a technical activity, like design a diagram, code a functionality, test a device, or prepare dataset
  • A Task contains description of individual work item (detailed, technical)
  • A Task can be shared, assigned, relate to, depends/depended on by, blocks/blocks by
  • A Task can be created by anyone
  • Task is entered  as a reference in Gerrit Commit to a JIRA Issue ID

Epic Story Sub-Task

Sub-Task

  • A Sub-Task is similar to a Task
  • A Sub-Task is typically one of many tasks that make up a Story
  • A Sub-Task is created from a Story. You cannot create a sub-Task from the Create Issue button
  • Breaks-up stories into digestible workloads
  • A Sub-Task is created by anyone
  • A Sub-Task is entered  as a reference in Gerrit Commit to a JIRA Issue ID

Create Sub-Task