Thanks to the roughly 100 of you who attended the Denver VS.Net User Group. While I’m sure you all showed up primarily for the free food and door prizes, I appreciate the level of interaction during my presentation last night (“Team Foundation Server: Today & Tomorrow”).
As promised, here is the presentation I used last night (posted on SkyDrive):
Please send me feedback or any other questions you might have!
The dinner and door prizes were swell, but I actually showed up for your talk. As a tester, I'm afraid I rarely attend the VS users' group. As an advocate for building better software, this was just what I needed. After hearing about upcoming features like hierarchical work items, better process templates, and improved test management features, I'm more confident that TFS can meet our needs here at DPS. Many thanks for posting the slides!
Hi Steve, thanks for the presentation. I'm now working on setting up a nightly build on our system, spurred by what you showed us about Build in TFS.
One question I have though that didn't occur to me at the meeting:
Management wants a way to view how we estimate our work vs. what the work actually takes. That is, they are looking for metrics on how much effort, for example, the average work item took. The idea is that we'll be better able to determine how much we want to take on in the next release.
I think I saw something like this at the meeting. Is there a report that addresses this? Is there a recommended practice in TFS to handle this sort of thing?
We've been trying to do something along these lines for a while. Basically buy using spread sheets and having people fill them out independently. We've tried this sort of approach a couple of times and it eventually gets forgotten.
Any ideas you have on this matter would be appreciated.
There are a couple canned reports which might get you close, such as "Actual Quality vs. Planned Velocity" and "Project Velocity". That said, they probabl won't give you the exact info you want. So two other thoughts:
1) You can use Project to do this, which integrates with TFS
2) Query the reporting warehouse (with via SSRS, Excel, whatever), and build a report that shows disparities between estimate an actual. I'll see if I can come up with an example in the next few days.
Thanks for coming!
much obliged for the suggestions! That should get me started and then we can evolve this for our team as we go along.