Keith Rowe's WebLog

Project Management and Visual Studio Team System

What was that about Excel?

When we started designing the project management features in VS Team System, we had a pretty idealized view of the world.  Project managers would sit in their cubicles and grind away in MS Project.  The resulting tasks would funnel into VS Team System to be handed around to all the rest of the team.  We got pretty far along on that model.

We knew that internal to MS, lots of people built spreadsheets to track stuff.  But we just chalked that up to the, how would one say, “loose” way that MS engineers sometimes manage projects.  Surely, IT shops would all be using Project?

Then we went to visit customers.  We were delighted and surprised to see that everyone else uses Excel as much as we do.  So, back to the drawing board, a few more late nights with bad pizza (ok, a lot of late nights), and, voila, Team System integrates with Excel.  I think this is going to be a feature that gets a lot of use in the real world for things like:

1. Light-weight project management - I don't have MS Project.  I don't want to learn all that stuff.  I just want to write out my list of tasks and track them quickly.  For the impromptu project manager, Excel will be a great way to pull together work items quickly.  And you're more likely to have Excel on your desktop than Project.

2. Custom views of the project - you can build a query against the VSTS work item database and attach it to an Excel spreadsheet.  Then, whenever you sync the spreadsheet to the underlying database, you get a current view on only the stuff you care about.  It may be a set of tasks or requirements; it may be a special organization of the tasks that matters to you (organize tasks by component or by use case or by team); it may be a custom project management model you're using (like a SCRUM sprint).  All these and a lot more are possible.  And they all sync back to the one true database, so they're always current and up-to-date.

3. Bulk editing - you need to grab all the tasks assigned to “Bob” and reassign them to “Mary”?  With the Excel integration, you can dump the tasks in a spreadsheet, click the mouse once or twice and drop them back into the database.

4. Reporting - VSTS will have rich reporting through our data warehouse tied to SQL Server (more on that another day).  But, you might not want to learn how to do all that, and you already draw cool graphs in Excel.  Pull over the work items you're interested in and go nuts!

Excel integration will bring a lot of flexibility to VSTS project management.  We'll be bundling in some sample spreadsheets, but we expect to see a lot more good ones out there as people explore what this can do.

Which do you use more, Project or Excel?

Published Wednesday, June 02, 2004 11:48 AM by KeithRowe

Comments

 

Zk said:

At Verizon we built our own web based tracking system (which was basically my job). I'm solo now, but I'm redeveloping the app with .NET and I have a lot of overlap to what the TS team is doing, except I'd be very interesting in adding the capabilities to tie in directly to VS.NET's Team System and have them work together. (Team System doing what it does best, and my tool doing what it does best.)

I guess I'd just add that I've had a lot of requests to tie my product in with MS Project, but never with Excel (beyond reporting).
June 2, 2004 11:56 AM
 

Romualdas said:

Even very big projects can (and mostly are) split into something small (or in other words manageable). But why I am talking about MSF, You guys probably should know that better than me.
This way even HUGE projects finally split into "manageable" Excel sheets anyway (and I believe almost always).
So, forwarding these great news to Lithuania ...
June 2, 2004 12:22 PM
 

Keith Rowe said:

Cool. We're building in a lot of APIs to allow you to control Team System. You can get an overview of how they'll work here: http://msdn.microsoft.com/library/en-us/dnvsent/html/vsts-ext.asp.

We're also integrating with Sharepoint to provide a project site that can reflect all the reports and status of each project. More on that in another posting.
June 2, 2004 12:41 PM
 

Keith Rowe said:

Romualdas,

You're right - projects do get broken down into smaller and smaller units. Some will want to track there pieces in Excel. Others will want to see it rolled up in Project. Since you can keep the same tasks in multiple files and sync them all to the database - everyone can look at the pieces they care about.

We've even built in a system to resolve merge conflicts between multiple people working on the same work item.
June 2, 2004 1:02 PM
 

Keith Rowe said:

And another scenario:

5. Offline work - you can pull a collection of work items into Excel (or Project) and edit them while disconnected from the rest of VS Team System. This may be useful for distributed teams or work on the road.

June 2, 2004 1:04 PM
 

Boris Letocha said:

But it will be possible to NOT use Excel and Project - so directly enter tasks in VS (thinking about rich client - better then Excel not so much complex as Project, and/or Web (not that rich, but accessible to "Other" platform guys)?
June 2, 2004 1:17 PM
 

Romualdas said:

I'm curious, how often it happens software projects to be part of some business development project, where everything (total costs, durations, resources) has to be controlled in one place?
Just a thought - where the Project Server with it's own DB is here? Syncing through MS Project?
June 2, 2004 1:19 PM
 

Keith Rowe said:

Boris,

Yes, you will be able to manipulate work items directly from inside Visual Studio and, in some cases, from a web browser. We expect that developers, architects and others who live inside the VS IDE will do most of their updates there.
June 2, 2004 1:21 PM
 

Keith Rowe said:

Romualdas,

Yes, we will be able to sync between Visual Studio Team System and Project Server. As you do today, you'll open a ppt file, update with new info from VSTS and then sync it back to Project Server.

We are working with the MS Project team to add more features to our Project Server integration story for the next release.
June 2, 2004 1:24 PM
 

Romualdas said:

I will not have to do that, because in our case Project ppt (for manager) and Excel (for teams) is more than enough for projects up to $200k, but others might need syncing.
Anyway, want to thank you - finally something real for the entire team in one place and integrated.
As I see, the "integration" is the product that Microsoft customers (including me) are buying, though it's not in the product list :)
June 2, 2004 2:52 PM
 

Alex said:

Great to hear about the Excel integration...

I tend to use custom spreadsheets that cover the different granularities of the project. Team leaders need to know task levels, whilst PM's need to know how well the modules are tracking at a higher level.

Personally I prefer Excel to Project. Project looks pretty, but I find my Excel tools to be of far more use.

I have one question, we have used MS Raid on a large project we undertook with MS in the past and found the Bulk edit functionality to be invaluable when for instance moving stuff out of triage or bumping it to another release in bulk. Above you say about using Excel to do bulk editing, will this functionality be available inside the defect tracking system as well?
June 2, 2004 3:39 PM
 

Keith Rowe said:

Alex,

We've generalized the idea of defect tracking to work item tracking. "Bugs" are one class of work item. We will also include "tasks", "features", "risks", "issues" and others. You can also add your own work item definitions through an XML Schema that we ship.

Thus, you'll be able to use Excel to bulk edit your defects, just like any other work item!
June 2, 2004 4:00 PM
 

RobCaron's Blog said:

June 2, 2004 8:35 PM
 

AdamC said:

Excel
June 6, 2004 7:48 AM
 

Donavan McDonough said:

By using Excel as the reporting tool of VSTS does that no open you up to the risks associated with spreadsheets?

I am keen to hear your take on this and share it with my blog readers @

The Fragile Last Mile of BI: Spreadsheet Risk & Fraud Analysis

http://blogs.ittoolbox.com/bi/spreadsheet/archives/000613.asp">http://blogs.ittoolbox.com/bi/spreadsheet/archives/000613.asp

and

http://blogs.ittoolbox.com/bi/spreadsheet/
August 4, 2004 4:17 PM
 

Keith Rowe said:


You raise some great points, Donovan. It will be possible to make errors with the Excel spreadsheet.

Fortunately, it is only our secondary solution for reporting. All the data of interest in VSTS is kept in a data warehouse hosted on SQL Server. All the tools, including the build engine, the source code control system, the test manager and the work item database, report their results into that warehouse.

We then use SQL Reporting Services to generate the reports. Out of the box, we will provide over 60 different reports that combine data from all the individual tools to give you great analysis of how your project is progressing.

You can also create your own new reports with the same service.

Team members can also use Excel to manipulate or examine collections of work items. This may lead to errors - but you can sanity check results you generate here against the more rigorous reports coming out of the data warehouse.
August 4, 2004 8:43 PM
 

music said:

August 5, 2004 4:36 AM
 

Keith Rowe s WebLog What was that about Excel | Green Tea Fat Burner said:

June 9, 2009 3:19 PM
Anonymous comments are disabled

© 2009 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Microsoft
Page view tracker