Being able to monitor business value delivered seems to be table-stakes for Agile, yet there is no mechanism for reporting nor tracking of business value against completed stories.

by: Catherine L. | over a year ago | Reporting & Analytics

Comments

• I agree that there is value in having this feature, but the cost of implementing this might not be worth as much other requests.
  
  I say this because it should be the Product Owner's role to prioritize work based on value and the team should be working it in that manner. You can already use priority or custom fields to put this value ranking in the system.

  by: Kevin S. | over a year ago

• We do this. We just added some custom fields to the Requests, so we can enter values and then track when the value has been gained.

  by: Toni S. | over a year ago

• this would be useful to have as a first class attribute against the story - V1 could then auto-calculate effort to value. i agree with the original requester - this would be very useful.

  by: Ian E. | over a year ago

• Value is a key piece of information for a team that uses Scrum (and most other agile approaches). Having selected the Scrum option when deploying, I'm very surprised that a basic piece of the approach has been omitted. It's as important as the estimate. It needs to be there.

  by: Shawn L. | over a year ago

• this is especially useful when trying to make the case for increased resources to justify increasing the scope of work done per sprint. having to create custom fields and a custom tracking/reporting process sounds unduly complicated. Using the priority field for this seems very 'blunt' and not useful for calculating any real differences across work.

  by: Derek .. | over a year ago

• As of the Winter 2012 Release, Epics support the ability to define and track value.

  by: Mark Crowe | over a year ago

  official response