Value Delivered: You’ll need your product owner for this. Ask him to give each user story a value that represents its impact to his stakeholders. You can enumerate this with an actual dollar amount or some arbitrary number of some kind. At the end of each sprint you’ll have a number that can tell you how much value you’ve delivered to your customers through the eyes of the product owner.
This metric does not measure performance, instead it measures impact. Ideally your product owner will prioritize higher value items towards the top of the backlog and thus each sprint will deliver the maximum value possible. If you’re working on a finite project with a definite end in sight, your sprints will start out very high value and gradually trend towards delivering less and less value as you get deeper into the backlog. At some point, the cost of development will eclipse the potential value of running another sprint, that’s typically a good time for the team to switch to a new product.
Group items matching
in title, tags, annotations or url
1More
User-Managed Access (UMA) Profile of OAuth 2.0 - 0 views
API Management tools: How to find the one for you - Developer Economics - 2 views
1More
C++11 and Ada 2012 - renaissance of native languages? - 0 views
1More
Six Docker services making serious waves - ComputerworldUK.com - 2 views
1More
Clocker - Creating a Docker Cloud with Apache Brooklyn « Cloudsoft - 0 views
‹ Previous
21 - 40 of 120
Next ›
Last »
Showing 20▼ items per page