Agile Release Planning

Using Jira
 Learning Objectives

By the end of this lesson, you will be able to:

Provide a high level overview of Jira

List the various use cases and features of Jira

Create various issues and schemes

Differentiate between Product and Sprint backlogs

What Is Jira?
 What Is Jira?

Jira is an Agile project management tool designed to help teams manage all types of work. It
can plan, track, and manage all software development projects.

Aspects provided by Jira

Projects

Issues

Workflow

Search

Dashboards
 Agile Methodologies Supported by Jira

Jira can support any Agile methodology, be it Scrum, Kanban, or any mixed methodologies.

Scrum Kanban Agile at scale Mixed

methodologies
 Origin of Jira

Jira was initially designed as a software testing tool purely for tracking bugs and issues.

Evolved after the

launch of Atlassian
Launched in 2002
Marketplace in 2012

Adopted by non-IT
organizations as a project
management tool after a
few years
 Jira Hosting Options

Jira is available in two hosting options: cloud and self-managed in a data center.

Cloud Data center

Jira is set up and Jira is self-managed and

hosted on the cloud hosted on hardware or
with IaaS vendors
Activity: Setup JIRA Account

Problem Statement / Agenda:

Scenario:
Your company, SunshineBox has created a development team to build a web application to
maintain a database of outlets selling your company’s products. The webapp should allow
your company to control access to this information. There should be a clear audit trail of
access and changes made to this database. The infrastructure needs to be robust to prevent
data loss.
You have been tasked with helping your team manage the development work. Your team has
decided to use JIRA to help you manage tasks, release, and visualize progress throughout the
project.
Setup a JIRA Account for the same.
Duration: 25 mins
 Activity : Guidelines

Instructions
• Create a new JIRA account.
• Go to https://www.atlassian.com/software/jira
• Follow the instructions on the website to create the account.
• Verify your account via an emailed link.
Activity: Create your Scrum project

Problem Statement / Agenda:

Scenario:
Your company, SunshineBox has created a development team to build a web application to
maintain a database of outlets selling your company’s products. The webapp should allow
your company to control access to this information. There should be a clear audit trail of
access and changes made to this database. The infrastructure needs to be robust to prevent
data loss.
You have been tasked with helping your team manage the development work. Your team has
decided to use JIRA to help you manage tasks, release, and visualize progress throughout the
project.
Setup a JIRA instance for your company and create your first project.
Duration: 60 mins
 Activity : Guidelines

Instructions
• Login to your JIRA account.
• Create a site for your project.
• Personalize your experience.
• Invite your team members.
• Choose the template you want to create (Scrum / Kanban / Bug tracking etc.). Choose Scrum
template.
• Create a project and give an appropriate name.
• You will see the Sprint Board in the Active Sprints view, once the project is created.
Jira Use Cases and Features
 Jira Use Cases

Jira can be used for all types of teams, from requirements and test case management to Agile
software development.

Requirements & test

case management
Agile
Project management

Software development
Product management

Task management
Bug tracking
 Jira for Requirements and Test Case Management

Jira provides a central hub for the coding,

Requirements
collaboration, and release stages.

Jira uses issues, customized screens, fields, and

Testing
workflows to manage manual and automated tests.
 Jira for Agile Teams

Jira provides Scrum Boards, Kanban Boards, and a number of useful features for teams that
practice Agile methodologies.

Issue tracking Progress

reports

Customizable
Project-level
workflows
permissions

Estimation & Email

work logging notifications
 Jira for Project Management Teams

Jira can be configured to fit any type of project. Teams can start with a project template or
create their own custom workflow.

Issue/Task
management Issue
customization

Project
Granular user
customization
permissions

Report & Workflow

Analytics customization
 Jira for Software Development Teams

Jira provides planning and roadmap tools that help teams manage stakeholders, budgets, and
feature requirements from Day One.

Release
planning Issue
management

Sprint
Feature
planning
flagging

CI/CD Developer tool

integrations integrations
 Jira for Product Management Teams

Jira enables teams to build a roadmap that’s associated with each project and that can track
and share progress of the products.

Roadmap
progress Advanced
tracking roadmaps

Roadmap
Forecasts
sharing

Dependency Confluence
mapping integration
 Jira for Task Management

Jira creates tasks and subtasks for team members to work on, complete with details, due
dates, and reminders.

Issue hierarchy Custom fields

Task change
Task linking/
log/history
relationships

Project linking Email

notifications
 Jira for Bug Tracking

Bugs are problems that stem from within the software that a team is building. Jira ensures that
bugs are automatically assigned and prioritized once they are captured.

Product/Issue
backlog Task/Bug
linking

Customizable
Project level
workflows
configuration

Email Project rules

notifications
Jira Scheme
 Jira Scheme

A Jira Scheme is a collection of configured values that can be used by one or more Jira projects.

Projects Project a

Schemes Scheme a Scheme b

Configurations Config Config Config

 Common Jira Schemes

Issue Type Scheme What issue types can be used in a particular Jira project

Notification Scheme Who receives what email when an issue changes

Permission Scheme Who can do what to an issue

Activity: Brainstorm and create a list of tasks

Problem Statement / Agenda:

Scenario:
Your company, SunshineBox has created a development team to build a web application to
maintain a database of outlets selling your company’s products. The webapp should allow
your company to control access to this information. There should be a clear audit trail of
access and changes made to this database. The infrastructure needs to be robust to prevent
data loss.
You have been tasked with helping your team manage the development work. Your team has
decided to use JIRA to help you manage tasks, release, and visualize progress throughout the
project.
Brainstorm with your team and identify the list of tasks your team needs to accomplish to
deliver the project.
Duration: 30 mins
 Activity : Guidelines

Instructions
• Create the list of tasks on paper or using a text editor.
• Think through the different phases of the project.
• Identify what the team can do and what external resources they need.
• Categorize the tasks under various categories. For example,
• Database requirements
• Infrastructure needs
• Webapp
Jira Issues and Issue Types
 Jira Issues

Issues are the building blocks of Jira. They distinguish different types of work in unique ways
and help to identify, categorize, and report on the team’s work across the Jira site.
 Issue Hierarchy

Depending on the complexity of the projects, different issues can be nested together. This can
help teams work on individual tasks while team leaders track the team's bigger picture.

Default hierarchy levels

Parent issues

Standard issues

Child issues
 Parent Issues

Parent issues or Epic issues represent high-level initiatives or bigger pieces of work in Jira.

Team Examples of parent issues

Software team A new feature being developed

IT service teams A major service change or upgrade

Business teams A major deliverable or phase of a project

 Standard Issues

Standard issues represent regular business tasks. In Jira, standard issues are where daily work is
discussed and carried out by team members.

Team Examples of standard issues

Software team Tracking the effort required to reach the end project goal

IT service teams Requests made by the customers

Business teams Tracking the daily tasks of all the teams

 Child Issues

Child issues or subtask issues are used, when needed, to help a team break a standard
issue into smaller chunks.

Team Examples of standard issues Examples of child issues

Software Tracking the effort required to reach Tracking the effort required to reach the
team the end project goal Sprint goal

IT service Splitting requests into separate

Requests made by the customers
teams categories

Business Tracking the daily tasks of different

Tracking the daily tasks of all the teams
teams teams separately
 Issue Types

Jira comes with five default issue types to suit the needs of projects and teams. They
can be customized to match any method of project management.

Epic Task Sub-task

Bug Story
 Issue Types

Epic

• Parent issue
• Groups together bugs, stories, and tasks to show the progress of a larger initiative

Bug

• Standard issue
• Represents a problem that impairs or prevents the functions of a product

Task

• Standard issue
• Represents work that needs to be done
 Issue Types

Story

• Standard issue
• Represents the smallest unit of work that needs to be done

Sub-task

• Child issue
• Represents a piece of work that is required to complete a task
 Issue Type Schemes

Issue Type Schemes make it easier for a team to select the right type when creating
issues in their project.

Issue type 0

Project Issue type …

Issue type n
 Issue Type Schemes

Uses

Set the available Issue Types for a project

Set the default Issue Type and order of Issue Types

Share the same group of Issue Types across multiple projects

Activity: Link issues to track dependencies

Problem Statement / Agenda:

Scenario:
Your company, SunshineBox has created a development team to build a web application to
maintain a database of outlets selling your company’s products. The webapp should allow
your company to control access to this information. There should be a clear audit trail of
access and changes made to this database. The infrastructure needs to be robust to prevent
data loss.
You have been tasked with helping your team manage the development work. Your team has
decided to use JIRA to help you manage tasks, release, and visualize progress throughout the
project.
Link issues when there are dependencies to figure out the priority order of tasks.
Duration : 30 mins
 Activity : Guidelines

Instructions:
• Link issues to the dependencies.
• Dependency can be an another task for the same project.
Story Points and Estimating Story Points
 Story Points

A Story Point in Jira is an estimated measure of effort required to implement a User Story.

Estimation field

User story
 Estimating Story Points

To estimate Story Points, stories are sized down and a point value is assigned to each story.
The team collectively brainstorms on the complexity of a story using “points”.

It’s too easy for an 8.

It’s an 8!
 Estimating Story Points

Points are given to each story taking into consideration a number of factors.

The amount of work to do

The complexity of the work

Risk or uncertainty in doing the work

Time/Duration
Common Scales for Estimating Story Points

Fibonacci Series T-shirt sizing

1,2,3 5, 8, 13, 21 XS, S, M, L, XL, XXL

General progression Complexity bucket

1, 2, 4, 8, 16 0.5D, 1D, 2D, 3D, 4D

 Steps for Estimating Story Points

Step 1 List all the stories to be sized

Put the stories in order, from the simplest to the most

Step 2
complex

Start from the bottom and give the bottommost story 2 story
Step 3
points*

Note
Giving ‘2’ provides room to give “1” if a smaller story is discovered at a later stage.
 Steps for Estimating Story Points

Look at the next story and decide how big it is as compared to the first
Step 4
one and assign points

Step 5 Continue until you have assigned a point for every story
 Importance of Story Points

Gives an Uses multiple

overview of the perspectives to Rectifies false
scope of the determine the assumptions
work size of the work
Activity: Story Points

Problem Statement / Agenda:

Scenario:
Your company, SunshineBox has created a development team to build a web application to
maintain a database of outlets selling your company’s products. The webapp should allow
your company to control access to this information. There should be a clear audit trail of
access and changes made to this database. The infrastructure needs to be robust to prevent
data loss.
You have been tasked with helping your team manage the development work. Your team has
decided to use JIRA to help you manage tasks, release, and visualize progress throughout the
project.
Estimate the complexity and work involved for each story and add story points.
Duration: 45 mins
 Activity : Guidelines

Instructions:
• Estimate the complexity and work involved for each story and add story points.
• Assume this metric for convenience.

Story Points Complexity or Work Involved

1 Less than ½ a day

2 1-2 days or has an external dependency

Multiple steps required, will require 3-5
3
days
Extremely complex or many unknowns,
5
may take the entire sprint
Jira Velocity Chart
 Jira Velocity Chart

Jira Velocity Chart shows the amount of value delivered in each Sprint. It helps to predict the
amount of work that a team can get done in future Sprints.
 Jira Velocity Chart

A team’s Velocity is calculated from a Velocity Chart by taking the average of the total
completed estimates over the last several Sprints.

Forecast Actual

Example:
The team's velocity is (15+15+20) / 3 = 16.67.
This means that the team can be expected
to complete around 16.67 Story Points
worth of work in the next Sprint.
 Jira Velocity Map

Forecast Actual

Note

The Velocity Chart becomes more accurate and reliable over time, as more data becomes
available and the team gets better at estimating issues.
Activity: Create a Velocity Chart - JIRA

Problem Statement / Agenda:

Scenario:
Your company, SunshineBox has created a development team to build a web application to
maintain a database of outlets selling your company’s products. The webapp should allow
your company to control access to this information. There should be a clear audit trail of
access and changes made to this database. The infrastructure needs to be robust to prevent
data loss.
You have been tasked with helping your team manage the development work. Your team has
decided to use JIRA to help you manage tasks, release, and visualize progress throughout the
project.
Create a Velocity Chart to review the amount of work done by your team in each Sprint.

Duration: 30 mins
 Activity : Guidelines

Instructions:
• Click on Complete sprint in the Active sprints view at the end of the Sprint.
• Move the incomplete tasks to another Sprint or to the backlog.
• Go to Reports > Velocity Chart to see how many story points were committed to vs
completed in each Sprint.
Jira Roadmap
 Jira Roadmap

A Jira Roadmap is a shared source of truth that outlines the vision, direction, and progress of a
product over time. They can help plan large groups of stories across different Sprints.
 Types of Jira Roadmaps

Roadmaps come in different forms and serve a variety of audiences. The content of a
roadmap will depend on its audience.

1 Internal roadmap for development team

2 Internal roadmap for executives

3 Internal roadmap for sales

4 External roadmap for customers

Benefits of Jira Roadmaps

Allow teams to focus on the most important tasks

Allow teams to communicate priorities effectively with

adjacent teams

Provide a big picture of the entire project

 Best Practices for Jira Roadmaps

Include only as much detail as necessary for an audience

Keep the roadmap focused on short-term tactics and how these

relate to long-term goals

Review roadmaps on a regular basis

Make sure everyone has access to the roadmap

Stay connected with stakeholders at all levels to ensure alignment

Activity: Create a Product Roadmap to review timeline -
JIRA

Problem Statement / Agenda:

Scenario:
Your company, SunshineBox has created a development team to build a web application to
maintain a database of outlets selling your company’s products. The webapp should allow
your company to control access to this information. There should be a clear audit trail of
access and changes made to this database. The infrastructure needs to be robust to prevent
data loss.
You have been tasked with helping your team manage the development work. Your team has
decided to use JIRA to help you manage tasks, release, and visualize progress throughout the
project.
Create a Product Roadmap to review the timeline of this project.

Duration: 45 mins
 Activity : Guidelines

Instructions:
• Capture each major feature/ aspect of the product as an Epic.
• Create Epics in the Backlog View.
• Attach an Epic to each story in the Backlog View
• Review the stats of stories and their statuses for each Epic.
• If Roadmap is not enabled, enable it with Active sprints > … > Board Settings > Roadmap
> Enable.
• Go to the Roadmap view to review the progress of different Epics along the timeline.
Jira Releases
 Jira Releases

Jira Releases can be used to schedule how features are rolled out to customers, or as a
method to organize work that has been completed for the project.
 Types of Jira Releases

There are two types of releases in Jira: project release and cross-project release.

Project Cross-project
release release

Used to organize specific Used to organize multiple

releases for corresponding Jira releases across different Jira
projects projects
Activity 1.4.6: Create a Release Plan _ JIRA

Problem Statement / Agenda:

Scenario:
Your company, SunshineBox has created a development team to build a web application to
maintain a database of outlets selling your company’s products. The webapp should allow
your company to control access to this information. There should be a clear audit trail of
access and changes made to this database. The infrastructure needs to be robust to prevent
data loss.
You have been tasked with helping your team manage the development work. Your team has
decided to use JIRA to help you manage tasks, release, and visualize progress throughout the
project.
Create a Release Plan. Add the release number to stories to track the version of the feature
release.
Duration: 60 mins
 Activity : Guidelines

Instructions:
• Assume your team decided to release new features every 2 weeks, i.e. at the end of each
Sprint.
• For a good measure, you can set the release date to 2 days after the Sprint.
• If Sprints end on Mondays, there will be a release on Wednesday of that week.
• Create and schedule releases in the Release view.
• Add the release number to the fix versions of your stories.
Jira Backlogs
 Jira Product Backlog

The Product Backlog contains all the items that are to be completed for the whole project.
 Jira Sprint Backlog

The Sprint Backlog contains all the items that are to be completed during each Sprint.
 Product and Sprint Backlog

Sprint backlog is a subset of the Product Backlog. The items needed for a particular
Sprint are selected from the Product Backlog and moved to the Sprint Backlog.

Everything to be Everything to be
1 2 3
done in a project done in a Sprint

Steps for carrying

Product Backlog Sprint Backlog
out work
Activity: Product Backlog

Problem Statement / Agenda:

Scenario:
Your company, SunshineBox has created a development team to build a web application to
maintain a database of outlets selling your company’s products. The webapp should allow
your company to control access to this information. There should be a clear audit trail of
access and changes made to this database. The infrastructure needs to be robust to prevent
data loss.
You have been tasked with helping your team manage the development work. Your team has
decided to use JIRA to help you manage tasks, release, and visualize progress throughout the
project.
Create your Product Backlog containing a story for each task in your list.
Duration: 45 mins
 Activity : Guidelines

Instructions
• Click the Create button to create an issue.
• Use Issue Type Story for each task.
• In general, the story creator is encouraged to include as much detail as possible in the
Description.
• For this exercise, leave the Description blank which can be filled later.
• Priority for each task can be set. The default is Medium.
• If the tasks have been categorized under different headings, those headings can be added as
Labels.
• Issues added will be listed in the Backlog view.
• Product Backlog is now ready.
Activity: Sprint & Sprint backlogs

Problem Statement / Agenda:

Scenario:
Your company, SunshineBox has created a development team to build a web application to
maintain a database of outlets selling your company’s products. The webapp should allow
your company to control access to this information. There should be a clear audit trail of
access and changes made to this database. The infrastructure needs to be robust to prevent
data loss.
You have been tasked with helping your team manage the development work. Your team has
decided to use JIRA to help you manage tasks, release, and visualize progress throughout the
project.
Identify the set of tasks to be completed in a 2-week Sprint. Review the Sprint Board & ensure
each task reflects the correct status.
Duration: 45 mins
 Activity : Guidelines

Instructions
• In the Backlog view, click Create Sprint to create a new Sprint. (This is typically called Sprint
Planning.)
• Identify the set of tasks to be completed in this 2-week Sprint.
• A prioritized backlog helps. The ones at the top of the Backlog can then be moved into the
Sprint.
• While identifying the tasks to include in a Sprint, consider the skills of the team and ensure
everyone has something they can work on.
• When you’re done, click Start Sprint.
• You can rename your Sprint, set duration, start and end dates etc.
• Go to the Active Sprints view to review your Sprint Board.
• Since the stories are all new, they should all be in the TODO column.
• As work is started or completed for a task, change the status to In Progress or DONE by
dragging to the corresponding column or changing the status within each story.
Using Jira
 Steps to Use Jira

Step 1 Click on Projects > Create Project

Step 2 Pick a template

Classic template Next-gen template

Contains all the power and Provides a reimagined, redesigned,
options that Jira is known for and simplified Jira experience
 Steps to Use Jira

Step 3 Set up the columns on the board

How to set columns?

Step 3.1 Navigate to the team's board in the project menu on the left

Step 3.2 Select more (•••) > Board settings in the top-right corner

Step 3.3 Select Column > Add column

 Steps to Use Jira

Step 4 Create an issue

• Select Backlog in the project menu

For Scrum teams
• Select Create issue

• Navigate to Kanban Board

For Kanban teams
• Select Create in the global menu
 Steps to Use Jira

Step 4 Invite your team

How to invite your team?

Step 4.1 Select Project settings on the left

Step 4.2 Select People > Add people

Step 4.3 Search for a team member's email address, and select Add
 Steps to Use Jira

Step 4 Move work forward

Activity: Customize the Scrum Board - JIRA

Problem Statement / Agenda:

Scenario:
Your company, SunshineBox has created a development team to build a web application to
maintain a database of outlets selling your company’s products. The webapp should allow
your company to control access to this information. There should be a clear audit trail of
access and changes made to this database. The infrastructure needs to be robust to prevent
data loss.
You have been tasked with helping your team manage the development work. Your team has
decided to use JIRA to help you manage tasks, release, and visualize progress throughout the
project.
Customize your Scrum Sprint Board.

Duration: 45 mins
 Activity : Guidelines

Instructions:
• Assuming that each story goes through 4 stages :
TODO → In Progress → Testing → Done.
• Go to Active Sprints > … > Board Settings > Columns
• Add Status to introduce a status called Testing.
• Add Column to add a Testing column to the Sprint Board.
 Key Takeaways

Jira is an Agile project management tool designed to help teams

plan, track, and manage all software development projects.

Jira can either be cloud-based or self-managed.

Jira schemes are a collection of configured values used by

multiple Jira projects.

Issues can represent bugs, stories, epics, tasks and subtasks.

 Key Takeaways

Points are assigned to stories, based on their complexity.

Product Backlog contains items for the entire project and

Sprint backlogs contain items for a particular Sprint.

The content of roadmaps differ, depending on the audience.

Knowledge Check
Knowledge
Check
What are Jira Schemes?
1

A. Product Backlog items

B. Configured values

C. Customer requirements

D. All of the above

 Knowledge
Check
What are Jira Schemes?
1

A. Product Backlog items

B. Configured values

C. Customer requirements

D. All of the above

The correct answer is B

Jira Schemes are a collection of configured values.

Knowledge
Check
Which of these are called the building blocks of Jira?
2

A. Schemes

B. Issues

C. Tasks

D. Stories
 Knowledge
Check
Which of these are called the building blocks of Jira?
2

A. Schemes

B. Issues

C. Tasks

D. Stories

The correct answer is B

Issues are known as the building blocks of Jira.

Knowledge
Check
Which of these is a parent issue?
3

A. Requests made by the customers

B. Tracking the effort required to build end goal in the team's software

C. A new feature being developed

D. Tracking the team members’ daily tasks

 Knowledge
Check
Which of these is a parent issue?
3

A. Requests made by the customers

B. Tracking the effort required to build end goal in the team's software

C. A new feature being developed

D. Tracking the team members’ daily tasks

The correct answer is C

A new feature being developed is an example of a parent issue.

Knowledge
Check
Where can you create an issue in Jira for Scrum teams?
4

A. From the Create in the global menu

B. From the Project Settings

C. From the Board Settings

D. From the Backlog in the project menu

 Knowledge
Check
Where can you create an issue in Jira for Scrum teams?
4

A. From the Create in the global menu

B. From the Project Settings

C. From the Board Settings

D. From the Backlog in the project menu

The correct answer is D

An issue can be created from the Backlog in the project menu.

Knowledge
Check
Which of these is a standard issue?
5

A. Epic

B. Bug

C. Sub-task

D. All of the above

 Knowledge
Check
Which of these is a standard issue?
5

A. Epic

B. Bug

C. Sub-task

D. All of the above

The correct answer is B

A bug is a standard issue.

Knowledge
Check
A Story Point measures the _________ required to implement a user story.
6

A. Time

B. Effort

C. Velocity

D. Throughput
 Knowledge
Check
A Story Point measures the _________ required to implement a user story.
6

A. Time

B. Effort

C. Velocity

D. Throughput

The correct answer is B

A Story Point measures the effort required to implement a User Story.

Knowledge
Check
How do you estimate a team’s velocity?
7

A. Total number of completed estimates / Total number of Sprints completed

B. Total number of completed estimates / Total number of projects completed

C. Total number of Sprints completed / Total number of completed estimates

D. Total number of projects completed / Total number of completed estimates

 Knowledge
Check
How do you estimate a team’s velocity?
7

A. Total number of completed estimates / Total number of Sprints completed

B. Total number of completed estimates / Total number of projects completed

C. Total number of Sprints completed / Total number of completed estimates

D. Total number of projects completed / Total number of completed estimates

The correct answer is A

A team’s Velocity is calculated by dividing the total number of completed estimates by the total number of Sprints
completed.
Case Study
 About the Case Study Component

Thoughtworks, a seasoned Agile practitioner conducted an

interested case study of estimating an Agile project.

Duration: 1hr 30 mins

 Executive Summary

The case study helps you understand

● How estimation and sizing are used in organizations that
practice Agile
● Assimilate concepts learned about estimation and sizing
● Highlight important and relevant facts that have a bearing on
the problem and the objective.
Discussion
 Analysis

● Why estimation is done?

● Where estimations are useful and for what?
● Read and analyse the story points
● What is relative sizing?
● How is estimation done on a distributed team?
 Recommendation

● Importance of estimation and how expectations are set through

the eyes of experienced and seasoned developer professionals
● Estimations help make significant decision like choosing between
features, coordination and collaboration across teams, and
encouraging useful conversations
● Story points are more beneficial that estimating in hours and
understand if story points can be standardized across various
teams
● Understand relative sizing through fruit basket analogy.
 Recap

Thoughtworks, a seasoned Agile practitioner conducted an

interested case study of estimating an Agile project.
The case study helped you understand
● How estimation and sizing are used in organizations that
practice Agile
● Assimilate concepts learned about estimation and sizing
● Highlight important and relevant facts that have a bearing on the
problem and the objective.
 What’s Next?

Definition of the Agile Maturity Model

• What is Agile Maturity Model?
• Levels of Maturity Level 0
• Levels of Maturity Level 1
• Levels of Maturity Level 2
• Levels of Maturity Level 3
• Levels of Maturity Level 4
• Self Assessing Agile Maturity Levels
• Continuous Improvement