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.
1More
implicit.ly - 0 views
seratch/scalikejdbc · GitHub - 1 views
Clean up Python source code with PythonTidy, available as Sublime Text 2 plugin too - 1 views
What's Your Next JVM Language? - 0 views
When in git - 0 views
1More
Unit testing best practices : Junit Reference guide « How to do in "JAVA" - 1 views
ZFS - The Last Word In File Systems - 0 views
1More
http://sarhaonline.afip.gob.ar/v2/sistema/sarha_planeamiento_desarrollo/ - 0 views
« First
‹ Previous
1081 - 1100 of 1478
Next ›
Last »
Showing 20▼ items per page