This document discusses how a Scrum team used JIRA to manage their work. It begins by describing some of the limitations they faced with using a physical board and their desire to go digital. It then outlines key questions the team had about functionality needed in JIRA. The document then walks through the team's journey in JIRA, covering planning (PLAN), active sprints (DO), and reporting (TRACK). It provides screenshots and explanations of how to use different JIRA features like epics, versions, boards, filters, and reports to support each part of the Scrum process.
3. About the speaker
Anuj M Ojha
Agile Consultant
An experienced Agile practitioner and transformation consultant who helps organizations deliver value to customers and businesses,
through team coaching and mentoring, effective collaboration, facilitation and continuous improvement practices
Certifications
Experience
14+ years of experience with relevant agile experience of 11+
years and have trained 12000+ participants & coached 80+
teams on agile practices & implementation techniques. Have
been to various geographies to deliver consulting services.
My special area of interest has been bringing in business
agility, appropriate mindset & enriching Culture. It all starts
from no process to some process which helps teams &
companies in being their own better version by healing their
broken processes and other aspects.
Educational Experience
• Bachelor of Engineering
Areas of Expertise
Business Agility, Agile Coaching (Leadership, Business
Stakeholders, Product Owners, Scrum Masters, Development
Team members, Agile in Distributed Teams & at Scale, Agile
Engineering Practices
Organisations I have consulted
ServiceNow, McKinsey, Verifone, Sunlife Financial, Honeywell,
Fidelity, SAP Labs, Grab, Sourcebits, Dell, Dell EMC, Nets
Norway, Maersk, NEC Technologies, Reliance JIO, Reliance
ADA, Ericsson, Orange, L&T Infotech, Gemalto and many more.
4. Today we are going to talk about the Scrum Team & also their JIRA experience..
PAM
Product
Owner
SAM
Scrum Master
DAM
Development
Team
5. We used various physical Visual Indicators..
.. and were also
happy while we
wanted to go
digital as we were
also facing some
limitations..
.. like working in
distributed team,
archiving our
work, multi team
work, focus more
on creating values
then managing
board..
6. Key Questions
● Can we get the online board like the visual board that we have been using?
● We use diff. color codes today to differentiate various issue types?
● Can we immerse our DOD in different columns?
● Can we showcase risk and dependencies?
● Will it help us in reducing our manual work?
7. The journey
begins
PDCA
● Plan mode for backlog
management
● Active Sprint mode to assure
delivery
● Report mode for tracking
progress
● Dashboard for quick glance
● Filters to find anything
7
8. We want this from JIRA
8
PLAN
RELEASE
REPORT
TRACKJIRA
13. Backlog Mode
- It has total 3 panels
- Version, Epic and Backlog
- Version - Create a version which you are currently working on and also other future versions if you want
to.
- Epic - The bigger stories are called EPICS which is further on broken into small stories which when refined
further to get done into sprints. Here we can add issues which could be Story, Bug, Tasks or other type
- Backlog - here you manage the list of issues that you want to finish in a version which you can also
categorize into sprints and the active sprints are always at the top and the orders of issues should also
signify their priority
13
14. Create a version
- Expand the VERSIONS panel by clicking on it
- Click on link - Hover the cursor on Versions heading and you will get the link to
create version.
14
15. Create EPICs
- Now it’s time to create the backlog first which is done by identifying the high level stories or say the
requirements that are bigger in size also called EPICs.
- There are 2 ways of creating it. One is to click on CREATE button in Navigation panel.
- Same like Versions, click on the EPICS panel and hover the cursor on EPICS heading to get the CREATE
EPIC link. Click on it and fill up the following details:
15
16. Create Issues in EPIC
- Once the issue is created then the entry will
be updated in EPICS panel
- To create issue in an EPIC, either you can
create it through CREATE button from Top
Navigation Panel or simply expand the Epic
and click on CREATE ISSUE IN EPIC link.
16
17. Create an
issue in Epic
- Fill up all the entries
- Issue type shall be
story in EPICs
- Labels will help us in
segregating the issues
by creating filters
17
18. Epic looks like this : When stories are not part of
current sprint
18
19. Epic looks like this : When stories are part of
current sprint
19
21. Now it’s time to start the sprint
First step : Create a new sprint
// update the sprint name and number
21
22. Move the items from the Backlog to the sprint
created
22
23. Ensure all the stories planned are moved in the
corresponding sprint before starting the Sprint
planning meeting
- In sprint planning meeting, product owner educates the team about planned
stories
- Team discusses the details of all the stories till they get clarity and confidence on
creating the technical tasks to complete the stories
- Recommendation is to create the technical tasks as sub-tasks in corresponding
story : this is useful when you are only doing story point estimations
- When you are estimating in hours, better you not create the sub-task and instead
create the tasks and link them to stories. BECAUSE – currently jira is not
supporting the sum of estimates of sub-tasks as the Original Estimate task
23
24. Create sub-task in a story
Story description and all other options can be viewed in the right-most panel which
only get appeared once the story is clicked
24
25. Create sub-task
in a story
● Click on the CREATE SUB-TASK
Button
● Enter all the relevant details.
● You can attach the documents
and also assign the tasks if
needed.
● Please fill in the estimates
25
27. Start the sprint
Remember, the sub-tasks are not visible on BACKLOG
mode but they can be viewed once you go into
corresponding stories and also on ACTIVE SPRINT mode if
the story is part of the current sprint.
Also, sum of estimates of all the stories should not exceed
the capacity planned for team so as to avoid over
expectations.
Click on the START SPRINT button so as to view the items
in Sprint backlog on ACTIVE SPRINT mode.
Select the start date and end date of sprint before clicking
on START SPRINT.
27
28. Active Sprint Mode
● New Items in the backlog moves to To Do which are yet to be started
● Items from previous sprints if any will rest in their respective states.
● Each column signifies the current state of item.
● A story gets moved to DONE only when all the sub-tasks & linked items are moved to DONE otherwise the story
stays UNDONE and goes to the next sprint for completion
28
30. Remember: Story is done only when all sub-tasks & linked items are done
Legends: Sprint name, includes goal, timer, columns, swimlanes, quick filters, board
setting option, complete sprint, expand view for task or stories, tickets – assignee,
estimate, priority, type of issue, unique id
30
