Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Agile Reporting in JIRA

1,430 views

Published on

ome teams find it difficult to measure the success (or failure) of Agile projects. In many cases this is because the link between process and technology is absent and the right tools are not being used - or are not being used in the right way. In this presentation we will introduce Atlasssian products that bring agile reporting to life.

Published in: Software
  • Be the first to comment

Agile Reporting in JIRA

  1. 1. © 2016 cPrime Inc., All Rights Reserved JIRA Agile Reporting Presented By: Monte Montoya
  2. 2. About cPrime cPrime is an Alten Group Company 2
  3. 3. Presenter Background Monte Montoya CSM, CSPO Over the past 5 years, Monte has been managing software development and process development projects for Fortune 500 companies. His experience with the Atlassian clients has been in designing and building custom Atlassian products and Atlassian solutions. He has helped companies like Apple, PayChex, Enterprise Rent-A-Car, Uber, The Tradedesk and more. 4
  4. 4. Webinar Agenda • JIRA Reporting with Gadgets • Roles & Ceremonies • Demo 5
  5. 5. Scaling Agile Models • Many people bring out the lack of metrics in JIRA. As organizations scale, the need for reporting needs to support: • Release Level • Team Level • Role-Based Ceremonies • Each of these can be interpreted differently by organization but we will start with a few. Your tools must support your organizations methodology! 6
  6. 6. © 2016 cPrime Inc., All Rights Reserved Project Burnup Release Metrics - progress against functionality over time Estimate Accuracy Gadget Team/Sprint Metrics - comparing PBI’s estimated vs actuals. Epic Reporting Charts Epic Metrics - viewing your large chunks of work Program Boards for JIRA Release Metrics - release planning meeting and dependency management Links will be provided in follow up email.
  7. 7. Common Scaling Elements • Foundation based on iterative planning and delivery • Focus on delivery of business value • Centralized planning and decentralized decision making • Cross-team and Cross-organization Planning • At each level and across teams • Reporting on features and progress • Alignment of requirements 11
  8. 8. Containers in Agile Tools Collaboration Communication Planning & Refinement Tracking & Reporting Traceability Process Enablement Your work and containers must support your Scaling Agile methodology 12
  9. 9. Delivery & Support Alignment & Reporting Strategy Levels of Organization & Hierarchy Stories Initiatives Features Portfolio Team Program & Product Team Delivery Team 17
  10. 10. Alignment & Reporting Strategy JIRA Organization & Hierarchy Initiatives Features 17
  11. 11. Release Planning Meeting Where Business and Delivery meet.
  12. 12. The Meaning of Release Definition: A collection of Sprints Purpose: Guarantee ‘shippable’ quality All Releases Guarantee Deliverable Quality Checkpoints of known quality Delivered at convenient intervals Have value to justify delivery
  13. 13. Release Planning… Release Planning produces a Release Plan – Estimates for Stories, Epics in Release – Rough map of Stories to Sprints – Dependencies between Stories, Teams Release Planning can be expensive – 1—3 days for all Teams and members Value of Release Planning must justify the cost – Reduction in confusion due to planning cross-Team dependencies – Necessary to understand how external resources may be engaged – Required to plan for customer commitments
  14. 14. Standard Roles for Release Planning Area Product Owner(s) • Define Vision for Release • Generate consistent priorities for Release • Make big-picture tradeoffs Teams and ScrumMasters • Define estimation techniques • Estimate capacity for Release • Understand architecture / infrastructure implications Team Product Owners • Create Product Backlog Items • Draft Release Plan, dates, across all Teams • Clarify requirements for Teams Program Manager(s) • Assists cross-Team collaboration • Captures Release Plan (with cross-Team dependencies)
  15. 15. Release Planning Meeting Backlog Development How we Plan Cross-Team Requirements 1. Write the Epic 2. Decompose Epic into Stories 3. Assign child Stories to relevant Teams 4. Identify dependencies between child Stories – Create a Dependency Map – Dependency Map is any visual representation of dependencies 5. Estimate, schedule child Stories for appropriate Sprints
  16. 16. Executing & Managing the Release Executing the Program Increment: • Teams Execute on the Stories • Conduct Scrum of Scrums, Manage dependencies • Conduct Release Meeting • Report metrics
  17. 17. Program Team Needs Team needs to: determine if the release date will be met and test some what-if scenarios to determine what changes can be made to ensure the release date is met 17 Any cross-team dependencies getting in the way? Where are we in process of delivering our features? What percent of the feature is complete? Are we going to deliver in budget and on- time? What are the details of this feature? Are there multiple teams working on it? Can I see Program dashboard of most important metrics?
  18. 18. Product Team Needs Team needs to: Prioritize and groom the backlog, need clear visibility into status and progress of the projects 18 Any cross-team dependencies getting in the way? Confirm ranking of the backlog is in alignment with top ranked features How is our release progressing? Communicate changes to work in progress Communicate acceptance criteria to the team
  19. 19. Delivery Team Needs Team needs to: Track and manage sprint commitments, work assignment, and impediments for optimal velocity 19 Any cross-team dependencies getting in the way? We have room in the sprint to take on next item? Which one? What have we completed? Do we have capacity to take on more in this sprint? What is our remaining ToDo? What discussions did our offshore team have yesterday? What is our velocity? Let’s break this work down…..what do we need to do and who is taking it?
  20. 20. © 2016 cPrime Inc., All Rights Reserved Project Burnup Release Metrics - progress against functionality over time Estimate Accuracy Gadget Team/Sprint Metrics - comparing PBI’s estimated vs actuals. Epic Reporting Charts Epic Metrics - viewing your large chunks of work Program Boards for JIRA Release Metrics - release planning meeting and dependency management Links will be provided in follow up email.
  21. 21. Metrics – Program Board Visualization Visualize your release:
  22. 22. Metrics – Feature / Epic Completeness Percent Feature Complete:
  23. 23. Metrics – Burn Up Burn Up:
  24. 24. Metrics – Estimate to Actuals Estimates to Actuals:
  25. 25. DEMO 22
  26. 26. Q & A 22
  27. 27. THANK YOU! 23

×