Visual Studio 2005 Team System: Software Project Management

1
(No Transcript)
2
Visual Studio 2005 Team System Software Project
Management
Hans Verbeeck hansver_at_microsoft.com
http//msdn.microsoft.com/teamsystem
3
Visual Studio Team System
Visual StudioTeam Architect
Visual StudioTeam Developer
Visual StudioTeam Test
Visual StudioTeam Foundation
4
A Software Project Team
Larry Sykes Product Manager
5
Following Best Practices

• What process is the team using?
• Where is the real data?
• Process manuals quickly become out-of-date
• Process alone does not bridge gaps

6
Today - Project Managers Bridge Gaps

• Copy and paste
• Status meetings
• Translating data
• Transferring work
• Chasing down loose ends

• Between People
• Between Tools

7
The Problem with Process
Predictable Repeatable
Productive
Why cant process help productivity?
8
The Rules Have Changed

• From Anticipation
• (Define, Design, Build)

• To Adaptation
• (Envision, Explore, Adapt)

???????????
9
Microsoft Solutions Framework (v4) is

• Guidance on how to organize people and projects
  to plan, build, and deploy technology solutions
  successfully and effectively
• An agile software development process
• A formal software development process
• Framework for customers and partners to implement
  custom software development process

10
Out of the box MSF processes

• MSF Agile
• Evolve and adapt
• Ideal for Competitive Environments
• Rely on People
• Plan as you go
• MSF Formal
• Plan and optimize
• Ideal for Regulated Environments
• Rely on Process
• Plan in advance

11
MSF Delivered

• Accessible/Embedded
• Exposed within Help
• Centralized
• Delivered via Team Foundation Server
• Current
• Updated from MSDN
• Customizable
• Extended by Customers and Partners

12
Methodology Templates

• Default settings for a Portfolio Project
• Consumed during project creation
• Tailored to common SDLC practices
• MSF Formal, MSF Agile (out of the box)
• Extreme Programming, RUP
• Industry Specific (financial, health care, etc.)
• ltYour customers organization heregt

13
Portfolio Project Creation
Methodology Template
Portfolio Project
Project Creation Wizard
User Input
14
Anatomy of a Methodology Template
Methodology Definition
Methodology.xml
Guidance
Reporting
External References
Work Items
Methodology.zip
Bug.xml
Task.xml
CustomWIType.xml
15
Methodology.xml

• lttask id"Currituck" assembly"Microsoft.VisualStu
  dio.ProjectCreation" class"Microsoft.VisualStudio
  . WorkItemCreator" completionDescription"Work
  items uploaded to the project site."gt
• ltdependenciesgt
• ltdependency taskId"CSS" /gt
• lt/dependenciesgt
• lttaskXmlgt
• lttask name"WorkItemType"gt
• ltworkItemTypesgt
• ltworkItemType fileName"Bug.xml"
  typeName"Bug" /gt
• ltworkItemType fileName"Task.xml"
  typeName"Task" /gt
• ltworkItemType fileName"CustomWIType.x
  ml" typeName"Custom Work Item Type"gt
• ltworkItemsgt
• ltworkItem id"1"gt
• ltfield name"title"
  value"Identify and assign team resources" /gt
• ltfield name"Priority" value"1"
  /gt
• ltfield name"State" value"Active"
  /gt
• ltfield name"Active Date"
  value"1/1/04" /gt
• ltfield name"SubState"
  value"Blocked" /gt
• ltfield name"Reason" value"New"
  /gt
• lt/workItemgt

16
Process Baked In - Key Concepts
Role
performs
permissions
Activity
Iteration
schedules
groups
reports
Query
Report
17
Demo - Team Explorer - Process Methodology -
Customization - Project Creation
18
What about all the other lists I manage?
19
Demo - Office Integration
20
Resolve Conflicts
21
Visual Studio Team System Reporting

• .

• Cross Lifecycle
• Customizable
• Extensible

22
Example of cross domain report
23
Readily Available
24
Reporting Extensibility Architecture
SQL Server Reporting Services
Reporting Warehouse
Excel
Reporting Warehouse Object Model
Custom Reporting
Test/Build Adapter
Work Item Adapter
Source Code Adapter
Add-on Adapter
Partner ToolA
Build Database
Work Item Tracking
Source Code Control
25
Demo - Project Portal - Reporting
26
Visual Studio Team System Project Management

• Productive AND Predictable Teams
• Process automates transitions between tools and
  the people
• Your team is on the same page
• You can view the data the way you want
• Using the tools you want
• While others view their data in their tools
• Status meetings become tactics meetings
• NO Where are you on that?
• NO When do you think youll be done?
• YES How can we address the road blocks in your
  way?

27
For More Information

• Visual Studio Team System Site
• http//msdn.microsoft.com/teamsystem
• Project Management Blogs
• http//weblogs.asp.net/keithrowe/
• http//lab.msdn.microsoft.com/teamsystem/community
  /blogs/
• MSF Agile Web Site
• http//lab.msdn.microsoft.com/teamsystem/workshop/
  msfagile/