Introduction to Scrum with JIRA

Ask us a question

Introduction to Scrum with JIRA is a one-day online workshop giving you the confidence to start using Jira to manage work within a Scrum team.

Delegates leave the course more confident in five key areas:

  1. Scrum in a nutshell: Roles, events and artefacts.
  2. Getting started with JIRA: setting up a project
  3. Managing requirements from epics to user stories
  4. Sprint planning sessions in JIRA
  5. Tracking progress towards sprint goals and major releases.

Content

Case Study Project: Setting it Up in JIRA

An idea for a product is presented to the class, with an initial set of requirements available in text format.  Delegates are shown how to create a new JIRA project with the Scrum template, and populate the initial product backlog by creating user stories.

Introduction to Scrum Roles

The three roles in Scrum are introduced, and each team assigns a Scrum Master and Product Owner:

  • Product Owner: Maximising the value of the product
  • Development Team: Delivering a high-quality product
  • Scrum Master: Maximising the organisation’s ability to deliver

Scrum Framework

Scrum Artefacts in JIRA

The three core Scrum artefacts are introduced as the expression of requirements at different points in time:

  1. Product backlog: requirements to be delivered.
  2. Sprint Backlog: the current, active working plan.
  3. Increment: the current state of the product, representing the progress made so far.

Delegates explore the wide range of techniques available to manage this information and take part in practical exercises to explore, such as:

  • User stories.
  • Estimating software development with story points.
  • Value and return on investment.
  • Attaching diagrams, documents and images to JIRA tickets
  • Managing dependancies between JIRA work items.

Scrum Events in JIRA

Delegates explore the intent between the Scrum events, and are given the opportunity to simulate these in practice:

  • Sprint Planning: The team and product owner use JIRA to break down user stories into sub-tasks and estimate their capacity for the sprint
  • Daily Scrum: The team assess their progress towards the sprint goal by reviewing the Jira Scrum board and sprint burndown charts
  • Sprint Review: The team assess the longer-term release forcasts by learning how to configure JIRA to show a rolling backlog projection and release burnup chart.
  • Sprint Retrospective: The team learn the principle of continuous improvement and how JIRA can help to track team improvements.

Outcomes

Delegates will leave the course having been taken through a worked example of software development in Scrum. They will have used JIRA to undertake the full range of tasks and processes that real development teams do while managing their work.

Ready to get started?

Our team of business agility experts are here to help

Contact us

Discover new insights

I’m a product owner not a feature... By Paul Grew

Read More
Agility.im

Sign up for our newsletter

Keep up to date with all the latest business agility news