Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Transcript of JIRA Overview
To build and maintain software, we have to deal with issues (tasks, ideas, requests, bugs...) in an organized manner
Company behind JIRA... help teams of all sizes track and share everything, work smarter, and create better software together.
Demo / Q&A
Quick starts for users, Admins and Agile
JIRA: track, plan, analyze
GreenHopper: Agile Software Development
Bonfire: Testing for Agile teams
Project & Issue Tracking
Collaboration & Content Sharing
Distributed Version Control
JIRA creates harmony by wrapping issues with a process... your process, not someone else's
JIRA is simple, configurable and has an ecosystem of add-ons
Foundation of Atlassian's product suite
Processes that JIRA could manage
(bye bye OTRS)
Transitions can optionally define:
Screen/form, Conditions, Validators & Post actions
Become a JIRA Ninja!
Agile Software Development
"... a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle"
Split your organization into small, cross-functional, self-organizing teams
Two popular Agile methods:
Split your work into a list of small, concrete deliverables. Sort the list by priority and estimate the relative effort of each item
Split time into short fixed-length iterations (usually 1 – 4 weeks), with potentially shippable code demonstrated after each iteration
Optimize the release plan and update priorities in collaboration with the customer, based on insights gained by inspecting the release after each iteration
So instead of a large group spending a long time building a big thing, we have a small team spending a short time building a small thing
Legacy Enrollment Setup requests
KYN, MAT, OBIEE...
collection of issues (KYN, MAT, OBIEE, SOC2)
a software bug, a project task, a help desk ticket, a leave request form...
the movement (Transition) of an issue through various Statuses
JIRA Standard Workflow
Create some issues
Transition them through workflow
Auto escalations: https://confluence.atlassian.com/display/JIRA/Jelly+Escalation
Workload Pie Chart Report * — Shows the relative workload for assignees of all issues in a particular project or issue filter.
User Workload Report * — Shows how much work a user has been allocated, and how long it should take.
Version Workload Report * — Shows how much outstanding work there is (per user and per issue) before a given version is complete.
Version Time Tracking Report * — Shows progress towards completing a given version, based on issues' work logs and time estimates.
Single Level Group By Report — Shows the search results from an issue filter, grouped by a field of your choice.
Created vs Resolved Issues Report — Shows the number of issues created vs number of issues resolved over a given period of time.
Resolution Time Report — Shows the average time taken to resolve issues.
Pie Chart Report — Shows the search results from a specified issue filter (or project) in a pie-chart, based on a statistic of your choice.
Average Age Report — Shows the average age (in days) of unresolved issues.
Recently Created Issues Report — Shows the rate at which issues are being created.
Time Since Issues Report — Shows the number of issues for which your chosen date field (e.g. 'Created') was set on a given date.
How does Agile Scrum work?
(KYN / MAT issues & user stories)
(1 - 4 week iteration)
Subset of issues/user stories for Sprint