NOTE: THE STEPS OUTLINED IN THIS POST ONLY APPLIED TO TFS 2010 BETA 2. PLEASE SEE THIS POST FOR THE SIMPLIFIED RTM STEPS.
Visual Studio Team System (VSTS) 2010 Beta2 introduces new features and capabilities to help agile teams with planning. One of those features is “out of the box” Excel workbooks that ship as part of the MSF for Agile Software Development v5.0 process template
This article describes the steps you can take to enable the Iteration Backlog workbook for existing Team Projects not based on the MSF for Agile Software Development v5.0 process template. This post is one of a series about upgrading Team Projects to take advantage of new features that ship in VSTS 2010. To simplify the steps this article assumes you’re existing Team Project is built on the MSF for Agile Software Development v4.2 process template.
To get started you’ll first need to download the MSF for Agile Software Development v5.0 process template from your Team Foundation Server. We need to download this template to get a copy of the Iteration Backlog workbook.
Next, let’s modify the Task work item definition in your current project to include the fields required by the Iteration Backlog workbook.
witadmin.exe exportwitd /collection:http://myserver:8080/path/mycollection/p:myproject/n:“Task” /f:MyTask.xml
<FIELD name="Original Estimate" refname="Microsoft.VSTS.Scheduling.OriginalEstimate" type="Double" reportable="measure" formula="sum"> <HELPTEXT>The number of hours originally estimated to complete this task</HELPTEXT></FIELD>
<CONTROL type="FieldControl" fieldname="Microsoft.VSTS.Scheduling.OriginalEstimate" label="Original Estimate &(hours):" labelposition="Left" numberformat="DecimalNumbers" maxlength="10" />
witadmin.exe importwitd /collection:http://myserver:8080/path/mycollection/p:myproject/f:MyTask.xml
In order to use the Iteration Backlog workbook you must create the appropriate query in Team Explorer.
Next, we’ll bind the query we created in Step 3 to the workbook.
The final step is to add a set of document properties that allow the workbook to communicate with the TFS reporting warehouse. Before we create the properties we need to collect some information about your project. The first piece of information comes from the table created in the previous step. As you collect these properties, copy them into notepad so they can be used in later steps.
Your new Iteration Backlog workbook is now attached to your Team Project and can be used to plan an iteration. To preserve the workbook you should save it to a permanent location (SharePoint portal, etc).
After you upgrade your server to Visual Studio Team System 2010 Beta 1, you have a wealth of new features
In Step 3 – Create an iteration backlog query.
Would'nt the work item type be "task" instead of "scenario"?
You're right Bertrand. I've corrected the typo.
For the life of me, I cannot get the burndown chart to work.
It spins forever connecting to the server and then bombs.
I have taken a copy of the chart down and walked through all the hidden sheets, macros, DocumentProperties, etc and cannot find out what to do. Everything "kinda" appears to be in place.
The only thing that looks awkward is the lack of data on the "BurnDownData" tab. But that was hidden, so I figured it was supposed be filled in dynamically somehow. (appears that way from the macros also).
Our PMs are chomping at the bit to enable this. It should have just worked out of the box I thought.
I REALLY need help if you can. We are trying to roll out TFS 2010 and need this to help PM work daily. How can I get ahold of someone?
We are not running any configuration scenarios that are non-standard.
Russell - I'd be glad to help. Can you email directly at firstname.lastname@example.org?
Have MS resolved the errors in Iteration backlog workbook due to the iteration name change?
I am still waiting for the solution for this. We can't do any project planning in TFS due to this as we renamed the "iteration 1" in the very beginning.
@StanMar - Sorry you're getting that error. Have you tried downloading an unbound copy of the workbook as described here: blogs.msdn.com/.../unbound-agile-workbooks.aspx
That should do the trick as it gives you a fresh, unbound workbook. This bug is on our backlog.
Yes, I've tried downloading an new copy from the Process Template Manager and use it locally. But it still didn't work.
We renamed "iteration 1\iteration 2\iteration 3" to MQ1\Sprint1\Sprint2 in the very beginning of the project setup and have created work items under each iteration.
We can connect the unbounded iteration backlog to TFS and configure a new list in the iteration backlog spreadsheet. But we get "the value you entered is not valid" error when trying to change the Iteration from "\Iteration 1" to "\Sprint1" in the Settings spreadsheet. The burndown sheet also returns "\Iteration 1 is not in the cube" error.
PS. I am unable to complete the Step5 as you described above.
•Switch back to the Iteration Backlog workbook. Click the Office button and select Prepare – Properties.
•Click the Document Properties – Server drop down and select Advanced Properties.
I didn't see a Office button on my iteration backlog and not sure if it is related to the problem I am facing.
@StanMar - the steps in this post are no longer relevant... which is why I pointed you to blogs.msdn.com/.../unbound-agile-workbooks.aspx. You don't need to do a bunch of the additional steps in this post.
Try the steps in the post above. When you get to the settings tab, you can only select a value that is returned in the query. In other words, you'll need to ensure that your query returns a work item with a value of "Sprint1" before you'll be able to selected it.
Let me know if that works.
I tried the downloaded interation backlog workbook. I am able to configure a new list in the Iteration Backlog tab and select from the query I saved in My Queries. However, I didn't see my interations (like Sprint1, Sprint2) in the Iteration droptown list in the setting tab. I only shows "interation 1" in that field.
Is there anyway I can troubleshoot and debug?
thanks a lot
@StanMar - that cell on the settings tab will only display a subset of what is returned in your query result. It's hardcoded to "Sprint1" at the start... but once your query results return something else, those values should be avialable in the cell drop down list. Let me know if that works.
Nope. I expect the iteration in the settings tab displaying "Sprint1", but "Iteration 1" is the only item available in the iteration dropdown list.
I renamed iteration1\iteration2 to Sprint1\Sprint2 in the Team Explorer\Project\Team Project Settings\Areas and Iterations right after I created the project. I didn't know it will create so many problems.
For instance, the folder name in Team Queries still remains "Iteration 1", "Iteration 2" and I can't access any of the team queries under "Iteration 1" folder. It shows "TF51011 error: the node specified is not found in the hierarchy" when you click a query under Iteration1 (such as Active bugs, Active Tasks). Rename folder name "Iteration 1" to "Sprint1" doesn't help.
Looks like it also creates problems in the iteration backlog and product planning workbooks. I am able to configure a new list in the Iteration Backlog tab and select from the query I saved in My Queries. But the Iteration dropdown list in the settings tab doesn't get result from the query I configured for the list.