1. Managing Software Development Projects with Jira

2. 2 Agenda Managing software development projects with Jira Types of projects Types of tickets Fields & Relationships SDLC: Kanban SDLC: Scrum Reporting Dashboards Add-ons 1 8 3 4 5 6 7 2

3. PROJECT TYPES

4. 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 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 https://www.atlassian.com/wac/software/jira-agile/whats-new/greenhopper-60

6. TICKET TYPES

7. 7 Ticket Types Epic When to use High-level organizational tool Measuring progress for a feature set Epic Story Sub-Task

8. 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. 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. 10 Ticket Types Task/Technical Task http://www.psdgraphics.com/psd/task-accomplished-icon-psd/ When to use Non-development activities Spikes/Research activities When not to use On anything that will directly impact the system.

11. 11 Ticket Types Improvement https://trackduck.com/en/ 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. 12 Ticket Types New Feature http://maxrsk-rskservicecorp1.netdna-ssl.com/wp-content/uploads/2015/06/nrsk.jpg When to use Tracking requests for new features or functionality. When not to use To assign development work.

13. 13 Ticket Types Bug http://herdingcats.typepad.com/my_weblog/2011/07/connecting-the-dots-in-agile.html 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.

14. FIELDS & RELATIONSHIPS

15. 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. 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. 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

18. KANBAN SDLC

19. 19 Kanban SDLC Planning Board

20. 20 Kanban SDLC Workflow

21. 21 Kanban SDLC Reports & Monitoring

22. 22 Kanban SDLC Reports & Monitoring: Issues Created Report

23. 23 Kanban SDLC Reports & Monitoring: Resolution Time

24. 24 Kanban SDLC Reports & Monitoring: Average Age

25. SCRUM SDLC

26. 26 SCRUM SDLC Backlog View Tip: Name sprints as “Project Name Sprint 1”

27. 27 SCRUM SDLC Active Sprint View

28. 28 SCRUM SDLC Workflow

29. 29 SCRUM SDLC Sprint Monitoring & Reporting

30. 30 SCRUM SDLC Sprint Monitoring & Reporting: Burndown Chart

31. 31 SCRUM SDLC Sprint Monitoring & Reporting: Epic Report

32. 32 SCRUM SDLC Sprint Monitoring & Reporting: Velocity Chart

33. 33 SCRUM SDLC Sprint Monitoring & Reporting: Created vs Resolved

34. REPORTING

35. 35 Reporting Issues Worked On (EazyBI) Issues Worked On Hours Spent Per Issue

36. 36 Reporting Budget Status (EazyBI) Kanban Style Scrum Style

37. 37 Reporting Tempo Timesheets

38. 38 Reporting Scrum Worklogs (Tempo: Excel Export)

39. Dashboards

40. 40 Dashboards Developer Board

41. 41 Dashboards Project Management Board

42. ADD-ONS

43. 43 Add-Ons EazyBI Provides an extensive set of custom reporting options to Jira. Has an additional licensing fee. https://marketplace.atlassian.com/plugins/com.eazybi.atlassian-connect.eazybi- jira/cloud/overview

44. 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. 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. 46 Questions

47. 47 Thank You