Agile terms in jira

From Tintu Wiki
Revision as of 11:41, 29 October 2024 by Tintucraju (talk | contribs) (Created page with "== Issue Type Story == Concept called user story. as a type of <user> I want <some goal> so that <some reason> Example : As a web developer I want to add users to jira so that my coworkers can report bugs. As a driver I need a voice activation so that I can voice search while driving.. There is no technical point here it just purely tell a story === Epic === it is a story that is too big for a sprint(typically two weeks). this will be break down to multiple st...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Issue Type Story[edit]

Concept called user story.

as a type of <user> I want <some goal> so that <some reason>

Example : As a web developer I want to add users to jira so that my coworkers can report bugs.

As a driver I need a voice activation so that I can voice search while driving..

There is no technical point here it just purely tell a story


Epic[edit]

it is a story that is too big for a sprint(typically two weeks). this will be break down to multiple stories. once all such stories are completed then the epic is completed.

Epic : <insert a simple example>

    <story 1 insert here>
    <story 2 insert here>
    <story 3 insert here>

here stories are linked to epics.


Issues[edit]

containers for fields. description , summary , due date etc. we can have different issue types. epic , story , bug , etc..

Projects[edit]

projects are containers for the issues. The types can be customized between different projects based on the requirement.