Managing Projects with Microsoft Visual Studio 2005 Team System

Chapter 1: Managing Software Engineering Projects

Figure 1-1: Visual Studio Team System

Figure 1-2: MSF Remaining Work report

Figure 1-3: MSF Quality Indicators report

Chapter 2: Project Management Features of Visual Studio Team System

Figure 2-1: The Task work item

Figure 2-2: The Requirement work item type specifies four states.

Figure 2-3: Visual Studio Team System reporting is extensible, allowing you to create your own reports or even access the data warehouse directly from Microsoft Excel.

Figure 2-4: The project portal

Figure 2-5: Designers in Visual Studio Team Edition for Software Architects

Figure 2-6: Code Analysis settings in Visual Studio Team Edition for Software Developers

Figure 2-7: The role of a project manager encompasses many areas and is key to project success.

Figure 2-8: Process templates specify virtually every aspect of a Team Project.

Figure 2-9: Project managers can set specific permissions to restrict the team to performing certain activities with Visual Studio Team System.

Figure 2-10: The Remaining Work report

Figure 2-11: The MSF Risk Management model

Figure 2-12: The workflow of a Risk work item specified within the MSF for CMMI Process Improvement process template

Chapter 3: Project Initiation

Figure 3-1: MSF Envisioning track workstreams

Figure 3-2: Many more team roles are specified in MSF for CMMI.

Figure 3-3: Team Explorer in Visual Studio

Figure 3-4: Work item history

Figure 3-5: Creating links in a work item

Figure 3-6: Microsoft Office Excel integration

Figure 3-7: Hierarchical project classifications

Figure 3-8: The results of iteration length planning

Figure 3-9: A typical area breakdown for a Team Project

Figure 3-10: Area breakdown when managing two products under one Team Project

Chapter 4: Planning a Project

Figure 4-1: A work breakdown structure based on the Unified Process that specifies workflows, phases, and deliverables

Figure 4-2: Planning in MSF Agile

Figure 4-3: A conflict error

Figure 4-4: Using Office Excel pivot tables to review project estimates

Figure 4-5: A more complex area hierarchy used to classify work items

Figure 4-6: Example iteration breakdown

Figure 4-7: An initial release plan in Office Project

Figure 4-8: A project plan showing iterations, requirements, and tasks

Figure 4-9: Pivot table for viewing workload by team member for each iteration

Chapter 5: Monitoring and Controlling Project Execution

Figure 5-1: Home page for a Team Project based on MSF for Agile Software Development

Figure 5-2: MSF process guidance for the Build track

Figure 5-3: Results of the All Tasks work item query

Figure 5-4: Results of a work item query in Office Excel

Figure 5-5: Adding a Work Items check-in policy to a Team Project

Figure 5-6: Selecting a report in Team Explorer

Figure 5-7: SQL Server Reporting Services Web site for a Team Project

Figure 5-8: Unplanned Work report

Figure 5-9: Related Work Items report

Chapter 6: Improving Your Process

Figure 6-1: The LPI Framework life cycle

Chapter 7: Tailoring Visual Studio Team System

Figure 7-1: Opportunities for Visual Studio Team System customization

Figure 7-2: Custom work item type

Figure 7-3: Example of area classification customization

Figure 7-4: The Work Item Query Save Query As dialog box

Figure 7-5: Grouping clauses in a work item query

Figure 7-6: Example of a custom work item query

Figure 7-7: Changing the column options for a work item query definition

Figure 7-8: Process template directory structure

Figure 7-9: ProcessTemplate.xml points to XML files in plugin directories.

Figure 7-10: ProcessTemplate.xml points to other XML files for each Visual Studio Team System plugin.

Figure 7-11: Specifying a computer running Team Foundation Server by using the Process Template Editor

Figure 7-12: The Process Template Editor main window

Figure 7-13: Adding a new Risk work item to a process template

Figure 7-14: Managing work item queries by using the Process Template Editor

Figure 7-15: The query editor in the Process Template Editor

Figure 7-16: Creating a new work item from the definition of another

Figure 7-17: Editing field definitions within a work item type definition

Figure 7-18: Work item field rules

Figure 7-19: Editing workflow within a work item type definition

Figure 7-20: Selecting a field when adding a rule

Figure 7-21: Adding a workflow transition to a work item

Figure 7-22: Editing a work item’s layout

Figure 7-23: Selecting a work item to export

Figure 7-24: Managing Global lists with the Process Template Editor

Figure 7-25: Managing default classifications by using the Process Template Editor

Figure 7-26: Configuring default source control settings in the Process Template Editor

Figure 7-27: Editing default document libraries and documents

Figure 7-28: A Team Project’s process guidance

Appendix A: Capability Maturity Model Integration (CMMI)

Figure A-1: CMMI is truly an evolutionary offspring of many other models and provides a platform for future extensibility.

Figure A-2: CMMI representations

Figure A-3: Structure of a process area definition

Figure A-4: Structure of a process area definition

Figure A-5: Staged maturity model

Figure A-6: Continual capability model

Figure A-7: Benefit comparison between Staged versus Continuous representation

Appendix B: Microsoft Solutions Framework

Figure B-1: MSF components

Figure B-2: MSF tracks

Figure B-3: MSF Team Model

Figure B-4: Responsibility Matrix: MSF for Agile Software Development (Entire chart available at http://blog.arrowrock.com/sourceart/2006/02/07/MSFAnalysisTool.aspx)