Visual studio 2005 team system software project management
Download
1 / 27

Visual Studio 2005 Team System: Software Project Management - PowerPoint PPT Presentation


  • 88 Views
  • Uploaded on
  • Presentation posted in: General

Visual Studio 2005 Team System: Software Project Management. Hans Verbeeck hansver@microsoft.com. http://msdn.microsoft.com/teamsystem. Code Coverage. Code Profiler. Version Control. Work Item Tracking. Team Reporting. Project Portal. Integration Services. Project Management.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha

Download Presentation

Visual Studio 2005 Team System: Software Project Management

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Visual Studio 2005 Team System: Software Project Management

Hans Verbeeck

hansver@microsoft.com

http://msdn.microsoft.com/teamsystem


Code Coverage

Code Profiler

Version Control

Work Item Tracking

Team Reporting

Project Portal

Integration Services

Project Management

Static Code Analyzer

Class Designer

Unit Testing

Dynamic Code Analyzer

Visio and UML Modeling

Deployment Designer

Team Build

Application Designer

Test Case Management

Logical Datacenter Designer

Load/Web Testing

Visual Studio Professional Edition

Team Foundation Client (includes CAL)

Manual Testing

Process and Architecture Guidance

Visual Studio Industry Partners

Visual Studio Team System

Visual StudioTeam Architect

Visual StudioTeam Developer

Visual StudioTeam Test

Visual StudioTeam Foundation


Jacqui AckermanProject Manager

Art BensonArchitect

Mort GainesDeveloper

Renee DavisTester

A Software Project Team

Larry Sykes Product Manager


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


Copy and paste

Status meetings

Translating data

Transferring work

Chasing down loose ends

Jacqui AckermanProject Manager

Today - Project Managers Bridge Gaps

  • Between People

  • Between Tools


The Problem with Process

Predictable

Repeatable

Productive

Why can’t process help productivity?


From Anticipation

(Define, Design, Build)

The Rules Have Changed

  • To Adaptation

    (Envision, Explore, Adapt)

???????????


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


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

Out of the box MSF processes


MSF Delivered

  • Accessible/Embedded

    • Exposed within Help

  • Centralized

    • Delivered via Team Foundation Server

  • Current

    • Updated from MSDN

  • Customizable

    • Extended by Customers and Partners


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.)

    • <Your customer’s organization here>


Portfolio Project Creation

Methodology Template

Portfolio Project

Project Creation Wizard

User Input


Anatomy of a Methodology Template

Methodology Definition

Methodology.xml

Guidance

Reporting

External References

Work Items

Methodology.zip

Bug.xml

Task.xml

CustomWIType.xml


Methodology.xml

<task id="Currituck" assembly="Microsoft.VisualStudio.ProjectCreation" class="Microsoft.VisualStudio. WorkItemCreator" completionDescription="Work items uploaded to the project site.">

<dependencies>

<dependency taskId="CSS" />

</dependencies>

<taskXml>

<task name="WorkItemType">

<workItemTypes>

<workItemType fileName="Bug.xml" typeName="Bug" />

<workItemType fileName="Task.xml" typeName="Task" />

<workItemType fileName="CustomWIType.xml" typeName="Custom Work Item Type">

<workItems>

<workItem id="1">

<field name="title" value="Identify and assign team resources" />

<field name="Priority" value="1" />

<field name="State" value="Active" />

<field name="Active Date" value="1/1/04" />

<field name="SubState" value="Blocked" />

<field name="Reason" value="New" />

</workItem>


Work Stream

Work Product

produces & consumes

sequences

Security Group

belongs to

tracks

User

Work Item

owns

Key:

Process Guidance Prescribes

VSTS Enacts

Process “Baked In” - Key Concepts

Role

performs

permissions

Activity

Iteration

schedules

groups

reports

Query

Report


Demo:- Team Explorer- Process Methodology- Customization- Project Creation


Change

Requests

Customer

Requests

Requirements

?

Bugs

Issues List

What about all the other lists I manage?


Demo:- Office Integration


Resolve Conflicts


Cross Lifecycle

Customizable

Extensible

.

Visual Studio Team System Reporting


Example of cross domain report


Readily Available


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


Demo:- Project Portal- Reporting


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 you’ll be done?

    • YES: How can we address the road blocks in your way?


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/


ad
  • Login