What Information Will Best Support Your Team Foundation Customization Requirements?

What Information Will Best Support Your Team Foundation Customization Requirements? | ASP NET Hosting

Sat, 16 May 2009 02:45:07 GMT

PingBack from http://asp-net-hosting.simplynetdev.com/what-information-will-best-support-your-team-foundation-customization-requirements/

Customizing TFS to fit your process

bharry's WebLog — Mon, 18 May 2009 17:48:26 GMT

Customizing TFS to fit your process can be a significant undertaking if you have an involved and detailed

Customizing work items

Allen Clark's Blog — Tue, 19 May 2009 00:05:16 GMT

Do you customize the work items that you use with Team Foundation? Kathryn Elliot is looking for your

re: What Information Will Best Support Your Team Foundation Customization Requirements?

christoph — Tue, 19 May 2009 10:39:09 GMT

Hi,

i have customzie the MSF AGILE Process only a little bit. But i need to create a TestAreaPath like the existing area path. How can i do this?

It would be helpful that i can upload more workitemtypes for more team project at one time.

At the moment i only need to add workitemtypes or change existing workitems forms and queries.

bye christoph

re: What Information Will Best Support Your Team Foundation Customization Requirements?

Colin — Tue, 19 May 2009 11:25:28 GMT

We use Prince2 as a project management methodology. Prince2 has to be customised to the organisation, so we've done that by customising work items within TFS.

We completely customised the work item types (we added new items Activity, WorkPackage and Product) with custom workflows, forms and fields. We also customised the Risk workitem and some of the other out-of-the-box workitems.

We had 4 big challenges on this customisation:

1. Hierarchies. The Products are split into Workpackages and the WorkPackages into Activities. We were using linking to provide the relationship, but the hierarchies that are coming in Rosario will make this much easier.

2. Project Server integration. We are using the Project Connector from Team Rangers, but because we so heavily customised the workitems, we found this integration fragile at best. Again, we are hoping the native Project integration in Rosario will help alleviate the problems we have here.

3. Reporting. Since we customised so heavily (new work items with new workflows) some of our reports had to be worked from scratch. However, we managed to muddle through using reports that others have released (especially from bharry's blog).

4. Process documentation. We just left the Agile documentation, but it would be great to get documentation to support our Prince2 process. I think the main issue here was time and resource - we don't have anyone dedicated to documentation...

Microsoft looking for customer feedback on TFS Customization

Steve Porter — Tue, 19 May 2009 12:00:37 GMT

One of the things I love about Team System is the amount of customization that is supports, but I'll admit that it's not always the easiest beast to work with.

VSTS work item tracking, project and process customisation … a focused blog

In search of simplicity, quality and tranquility in software engineering — Wed, 20 May 2009 00:25:46 GMT

Kathryn Elliott has started a dedicated blog to collaborate on the customisation requirements for work