TFS/VSTS - 101 Pocket Guide ... Value-Add or Waste?
I have, for some time, tried to understand why …
- The adoption of Visual Studio Team System (VSTS) and Team Foundation Server (TFS) has been slow with many of the development teams/companies who would/should benefit immensely from the technologies.
- Many adoptions are of short duration or end with problematic implementations adding little value to the solution stakeholders.
Talking to the communities, customers and leads it has become apparent that in our environment (South-Africa)":
- Most teams are either unaware of the TFS/VSTS capabilities.
- Most teams are ill-equipped to investigate, implement and adopt the technologies in parallel to their already tight development milestones.
- Most teams do not have the time or luxury to investigate technologies before they are shipped, often using products such as Visual Studio 2008 as a hammer, working no different to a Visual Studio 2003 or Visual Studio 2005 based environment.
- [01/06] Most technologies ship well advance of technical books and official training material.
Through other polls and workshops we have established that the following material is preferred by the developers and technical leads in terms of products such as VSTS and TFS (listed in terms of preference from best to least):
- Practical step-by-step guidance
- Inside TFS|VSTS resource kit
- Self-paced TFS|VSTS training material
- Official TFS|VSTS Courseware
Still operating as a MVP, I am trying to compile a proposal to Microsoft to convince them of the value of creating a set of related “101” guidance documents before or as part of the VS2010 release, ensuring that teams can understand existing and new features, with the objective of rapidly and correctly adopting the new release and all its features over time.
Without documenting the envisaged content and proposed schedule at this stage, I would appreciate your one click vote at http://zohopolls.com/wschaub/tfs-vsts-101-pocket-guide-value-add-or-waste, which should be an indication whether we are smoking something weird or are on the right track.
Obviously the guidance papers, once matured, could be consolidated as a TFS|VSTS guidance pocket guide … but that is beyond the scope of this blog post.
Please cast your vote at http://zohopolls.com/wschaub/tfs-vsts-101-pocket-guide-value-add-or-waste and feel free to add additional comments to this post.