26.04.2015 Views

Team Development with Visual Studio Team Foundation Server

Team Development with Visual Studio Team Foundation Server

Team Development with Visual Studio Team Foundation Server

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Foreword By Rob Caron<br />

Foreword<br />

Ever since the early days of <strong>Visual</strong> <strong>Studio</strong> <strong>Team</strong> System, we knew software development<br />

teams would need more content than we could possibly provide prior to shipping. In<br />

particular, we knew they would need proven guidance and best practices; however, that<br />

knowledge wouldn’t be known until the product was put through its paces by a variety of<br />

teams in a diverse array of environments, projects and scenarios to prove what works, and<br />

what doesn’t.<br />

Unfortunately, the identification and development of proven guidance and best practices<br />

takes time. Over the last few years, we have learned a great deal about the use of <strong>Team</strong><br />

System in general, and <strong>Team</strong> <strong>Foundation</strong> <strong>Server</strong> in particular. But that knowledge wasn’t<br />

always easy to find and digest. It would take the dedicated and methodical work of<br />

patterns & practices veteran J.D. Meier and his team months to make sense of it all.<br />

Finally, the wait is over! <strong>Team</strong> <strong>Development</strong> <strong>with</strong> <strong>Visual</strong> <strong>Studio</strong> <strong>Team</strong> <strong>Foundation</strong> <strong>Server</strong><br />

represents the collective wisdom of innumerable people who contributed directly, and<br />

indirectly, to this project. The team that assembled this content didn’t ignore the<br />

experience of those who went before them. They culled through a scattered collection of<br />

blog posts, forum threads, articles, and more to better understand how teams are adopting<br />

and using <strong>Team</strong> System “in the wild.”<br />

Along the way, they examined the key areas that impact software development teams,<br />

and identified which practices were responsible for predictable and repeatable success.<br />

Some of the most informative content explains a number of <strong>Team</strong> <strong>Foundation</strong> <strong>Server</strong><br />

feature areas, such as work item tracking, reporting, and process templates.<br />

In retrospect, I am thankful that as a documentation team we had the presence of mind to<br />

defer this work instead of trying to provide best-guess filler content. I apologize to all of<br />

those who suffered <strong>with</strong>out this content, and I thank those who persevered and pioneered<br />

the use of <strong>Team</strong> System.<br />

Rob Caron<br />

Lead Product Manager<br />

Microsoft Corporation<br />

July, 2007<br />

Rob Caron is the Lead Product Manager for Developer Content Strategy at Microsoft.<br />

Rob started at Microsoft in 1999 as a writer for <strong>Visual</strong> <strong>Studio</strong> product documentation.<br />

Over the years, he contributed content for <strong>Visual</strong> <strong>Studio</strong> .NET 2002, <strong>Visual</strong> <strong>Studio</strong> .NET<br />

2003, and <strong>Visual</strong> <strong>Studio</strong> <strong>Team</strong> System. In mid-2004, he started a blog that became the<br />

nexus for information on <strong>Team</strong> System. After seven years of creating content, Rob moved<br />

to the Developer Marketing team in the fall of 2006. He now leads a group that is focused

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!