Skip to content

Instantly share code, notes, and snippets.

@fabianbaechli

fabianbaechli/agile_with_jira.md

Last active September 15, 2017 09:55
Show Gist options
  • Save fabianbaechli/432169d04ba2a828d0fc6655ab11604a to your computer and use it in GitHub Desktop.
Save fabianbaechli/432169d04ba2a828d0fc6655ab11604a to your computer and use it in GitHub Desktop.
Download ZIP
Raw
agile_with_jira.md

Agile with JIRA

Scrum vs Kanban

Infos collected from this video

  • Scrum: Used when developing something with a target deadline
  • Kanban: When you don't have a target deadline. No planning just prioritozing.

Epic

Epics are kind of a upper category for a "kind of task". In my case this could be something like "Configuring devices" and every task which falls in that category has this tag

Scrum with Jira

Plan mode in Jira

  • Creating issues which end up in the backlog
    • It doesn't matter if the stuff gets done in two years or in the next week
  • Figuring out if you want to use epics
  • Picking things you want to do next (defining the sprint)
    • Naming the sprint (maybe letters)
    • The time required to do all the things should be about two weeks
    • Tasks dependencies can be defined

Work mode

After you defined the tasks for your sprint you change into workmode

Storypoints

  • In agile, the time required to complete a task, is not estimated in hours.
  • Tasks get estimated in storypoints. They are more flexible and abstract than hours and its therefore simpler to estimate the size of a task in storypoints rather than hours.
  • A good increment value for them is 2^x
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment