Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

32
Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft [email protected] http://blogs.msdn.com/ brianwh/

description

Visual Studio Team System Change ManagementWork Item Tracking ReportingProject Portal Site Visual Studio Team Foundation Integration Services Project Management Process and Architecture Guidance Dynamic Code Analyzer Visual Studio Team Architect Static Code AnalyzerCode ProfilerUnit TestingCode CoverageVisio and UML ModelingTeam Foundation Client (includes CAL)Visual Studio Professional EditionLoad TestingManual TestingTest Case ManagementApplication DesignerLogical Infra. DesignerDeployment Designer Visual Studio Team Developer Visual Studio Team Test Visual Studio Industry Partners Team BuildClass Designer

Transcript of Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Page 1: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Visual Studio 2005 Team System:

Software Project Management

Brian A WhiteMicrosoft

[email protected]://blogs.msdn.com/brianwh/

Page 2: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Expanding Visual Studio

IncreasedIncreasedReliabilityReliability

QualityQualityEarly & OftenEarly & Often

PredictabilityPredictability& Visibility& Visibility

Design forDesign forOperationsOperations

ProjectProjectManagerManager

SolutionSolutionArchitectArchitect

DeveloperDeveloperTesterTester

InfrastructureInfrastructureArchitectArchitect

Page 3: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Visual Studio Team System

Change Management

Work Item Tracking

Reporting

Project Portal Site

Visual StudioTeam Foundation Integration Services

Project Management

Proc

ess

and

Arch

itect

ure

Proc

ess

and

Arch

itect

ure

Guid

ance

Guid

ance

Dynamic Code Analyzer

Visual StudioTeam Architect

Static Code Analyzer

Code Profiler

Unit Testing

Code Coverage

Visio and UML Modeling

Team Foundation Client (includes CAL)

Visual Studio Professional Edition

Load Testing

Manual Testing

Test Case Management

Application Designer

Logical Infra. Designer

Deployment Designer

Visual StudioTeam Developer

Visual StudioTeam Test

Visu

al S

tudi

o In

dust

ry

Visu

al S

tudi

o In

dust

ry

Partn

ers

Partn

ers

Team Build

Class Designer

Page 4: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

A Software Project Team

Jacqui AckermanProject Manager

Art BensonArchitect

Mort GainesDeveloper

Renee Davis Tester

Larry Sykes Product Manager

Page 5: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Project Success is Rare

Average cost overrun: 45%Time overrun: 63%Functionality delivered on average: 67%

Standish Group

2000 28%23% 49%

SucceededChallengedFailed

Source: The Standish Group International, Extreme Chaos, The Standish Group International, Inc., 2000

Page 6: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Project Success Factors Executive Support 18User Involvement 16Experienced Project Manager 14Clear Business Objectives 12Minimized Scope 10Standard Software Infrastructure 8Firm Basic Requirements 6Formal Methodology 6Reliable Estimates 5Other 5

Source: The Standish Group International, The Standish Report, 2001

Page 7: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

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

Page 8: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

MSF Agile vs. MSF FormalMSF 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

Page 9: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Demo: MSF Agile

Page 10: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

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

Page 11: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Today - Project Managers Bridge Gaps

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

endsJacqui AckermanProject Manager

•Between People•Between Tools

Page 12: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

The Problem with ProcessPredictablePredictableRepeatableRepeatableProductiveProductive

Why can’t process Why can’t process helphelp productivity? productivity?

Page 13: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Improved Team Productivity with “Baked In” Process• What are people working on?• How does it all relate?

• Workflow followed automatically• Critical metrics captured• Up to date, public information • Nothing gets in the way • Tools for the job• Tools remember for me• Process steps close at hand

Page 14: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Anatomy of a Project

Project PlanProject Plan-Iterations-Dependencies-Schedule

ProcessGuidance- Process Help- Templates

Team Project&

Project Site

Page 15: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Demo: Visual Studio Team System andMS Project

Page 16: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft
Page 17: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

BugsBugs

RequirementsRequirements

Issues ListIssues List

ChangeChangeRequestsRequests

CustomerCustomerRequestsRequests

What about all the other lists I manage?

Page 18: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Anatomy of a Project

Project Plan-Iterations-Dependencies-Schedule

Work ItemsWork Items-Requirements-Bugs-Tasks

ProcessGuidance- Process Help- Templates

Team Project&

Project Site

Page 19: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Demo: VSTS and MS Excel

Page 20: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Resolve ConflictsWork Item Publishing ErrorsWork Item Publishing Errors ?

Cancel

16 of 20 work items have published successfully. Review and resolve the following issues to publish the remaining work items.

Publish

ID

357

407

437

507

Title

Setup: Set Permissions

InitializeDeBugger all times

Resize doesn’t work

User interface additions

StatusNot published

Not published

Not published

Not published

Assigned to

Priority

Conflicting fields

Details

Issue

Conflict

Validation error

Access denied

Server connection failed

jensj

2

monetaho

4

View Server Version

Local version Server version (10/04/2004 1:23 PM by monetaho)

Page 21: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Anatomy of a Project

Project Plan-Iterations-Dependencies-Schedule

Work Items-Requirements-Bugs-Tasks

ProcessGuidance- Process Help- Templates

Team Project&

Project Site

ReportingReporting-Available-Extensible

Page 22: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Visual Studio Team System Reporting• Cross Lifecycle• Customizable• Extensible

• .Work Items

(Requirements,Tasks, Bugs,

Features)

Source Code

Builds

Tests

Project Reports

Team Project

Page 23: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Example of cross domain report

Page 24: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Readily Available

Page 25: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Anatomy of a Project

Project PlanProject Plan-Iterations-Dependencies-Schedule

Work ItemsWork Items-Requirements-Bugs-Tasks

ProcessProcessGuidanceGuidance- Process Help- Templates

ReportingReporting-Available-Extensible

Team Project&

Project Site

Page 26: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Process Templates and Template Manager

• VS Menu: Team Foundation Server > Administration

Page 27: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Visual Studio Team System Project ManagementProductive 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 you’ll be done?● YES: How can we address the road blocks in your

way?

Page 28: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

For More Information…• Visual Studio Team System Site

● http://msdn.microsoft.com/vstudio/teamsystem

• Project Management Newsgroupshttp://communities.microsoft.com/newsgroups/project manager

• Project Management Blogs● http://weblogs.asp.net/keithrowe/

• MSF Agile Web Site● http://workspaces.gotdotnet.com/msfv4

Page 29: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Backup

Page 30: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Process “Baked In” - Key Concepts

Activity

Query

Report

Iteration

Role performs

Process Guidance Prescribes

VSTS Enacts

Key:

Work Productproduces & consumes

User owns Work Item

tracks

Work Stream

sequences

Security Group

belongs to

permissions

schedulesgroupsreports

Page 31: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Advanced Compare / Merge Architecture

WorkItems

1.1. Identify Identify User1 UpdatesUser1 Updates

2. Compare 2. Compare User1 User1 Updates Updates with Serverwith Server

User1Baseline1

User2Baseline1

Baseline1User2 Updates

Page 32: Visual Studio 2005 Team System: Software Project Management Brian A White Microsoft

Work ItemWork ItemTrackingTracking

Reporting Extensibility Architecture 0

50100150200250300350400450

0%10%20%30%40%50%60%70%80%90%

De fects Op enTe st Cases RunD efects/TC

Defect Trends

Weekly Executive Summary

MyHICPortal - Microsoft Internet Explorer

http: //humongous/myprojectportal/default.aspx

Home Project Counsel Discussions Documents Policy

Project PortalHome

Modify My Page

Home

Create New ProjectDocuments

Create a new report

Standard ReportsReports

Workflow

Project Schedule

Roles Manager

Project Portal web site provides role-based views of the development project. In addition to providing usefulinformation directly (such as the plan of record, defect trends, and other reports), it also serves as a launchingpoint for various other tools.

Links Project Management ConsoleDefect Tracking ToolMSWord Requirements TemplateHumongous Project Guidelines

Add New Link

Projects Status

Contacts

J acqueline Ackerman - Project ManagerEndicott Smith - VP Sales, Project SponsorAnna Jones - Business AnalystBert Lewis - Development ManagerBarbara Baker - Test Manager

Add New Link

EnvisioningPlanning

FX Hander

FX TickerTransfer ASP

Specs Defects I ssues Risks Due Date Signoff4 / 4 1 /12 / 2 6/5/03 Yes

7/15/03 No

7/25/03 No

8/1/03 No

0

Developing 9/1/03 No

Stabi lizing No

Deploying No

10/1/03

11/1/03

Recently updated Documents

NameVision DocumentBusiness RequirementsMyHIC Functional RequirementsCustomer Interviews

Modified ByFionaBettyPaulaBetty

Type

Add New Document

PortalSearch -- select from list --I need to...

Qu

ick

La

un

ch

Project X

Standard Forms

Vision DocumentBusiness Requirements

Feature SpecificationsStatus Reporting

Create a new Form

Functional Requirements

Public Reports

Status ReportsPresentationsRequirements

4 of 12 7 of 83 of 3

21 o f 55

9 of 92 of 4

5 of 7

1 of 10

9 of 10

8 of 9 8 of 1017 of 20

0 of 0 0 of 00 of 06 of 7

2 of 2

3 of 3

3 of 4

1 of 9

6 of 7

3 of 3

12 o f 15

8 of 8

Projects Overview

Over the past few weeks , teams have done ex traordinary work gett ing bugs resolved, triaging hard, andconsistently gett ing closer and c loser to meeting our milestone exit criteria. Ask mode has helped in keeping thebui lds work ing, and we're ready to start group checkins, after the mass i ntegration last week (Lab21, Lab22 andLab25 RI'ed in one day!). However , this is about a week and a half behind the original schedule.

Given our active bug count and incoming rates, i t's become apparent that we are not ready to start our final testpass today (6/16). Therefore, our new M2 exit path is as follows:

M2 Fork: TBD (see below) Final test pass start: 6/30 (see below) Sign off: 7/11

TeamAliasMembersCommunications

SubscriptionStatus reports

SQL ServerSQL ServerReportingReportingServicesServices

Source CodeSource CodeControlControl

Work Item Work Item AdapterAdapter

Source CodeSource CodeAdapterAdapter

Partner ToolPartner ToolAA

Add-onAdd-onAdapterAdapter

Reporting WarehouseReporting Warehouse

Reporting WarehouseReporting WarehouseObject ModelObject Model

ExcelExcel

CustomCustomReportingReporting

BuildBuildDatabaseDatabase

Test/BuildTest/BuildAdapterAdapter