I've got some problems with my TFS Burndown Chart. I've just created an Iteration (Sprint) with no start - end date. Then added some Working Items - Tasks each with their corresponding start - end date (lets say 10/06/2014). 6 days have passed since I realized that my whole Iteration (Sprint) did not have start - ending dates (10/06/2014 - 27/06/2014), so I've added those, but now... my Burndown chart is showing the progress only from dates 16/06/2014 to the current date, up to the finish date: 27/06/2014
Most of My Working Items (tasks) inside the Iteration - Sprint have their Start, In Progress and Finished within the current dates: 10/06/2014 - 16/06/2014.
Please Advice.
Not sure how your tasks have starting/ending dates. I thought all the default templates had Work Remaining on Tasks. Anyways, the burndown operates off the Work Remaining fields of the Tasks, you need to update that appropriately.
You should set start and end dates for the sprints themselves. Without start/end dates for the sprint itself, it can't project how much time you have left given the total task work at the beginning of the sprint. An iteration path (i.e. sprint) is inherently a period of time for doing your work (i.e. 2-4 weeks).
Related
What is the "Ideal Trend" line in TFS Sprint burndown chart based out of? Original Estimate or Remaining Work?
If I add more tasks mid sprint, my remaining work line will show a bump. Will the starting point of "Ideal trend" line also move up in this case?
You can find some explanation here: Sprint Burndown (Scrum).
The Ideal Trend line indicates an ideal situation in which the team
burns down all of the effort that remains at a constant rate by the
end of the sprint.
It is based on Remaining Work and represent how you have to update your Remaining Work in your sprint to get 0 hours of work at the end of a sprint. If you add new tasks after sprint start you will have non ideal line that adopted to new number of hours of tasks and duration of a sprint.
I have a query for "items completed yesterday" which is super useful in standups.
But #today - 1 seems to look at calendar days, not weekdays/workdays meaning that my query isn't useable on Mondays. Is there a way to tweak it to work?
Unfortunately we cannot achieve that.
You can Set working days for team's sprint planning and tracking when calculating capacity and sprint burndown, however it's not apply to work item queries.
So, as a workaround you can create another query with Closed Date = #today - 3 specified if you are using the normal working days...(Means the "Yesterday" is Friday)
More information please see Query by date or current iteration.
I want to get some different reports and charts from Tfs activities and history (most based on task tags and assigned users). for example after 3 monthes I want to know how many hours a user moved her tasks to next iteration, ...
Is there any tools for this?
No such a tool can exactly achieve that. There is an extension Team Capacity Management, but seems it's not apply for you.
If you want to know how many hours a user moved her tasks to next iteration, then you need to get the planned hours then subtract the completed hours in current iteration. Alternatively you can add tags on the work items which moved to the next iteration, then create a query which filter by the tags to get the sum of hours.
e.g.:
Create a query 'RemainingWork' with the column Assigned
to and Remaining Work added in "next iteration" (e.g.: iteration
2 here) to filter the moved work items from pervious iteration with the tag.
Save it in Shared queries
Add Chart for Work items widget in your project dashborad, then
configure the widget. Then you can see the hours a user moved tasks
to next iteration in the chart:
Recently came across "Remaining Work" option in TFS, got no clue what it stands for, is it the time in hours that i am supposed to define against a task.
Remaining work is the number of hours you have left to complete a task. If something is a 4 hr task and at the end of a day you have managed to complete 1hrs work, you would update it to 3hrs remaining. You can update the remaining work as often as you like. You could just 0 it when there is no more work, or every time there is 1hr's less work remaining - or somewhere in between.
From this value, TFS can create a burndown graph of remaining work in an iteration.
There are fields for Original Estimate and Actual Work you can use if you need to track estimates and how long things took.
Remaining Work field can actually show if the original estimate has changed since you started working on a task.
I need to produce a report, similar to the Unplanned Work report included with the MS Agile Process Template, but which lists me all work items which were added to an iteration after a given date.
The work item may have already been created before that date, so I can't used the created date.
Can anyone give any guidance on how I can go about this? If I can achieve it in Excel then that would be perfect...
Thanks.
Ok, took some work. Interesting enough though to put some effort in it ...
First screenshot is a Pivot table connected to the Analysis Cube. The most left colum shows the ID of a workitem. The second column shows the ChangeDate. In the row header I have included every iteration that I am interested in. What you see happening in the Excel sheet is items moving from one sprint to the other. For example, workitem 27 was created for iteration 1 at 14-3-2011. On 13-4-2011 it was moved to iteration 2. On 12-5-2011 it was moved to iteration 3. etc.
If I narrow down the filter to a specific iteration I actually see items entering the iteration and leaving the iteration. If I also change the ChangeDate filter, I can focus on items entering after a specific date, as you requested. Again, you can see item 27 enter iteration 2 at 13-4 and leave at 12-5. You can juggle around with the columns to get the view you want.
Finally, the options I used to get this view from TFS.
Hope this exceeds your expectations :-)