A quick guide about one of the Free Telerik TFS tools. So here we go.

After my last blog about these two tools, I had time to test both tools.  In this post, I put my attention to the dashboard as several teams here want to have something like this.

In my earlier post, I stated that I couldn't get it up.  Txs to Joel Poiron, I saw it was because my system couldn't copy the builderror.wav file into the Telerik dashboard folder in MyDocuments.

After some investigation at my site, I became aware that there was a policy which doesn’t allow us to copy music files on this folder (it's a network folder).

So after talking to security, my account was disabled for this policy and I was able to copy music files.  This problem, solved I run again the dashboard and there it was running smoothly.

And it works very fine.  I just took the default settings of widgets and added 3 projects.  For testing purposes, I reduced the recycle time to 30 seconds instead of 300.

See here some screenshots.

 

Project using the Conchango Scrum template 2.2, using TFS full blown and all the widgets.

Project using the Conchango Scrum template 2.2, using not everything in TFS and all the widgets.

Project using the Conchango Scrum template 1.2, using not everything in TFS and all the widgets.

As you can see, even with the last project, the dashboard still runs, but some widgets can't be used.

So a little about how to setup and configure the dashboard.
You can start up the dashboard din two ways:

1. Directly by clicking the Telerik TFS Project Dashboard
2. From within the Work Item Manager

Just one reminder, if you have the dashboard already running, you will get a message when starting it the second time to close the first session.

We will focus now only on the first method.
When the dashboard has started, you will see that there are no projects to display.

Just press F2 to go to the configuration screen.

You will see the configuration screen.  On the first tab you could change some basic settings.  Click on the projects tab at the left side.

Here you can add and configure the projects you want to see.  So click "Add project".  You will get the standard TFS project selector window.  Choose the TFS server and the project.
Next you will get a question where to store the User settings.  this can be on your TFS server in the selected project or locally on the computer.  You can always change this later.

Make your selection.  Now that the project is added, you need to change the configuration to work with your TFS.  First see if the default basic settings are good for you, otherwise just change them.  Next press configure to configure the widgets to use, the TFS datawarehouse connection string,...

When the config screen is open, you see that you need to setup the connection string first.  But you also have tabs for the images.  Opening this will give you the list of TFS users.  Here you can add for each user a nice picture .  Also there are tabs for every widget that can be used in the dashboard.  I'm not going into detail for the widgets.  Just see and you will see how easy it is to configure them.  or you can leave them with the default values.

Press save to store the info.  Next you can add another project or press save here and view your beautiful TFS project dashboard.

For the moment we already have 2 teams (with a total of 8 projects) who are interested in this dashboard after seeing my POC.  Instead of a 19" monitor like I have, we will supply them a nice 30" monitor....

Some (personnel) thoughts about it:

1. You can't change the path where to store your settings,...  It's always in MyDocuments.  So when you have like us a policy that you can't store music files on it, it won't work, because it will copy one .wav file.  I hope in the next version you can choose your storage path.
2. The startup is slow.  It took several minutes to start up.
3. Best is to use a dedicated PC.  Because starting up another application will result in performance loss of the Dashboard.
4. Mostly the memory and processor usage is very good.  But I had a few times where the process performance went up to 70% and the memory usage up to 1.6 GB.  When this is the case, you better kill the process, because pressing f.e. F2 will result in waiting for more than 5 minutes and nothing more than hanging of the application happened.
5. It's free and very good.  Even the support is great.
6. It's beta for the moment, keep that in mind.
7. Two system requirements are needed:
• VS 2008 Team Explorer
• .Net 3.5 SP1 runtime

I'm eager to see the first official release.