Requirements Management and Traceability with Visual Studio Team System 2010

Posted By: Brian Keller | Oct 1st, 2008 @ 11:41 AM | 28,603 Views | 15 Comments
How can you ensure that a requirement has been sufficiently tested? How do you track the work that goes into a specific feature? How much work is left to do before a feature is completed, and how does that feature relate to bigger scenarios or user stories?

Siddharth Bhatia, a senior group program manager for Visual Studio Team System, takes us through an end-to-end example of how Visual Studio Team System 2010 will help an organization manage their requirements throughout the lifecycle of a software project.

This "Humanized Screencast" is best viewed at fullscreen using the high-quality WMV download.

Update: This video was re-encoded to fix some indexing issues at 2:30 p.m. PST. If you downloaded a version prior to that please download a new copy.
Media Downloads:
Rating:
1
0
#Oct 1st, 2008 @ 1:01 PM
AthemeX
AthemeX
Here since the beginning
Hm, near the end the video is broken.. Perplexed can you please fix that because I was quite curious as to what the 'cool visualisation' looked like Wink
#Oct 1st, 2008 @ 1:20 PM
briankel
briankel
Hi AthemeX -

I think you're right, I'm seeing some funky index problems with this video as well on certain machines. I'm encoding a new version now - stay tuned...
#Oct 1st, 2008 @ 2:28 PM
briankel
briankel
A new encoding of this video has been uploaded which should fix the prior index problems. Thanks again for the report, AthemeX.
#Oct 1st, 2008 @ 8:08 PM
codputer
codputer
Don't you know what a cod is?
Just started looking into Team Foundation Server - although I've used all the other MS products.  It's nice to see that everything is being pulled together, getting everything fully integrated.  I bet it was not fun working with all the com object in office and project!

I love the screen cast format - the screen is easily readable, especially on my wide screen monitors!  Much nicer than zooming in and out with a shaky hand.  I'm sure the interviewers appreciate it as well!  Now they can concentrate entirely on conducting the interview!
#Oct 21st, 2008 @ 2:29 PM
Yaron
Yaron
That's all nice and encouraging, but traceability is not just about project management oriented "linking" of tasks for tracking of execution. Its about providing a tool for DOCUMENT traceability - does the developer specification cover the requirement? Do the test cases cover the requirement? See competitors like Doors, Rational (IBM) RequisitePro.
#Oct 24th, 2008 @ 12:52 AM
sbhatia
sbhatia
Hi Yaron,

Thanks for the note.

With particular regard to Word specifications and traceability, we're looking to our partners for that. [Link to our partners]
In terms of test cases and requirements, it is possible to -- very easily -- see what requirements are covered by test cases and even more importantly which ones aren't.

-Siddharth
#Jan 21st @ 9:55 AM
Judy H
Judy H
Which process template was used in the demo?
#Jan 26th @ 7:44 AM
briankel
briankel
I'm pretty sure everything was MSF for Agile.

Brian
#Jul 6th @ 10:20 AM
mglick
mglick

I don't hear anything in the video

Microsoft Communities