Managing Software Development Projects with Jira
2 Agenda Managing software development projects with Jira Types of projects Types of tickets Fields & Relationships SDLC: Kanban SDLC: Scrum Reporting Dashboards Add-ons
PROJECT TYPES
4 Ongoing support projects Projects with variable teams and release cycles When to use Project Types Kanban Benefits No waiting between tasks Less time shuffling resources Less time switching tasks
5 5 Active development projects with a consistent team and release schedule. When to use Project Types Scrum Benefits Iteration planning and monitoring Tracking sprint progress
TICKET TYPES
7 Ticket Types Epic When to use High-level organizational tool Measuring progress for a feature set Epic Story Sub-Task
8 Ticket Types Story When to use Define a single feature to be implemented in the system. When not to use Non-development activities Epic Story Sub-Task
9 Ticket Types Sub-Task When to use Breaking stories into smaller implementation tasks. When not to use On Simple/Short stories Tips Make titles of sub-tasks relate to the title of the parent story. Epic Story Sub-Task
10 Ticket Types Task/Technical Task When to use Non-development activities Spikes/Research activities When not to use On anything that will directly impact the system.
11 Ticket Types Improvement When to use Minor enhancements or adjustments to existing functionality. Small system tweaks of existing functionality. When not to use To add new functionality.
12 Ticket Types New Feature When to use Tracking requests for new features or functionality. When not to use To assign development work.
13 Ticket Types Bug When to use Tracking defects in the system. Includes both internal QA issues and end-user reported issues. When not to use For changes/enhancements to the system.
FIELDS & RELATIONSHIPS
15 Fields & Relationships Components When to use Relate tickets to various aspects of the system. Recommendations Per content type Per section/area of application Global elements (header/footer/Navigation) Per Role/Permission
16 Fields & Relationships Fix Version(s) Type 1 Type 3 When to use Tracking release(s) that the ticket was included in. Recommendations 1 release per sprint Use either semantic or date based versions. We use yyyymmdd.
17 Fields & Relationships Links & Relationships When to use Define relationships between 2 tickets. Provide links to documentation. Recommendations Define bug relationships. Provide links to docs/specs Define dependencies Point to similar tickets
KANBAN SDLC
19 Kanban SDLC Planning Board
20 Kanban SDLC Workflow
21 Kanban SDLC Reports & Monitoring
22 Kanban SDLC Reports & Monitoring: Issues Created Report
23 Kanban SDLC Reports & Monitoring: Resolution Time
24 Kanban SDLC Reports & Monitoring: Average Age
SCRUM SDLC
26 SCRUM SDLC Backlog View Tip: Name sprints as “Project Name Sprint 1”
27 SCRUM SDLC Active Sprint View
28 SCRUM SDLC Workflow
29 SCRUM SDLC Sprint Monitoring & Reporting
30 SCRUM SDLC Sprint Monitoring & Reporting: Burndown Chart
31 SCRUM SDLC Sprint Monitoring & Reporting: Epic Report
32 SCRUM SDLC Sprint Monitoring & Reporting: Velocity Chart
33 SCRUM SDLC Sprint Monitoring & Reporting: Created vs Resolved
REPORTING
35 Reporting Issues Worked On (EazyBI) Issues Worked On Hours Spent Per Issue
36 Reporting Budget Status (EazyBI) Kanban Style Scrum Style
37 Reporting Tempo Timesheets
38 Reporting Scrum Worklogs (Tempo: Excel Export)
Dashboards
40 Dashboards Developer Board
41 Dashboards Project Management Board
ADD-ONS
43 Add-Ons EazyBI Provides an extensive set of custom reporting options to Jira. Has an additional licensing fee. jira/cloud/overview
44 Add-Ons GitHub Usually built-in and already enabled, just needs to be configured. Displays branch, commit, and pull request info on your Jira tickets.
45 Add-Ons TrackDuck Allows client to report bugs directly from website. Captures user browser info and the page the issue was on. We’re looking for an alternative to TrackDuck though due to some platform stability issues and problems with the screenshot capture feature.
46 Questions
47 Thank You