Team Foundation Server Projects

Team Foundation Server Team Projects Adopting Visual Studio Team System 2008

Mickey Williams Director, Center of Excellence [email protected]

Agenda • Team Projects – Overview – Strategies

• Process Guidance Template Options – MSF – Comparing Agile and CMMI – Third parties – Customization

2

Team Project Overview

Team Projects • Server-side host for VSTS work – Server container for team collaboration – Generally contains multiple solutions

• Includes all aspects of VSTS: – SharePoint team site – Work item tracking – Team source control – Reporting – Testing – Builds

4

Team Project Strategies • Frequently asked questions: – When do I branch code? – When do I create a new team project? – When should I add iterations? – What should impact my decision?

5

Team Project Strategies • Impact points – Documents in SharePoint – Work items – Source code – Report data (build/test data) – Project staffing – Security boundaries – Release coupling

6

Team Project Strategies • Point release: V1 -> V1.1 – Favor a new iteration ›

In most cases

›

Maintains cohesion with existing project state

– All of the following remain intact and connected:

7

›

Workitems

›

SharePoint docs

›

Source code

›

Process

›

Reports

›

Team members

Team Project Strategies • Major release: V1 -> V2 – May favor a new team project ›

Major release boundary suggests major changes

– All of the following will be decoupled between team projects:

8

›

Workitems

›

SharePoint docs

›

Source code

›

Process

›

Reports

›

Team members

Team Project Strategies • Strategy for an aggregated software release – Software releases that consist of multiple sub projects – Projects may be capable of standalone operation – Some common interaction or branding (Microsoft Office)

• Options: – One large team project ›

Multiple areas

– Multiple team projects ›

9

Dependencies between projects

Team Project Strategies • One team project with multiple areas • Pros – Reports roll up all activity – Work item integration – Shared docs

– All source code is under the same folder – Project/excel integration for the whole system

• Cons – Security may be more complex – Reports and metrics have a tendency to comingle – Iterations generally must be aligned – Lack of isolation – Must use the same process for all sub-projects

10

Team Project Strategies • Multiple team projects • Pros – Security – Isolation – Process is specific to each team

– Scheduling

• Cons – Isolation – Reporting - all new reports needed for rollup – Cross-reference projects – Project/excel integration for the whole system

11

Agenda • Team Projects – Overview – Strategies

• Process Guidance Template Options – MSF – Comparing Agile and CMMI – Third parties – Customization

12

MSF as a Family of Processes MSF

MSF for Agile Software Dev

13

MSF for CMMI

Third-Party Offerings

In-House Customizations

MSF for Agile Software Development • Iterative and incremental – Scenario-driven

• Small teams – Common theme for Agile processes – Large projects utilize a team of teams approach

• Quality of Service requirements • Risk awareness and management • Utilizes a context-driven testing approach

14

MSF for CMMI® Process Improvement • CMMI® – Capability Maturity Model Integration (CMMI®) – Organized by Software Engineering Institute (SEI) – Model for continuous improvement of capability and maturity

• MSF for CMMI® – – – –

Help organizations work towards CMMI® level 3 Most of 21 process areas covered Template designed for lighter bureaucracy and documentation No guarantee for receiving of appraisal

• Elaborates on the MSF for Agile Development process – More work items – Extensive reporting

15

Agile vs. CMMI®

16

MSF Agile

MSF CMMI®

• Evolve and adapt

• Plan and optimize

• Ideal for competitive environments

• Ideal for regulated environments

• Rely on People

• Rely on process

• Plan as you go

• Plan in advance

Third-Party Process Guidance • Process guidance templates are easily customized • Two Scrum process guidance templates available: – eScrum ›

From Microsoft

›

Used internally on various projects

›

Current release challenging to install on TFS 2008

– Scrum for Team System

17

›

From Conchango

›

Third release, very polished

›

Very easy to install and use

Demo • Creating and configuring team projects

18

Questions?