The customer want to see initial estimates (rough estimated in XM) to be able to prioritize the stories within iterations. This part works pretty fine now.

During the iteration the customer would like to see how many hours are remaining at any given moment. If we store the remaining hours in an extra field of a task, we can show them in a graph. (dylan: to me it makes more sense to store the estimate of the remainder in the booking. Everytime you do some work you reestimate the remaining time. The task level estimate would be based on the latest book estimate)

To make the UI even more usable in the story view's tasks listing the remaining column could provide a dropdown to allow developers to change the time remaining ( but stores that by increasing the estimate). Most often a developer first estimates how much time it will take to finish the task any way, so it saves him the manual calculation to subtract the already worked hours.

iteration view

• Shows rough estimate for tasks in days in the states open and estimated.
• Once all tasks are added and the tasks are in progress, show the total of all tasks, in days.