Jira
Jira
1. JIRA Context
2. What is JIRA with brief demonstration
3. Why JIRA
4. JIRA Concepts with detailed demonstration
5. Benefits
- To Business Analysts
- To Project Managers
- To QAs
- To Developers
5. Q & A
WHAT IS JIRA
JIRA is a tool developed by Australian Company
Atlassian. It is used for bug tracking, issue
tracking, and project management. The name
"JIRA" is actually inherited from the Japanese
word "Gojira" which means "Godzilla".
Context
report
JIRA In Nutshell
Jira is a cloud- and
subscription-based issue
tracking tool designed to
handle team coordination in It increases and improves
agile software development as productivity by cutting
well down on time wasted on
tracking issues and
It helps it users in coordination.
prioritizing, assigning,
tracking, reporting and
auditing the issues in
form of software It enhances quality by
ensuring all tasks are
requirement, bugs, tasks
and change requests. recorded down with all the
details and followed up till
completion.
It is a highly
customizable platform. It allows to outline the
It's users can customize entire project progress
to match their business and ensures
processes. collaboration with a
multitude of tools.
JIRA features & tools
Scrum Board,
Kanban Board
Agile
Development
Create, handle, and
visualize Epics,
Stories, Sub-tasks Burndown Charts,
Reports Sprint Report,
Roadmaps Velocity Chart
The next section will explain why JIRA is one of the best tools to be used in software development
JIRA Concepts
LEVEL 3 ISSUES
Define issues &
Create issues
(Stories, bugs etc.)
ISSUE TYPES ISSUE TYPES
LEVEL 4
SUB SUB SUB SUB
Breakdown issues TASKS
TASKS TASKS TASKS
into sub-tasks
Projects, Issues & Sub-tasks (Sample of Projects)
Projects, Issues & Sub-tasks (Issue Types & Sub-tasks with
hierarchy)
Confluence
Demo link;
Sprint Backlog
Sprint Board
Kanban Board
Manage Project with Agile concepts- Backlog
Manage Project with Agile concepts- Sprint
Manage Issues – Workflow (sample)
Workflow defines the series of steps or stages an issue/ bug goes through during its lifecycle from creation to the
closing of the issue.
Manage Issues - with Priorities
▪ Usable — Intuitive interface designed with both business and technical users in
mind
▪ Open — An open API, full source code access allow for further integration and
customization of JIRA functionality
Reporting – Some examples
▪ Burn down Chart − Track the total ▪ Average Age Report ▪ Time Tracking Report − Shows the
work remaining, also whether sprint original and current time estimates
is achieving the project goal or not ▪ Created Vs Resolved Issue Report for issues in the current project. It
▪ Sprint Chart − Track the work ▪ Pie chart Report can help to determine whether work
completed or pushed back to the is on track for those issues.
backlog in each sprint ▪ Recently Created Issue Report
▪ Velocity Chart − Track the amount ▪ Resolution Time Report − ▪ User Workload Report − Shows the
of work completed from sprint to time estimates for all unresolved
sprint ▪ Single Level Group by Report issues assigned to a user across
▪ Cumulative Flow Diagram − Shows ▪ Time since Issues Report projects. It helps to understand how
the statuses of issues over time. It much a user is occupied, whether
helps to identify high-risk issues or overburdened or has less work.
unresolved important issues.
▪ Version Report − Track the ▪ Version Workload Report − Displays
projected release date for a version. how much outstanding work is
remaining per user and per issue. It
▪ Epic Report helps to understand the remaining
▪ Control Chart work of a version.
▪ Epic Burn Down
▪ Release Burn Down
Reporting – Some examples
Benefits