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.
Thanks for sharing this on RUclips. 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
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!
To save time start at 10:40.
Comprehensive explanation. Very useful for interviews. Thank you so much for sharing this.
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.
impressive tutorial for JIRA dashboard
Thanks for sharing this on RUclips. 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
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.
Very useful