JIRA Dashboards and Metrics
Vložit
- čas přidán 28. 05. 2024
- In this webinar, we will take a look at the only two JIRA reports that a scrum team really needs, whether they’re just starting out or well on their way down the path to Agility. We’ll also review two other JIRA reports that are great for stakeholders and process nerds alike.
Finally, we’ll put it all together into some sample JIRA dashboards that provide the right kind of visibility from a variety of perspectives within an organization.
This webinar is facilitated by Lisa Mabli and Roland Cuellar.
Connect with Lisa on LinkedIn: / lisamabli
Find Roland at LitheSpeed.com.
Sign up for our newsletter: lithespeed.com/newsletter/
Learn about our training offerings: lithespeed.com/agile-and-scru...
Check out our Agile Leadership Academy: agileleadershipacademy.com/ - Věda a technologie
Comprehensive explanation. Very useful for interviews. Thank you so much for sharing this.
To save time start at 10:40.
Story vs task, how my team has differentiated between the terms over the years:
A story is a product requirement that caters to a persona or a user, or a type of user within the product. For example. As an analyst, I want to be able to view A and B side by side. As a manager, I want to see a summary of all work completed by analysts.
A task is something that needs to be done but isn't tied to a persona for the application. For example, Node Upgrade to Version X.XX. Or migrate data from Cluster 1 to Cluster 2. Switch Unit Testing libraries from Mocha to Expect. Tech debt is another example: Refactor/Rewrite logic in some module to apply developer best practices.
Tasks don't check off boxes for user personas, nor does your product owner or stake holders ever want to be bothered with such things, typically. Also, developers are not application personas, typically. In our opinion, it has nothing to do with how many developers can work on an issue.
Thank you for sharing, very useful. I have a question, How will you evaluate the success of the change of a Product Backlog in Jira? Thank you so much in advance.
impressive tutorial for JIRA dashboard
Thanks for sharing this on CZcams. Got some pretty good ideas of which metrics to look for. It's unfortunate that the majority of these reports are only applicable to a scrum board.
I am a program manager working in the PMO my company is going through a business transformation program transforming the business into the new digital world
Very useful
One Quick question, can we bring the velocity report on dashboard by any chance?
Yes! If you have edit rights to the dashboard, just select "Add Gadget" and search for "velocity". Depending on what your Jira admin has enabled, you should see several options that can be configured to suit your needs. Good luck!
@@LitheSpeed Thanks for the reply, i already tried this but don't have those gadgets
Her comments on defining a story are off terribly. The story defines the User functionality. The sub-tasks are the lower level details.