ConcertCare always believes in knowledge sharing. A practical session how to effectively use scrum using JIRA, a management tool.

1. Scrum with JIRA
Software
BY YOGAPRABA

2. Agenda
 Quick Recap of agile and scrum
 Introduction to Scrum
 How Scrum Works
 What is Scrum Board
 What is KANBAN Board
 Difference between both scrum and Kanban board
 Introduction to JIRA
 What is JIRA
 Features of JIRA
 Why JIRA
 Key points & Terms to know in JIRA
 Getting into JIRA

3. Quick Recap
 AGILE : Methodology. time-boxed, iterative approach to build the projects
incrementally instead of all at once.
 SCRUM: Framework. In scrum, a product is built in the series of iterations
known as sprints or parts.
 Scrum Roles : Product Owner, Scrum Master and Scrum Team
 Scrum Artifacts : Product Backlog, Sprint Backlog and Product Increment
 Scrum Ceremonies: Sprint Planning, Daily Standup, Sprint Review and Sprint
Retrospective

4. Quick Recap
 Product Backlog
 Set of activities(User Stories) that need to be done to develop the software
 Usually, It will be created by Product Owner.
 Sprint Planning
 Key ceremony at the beginning of the sprint.
 What we can deliver to achieve the sprint goal and how we can deliver
 Outcome of this is sprint Backlog
 Sprint Backlog
 Sprint Backlog is a set of activities that need to be performed within this sprint.

5. Quick Recap
 Sprint
 A sprint is a short, time-boxed period when a scrum team works to complete a
set amount of work.
 Heart of scrum
 Daily Scrum
 Meeting has a predefined format, i.e., a team member has to tell what he was
doing yesterday, what he will do today, and what are the things which are
hampering him to complete his work.
 Sprint Review
 The sprint review is a meeting in which team members sit together, and they
give the demo to the client about the product that they have developed in this
sprint.

6. Working of Scrum
 Retrospective Meeting
 A sprint is a short, time-boxed period when a scrum team works to complete a
set amount of work.
 Heart of scrum

7. Introduction to Scrum
How Scrum Works
Some Do’s and Dont’s
What is Scrum Board
What is KANBAN Board

8. Working of Scrum

9. Working of Scrum
Step 1: User stories created by PO in Product backlog
Step 2: Sprint Planning will be conducted
Step 3: As a outcome of sprint planning, Sprint Backlog is created.
Step 4: Sprint is started.
Step 5: Daily Scrum will be conducted.
Step 6: Sprint Review will be conducted.
Step 7 : Sprint Retrospection
Step 8 : Sprint Closure
Step 9 : Again starts from step 1 for next sprint.

10. Working of Scrum – Do’s
 Do’s
 Make sure the team sets and understands the sprint goal and how success will be
measured.
 Do ensure you have a well-groomed backlog with your priorities and
dependencies in order.
 Ensure you have a good understanding of velocity, and that it reflects things like
leave and team meetings.
 Do use the Sprint Planning meeting to flesh out intimate details of the work that
needs to get done.
 Encourage team members to sketch out tasks for all stories, bugs, and tasks that
come into the sprint.
 Leave out work where you won’t be able to get the dependencies done, like
work from another team, designs, and legal sign-off.
 Finally, once a decision or plan is made, make sure someone captures that
information in your project management or collaboration tool, like your Jira
tickets.

11. Working of Scrum – Don’t
 Don't:
 Don’t pull in too many stories, overestimate velocity, or pull in tasks that
can’t be completed in the sprint. You don’t want to set yourself or your team up
for failure.
 Don’t forget about quality or technical debt. Make sure to budget time for
QA and non-feature work, like bugs and engineering health.
 Don’t let the team have a fuzzy view of what's in the sprint. Nail it down,
and don’t focus so much on moving fast that you forget to make sure
everyone’s moving in the same direction.
 Also, don’t take on a large amount of unknown or high-risk work. Break
down stories that are large or have high uncertainty, and don't be afraid to
leave some of that work for the next sprint.
 If you hear concerns from the team, whether it’s about velocity, low-certainty
work, or work they think is bigger than what they estimated, don’t ignore it.
Address the issue, and recalibrate when necessary.

12. Scrum Board
Scrum Board is a board that shows the status of all the activities that need to be done within this
sprint.

13. KANBAN Board
Kanban board is a tool used to visualize the work and limit work-in-progress.

14. Introduction to JIRA
What is JIRA
Features of JIRA
Why JIRA

15. What is JIRA
 JIRA is an issue and project tracking software to plan, track and manage
the projects.
 JIRA is developed by Atlassian Inc., an Australian Company.
 High level of customization ability
 It is mainly used for agile project management.

16. Key features of JIRA
 Issue tracking
 Different types of boards
 Project planning
 Project Backlog management
 Project tracking
 Reporting
 Notifications

17. Why we use JIRA
 Improves collaboration
 Improves tracking
 Better planning
 Increase productivity
 Improves customer satisfaction
 Flexible to use
 High level of customization

18. Terms to Know in JIRA
Issue Types
JIRA Attributes
Workflows
Swimlane

19. Issue Types
 Commonly used issue types are,
 Task – Task that needs to be done
 Sub-task - Smaller task within a larger piece of work
 Epic - Large piece of work that encompasses many issues
 Story - Functionality request expressed from the perspective of the user
 Change Request – Change in given requirement
 Bug - Problem that impairs product or service functionality
 We can create customized issue type also.

20. JIRA Attributes
 Statuses
 Open – Ready for the assignee to start the work
 In-Progress – Being actively worked on by the assignee
 Reopened – The issue was once solved but the resolution was incorrect
 Resolved – Issue is solved but waiting for reporter’s review
 Closed – Issue considered as finished. i.e., the resolution is correct
 Resolutions
 Resolutions are the ways in which an issue can be closed.
 Priorities
 Highest -This problem will block progress.
 High - Serious problem that could block progress.
 Medium - Has the potential to affect progress.
 Low - Minor problem or easily worked around.
 Lowest - Trivial problem with little or no impact on progress.

21. Workflows
 Record of statuses and transitions that an issue goes through during its
lifecycle.
 Statuses – Stage of an issue
 Transition – link between 2 stages

22. Swimlane
 A swimlane is a horizontal categorization of issues in the Active sprints of
a Scrum board, or on a Kanban board.

23. Getting into JIRA
How to login
How to create project
How to

24. How to Login?
 For Concertcare JIRA :
https://concertcare.atlassian.net/
 Type Email ID and Password
 URL will be different, if your JIRA account is
created by Client.

25. Choose the Project

26. Create Issue & Product BAcklog

27. Create Epic

28. Product Backlog

29. Create Sprint

30. Create Sprint Backlog

31. Create Sprint Backlog

32. Active Sprints

33. Complete Sprint

34. Release & Version
Management in JIRA
Create Version
Release
Release Notes

35. Create Version

36. Release
Releasing a version is the culmination of your team's hard work. It may be the
result of many iterations of work across a number of months.

37. Release Notes
Release notes contains the list of items to be delivered in the current release.
It is associated with versions.

38. Titbit - Versioning System
Concertcare follows 4 digit versioning system.

39. Reports in JIRA
Different reports in JIRA

40. Different Reports in JIRA
Burndown Chart -A burn down chart is a graphical representation of work left to
do versus time.
Burnup Chart - A burn down chart is a graphical representation of work
completed versus time.
Sprint Report - The Sprint Report shows the list of issues in each sprint.
Velocity chart - The Velocity Chart shows the amount of value delivered in each
sprint, enabling you to predict the amount of work the team can get done in future
sprints.

41. Different Boards in JIRA
Scurm
KANBAN
Next-gen

42. Different Boards in JIRA
 Next-gen board
This board is useful for those who are new to the agile. It is a very simplified,
straight-forward, and streamlined board.
 Scrum board
This board is useful when teams work on sprints that includes a backlog.
 Kanban board
Kanban board is an agile project management tool designed for the
visualization of work, limit work-in-progress, and maximize efficiency.

43. Scrum Board

44. KANBAN Board

45. Next-gen Board

46. ANY QUERIES?

47. THANK YOU!!
BE AGILE, NOT JUST DO AGILE