Working with Microsoft Visual Studio 2005 Team System (Pro-Developer)

Appendix A

A Day in the Life of Team System

Probably the best way to learn about a new methodology and how to use a tool is to see them in practice. In this appendix, you will see a three-month walk-through demonstration using Microsoft® Visual Studio® 2005 Team System in presenting a fictitious scenario using a fictitious team. There are many scenarios for which Team System can be of assistance.

Here are a few of the more interesting scenarios, with some potential time spans:

• Design, develop, test, deploy

  A fairly straight path and typical software development life cycle (SDLC) with planned work (1–6 months)

• Maintain existing code

  Ad hoc, unplanned, operations-driven crisis work (3–5 days)

• My first day

  For a new hire or other initial practitioner experience (1 day)

• Our second project

  Administration of teamwork (1–10 days)

• Oops—someone else touched it, too

  Parallel development and configuration management (2–3 days)

• The sun never sets

  Multisite, globally distributed work (2–3 days)