My Old IIS.NET BlogTechNet Magazine Articles Learn about IIS7 from a book I wrote a few years back!
It seems that many people will get the first iteration backlog workbook working and then they will copy & paste it for future iterations. This is what we started doing until we found out just how messy this really is. The Agile iteration backlog workbooks are very useful for Agile (and SCRUM) teams to understand their capacity with interruptions.
These workbooks are very useful, though, there is some confusion often by those using the workbooks what to do when a new “Sprint” (or “Iteration” – used interchangeably in this post) is started. The copy & paste exercise *might* work but often it locks the workbooks up due to the macros getting unhappy. This is the point of today’s post.
I will walk you software dev managers (project, pm’s, or whatever title you have) through starting from scratch at each sprint and utilizing the workbooks to track progress.
The first step is to select the iteration backlog tab of your previous sprint’s workbook by click on it, then locating the Iteration Path column and moving all work items back to the Backlog iteration. To do this, here are the step-by-step pieces -
The next step, often overlooked, is to create a new List-based query that pulls all the work items and columns for your upcoming sprint. In this step, I will walk you through step-by-step creating the new query that will be utilized by your new Iteration backlog workbook.
The next step actually lights up your iteration backlog by binding the workbook to the query you’ve recently edited and saved. This tells the workbook what data to pull in to manage for this sprint. Let’s walk through this binding process…
NOTE: This step assumes you’ve got a folder under documents called Process Templates. If you do not, then you will need to locate where you’ve got a file named Document Template – Iteration Backlog.xlsm and open it. This file is bound to the project automatically and should be made available as part of your creation of a new project.
That’s it. You are now ready to start pulling items from your backlog and assigning them to the sprint and they will now show up in your workbook. Please keep in mind that you utilize the Product Backlog workbook to set the iteration path and then, once you’ve selected your sprints scope, you then open the Iteration backlog and start setting your Remaining Work & Completed work, Capacity, etc.
In today’s post, I wanted to share with project managers how they can best utilize the great workbooks that are part of TFS 2010. The unfortunate time comes when you’ve got to understand how to take a template all the way to a workbook and this wasn’t something that necessarily just “made sense.” Today, I walked you through the steps to go from a template (shipped with TFS) to an actual workbook with actual data.
If you want to simply your life try Urban Turtle. They provide a great planning board and task board over the web to manange your Agile Project. urbanturtle.com
I like that tool with the drag and drop over the web !
We installed Urban Turtle and I think the Planning Board & Task Board are nice. However, we found them to be a bit ackward and ultimately abandon them. The planning aspects & task board are nice...
Our team's ultimate review said that it just didn't make sense to use it since we spend zero time utilizing the web interface. All of our work is done in Visual Studio and we are ultimately looking for a planning/task board that aids where we spend time.
The drag & drop was nice but overall we ended up uninstalling :(
Thanks though for the comment - everyone has their opinions and it sounds like Urban Turtle is working for you.