Scrumulous 3.2

The following changes have been introduced in version 3.2

• Business Value estimate to stories
• Business Value earned 'burn-up' graph by sprint
• Description field on tasks
• Setting task status to 'done' clears remaining hours
• Added 'ideal line' to the Release Burn-down graph
• Usage Analytics and crash reporting
• UI enhancements and bug fixes

Business Value estimate to stories

There is a new field on stories called the 'Value' field. It works like the 'Size' field, and is intended to capture a poker point style business value estimate. Imagine a meeting of stakeholders all using planning poker to estimate the relative business value of a story.

Business Value earned 'burn-up' graph by sprint

As you complete sprints you can track the business value being earned. The new value points field is used to create a graph of the increasing business value in your product. Only stories in completed status are counted in the calculation.

Description field on tasks

As requested in an iTunes rating, there is now a comments field on tasks. Additional information about the task can be added here. Please Note: App store ratings are a great way to send feedback and help me improve this app.

Setting task status to 'done' clears remaining hours

When you set a task to complete, the remaining hours are now automatically set to 0. A small but handy convenience. If you do this accidentally and wish to get the value back you can navigate back to the task list (essentially cancelling the change).

Added 'ideal line' to the Release Burn-down graph

The ideal line helps highlight variances from the sprint velocity. At the moment, the velocity is calculated as an average of the total points completed per sprint. This is why the burn-down always meets the ideal line at the last sprint. I am looking into adjusting how the velocity is calculated, and adding a field where the calculated velocity can be overridden by a user entered velocity.

Usage Analytics and crash reporting

Analytics have been added in order to help decided where to focus effort and which features are most used. Crash reporting will help make the app more stable and improve the overall user experience. The tracking simply counts screen views and general regional statistics. No personal or private information is tracked.