2. Agenda
• Introduction to JIRA
• Key Features and Benefits
• Agile Methodologies in JIRA
• Issue Types & Workflows
• Boards: Scrum & Kanban
• Reporting & Dashboards
• Best Practices
• Q&A
3. What is JIRA?
• A project management tool developed by
Atlassian
• Primarily used for issue tracking and Agile
software development
• Supports Scrum, Kanban, and hybrid models
• Highly customizable to fit various team needs
4. Why JIRA?
• Agile project management support (Scrum &
Kanban)
• Customizable workflows tailored to teams
• Real-time reporting and analytics
• Efficient issue tracking and assignment
• Integration with Confluence, Bitbucket,
GitHub, etc.
• Scalable from small teams to large enterprises
5. JIRA Key Terminology
• Issue: A task, bug, story, or other unit of work
• Project: A collection of issues under a single
objective
• Epic: Large user stories that can be broken
down
• Story: A user requirement or feature
• Task/Sub-task: Work assigned to team
members
6. JIRA Agile Boards
• Scrum Board: Used for iterative development
• Kanban Board: Continuous workflow
• Supports backlog grooming, sprint planning,
and retrospectives
• Ideal for support teams or ongoing tasks
7. JIRA Workflow
• Statuses: To Do → In Progress → In Review →
Done
• Transitions: Define how issues move between
statuses
• Conditions, Validators & Post Functions
• Customize per team/project needs
8. Creating & Managing Issues
• Steps to create an issue
• Assigning priority, labels, due dates
• Linking issues: blocks, relates to, duplicates
• Attaching files, comments, and watchers
9. Sprint Planning in JIRA
• Creating a sprint
• Adding issues from backlog
• Estimation using Story Points
• Starting and completing a sprint
• Burndown chart analysis
10. Dashboards & Reports
• Create personal/team dashboards
• Use gadgets like: Pie Chart, Created vs
Resolved, Two-Dimensional Filter
• Sprint reports, Velocity, Control Chart,
Cumulative Flow
• Filters & JQL (JIRA Query Language) for
advanced views
11. Best Practices
• Keep workflows simple and clear
• Use components and labels wisely
• Regularly groom your backlog
• Encourage team collaboration with comments
& mentions
• Make use of keyboard shortcuts
• Automate where possible