MSF MSF (Microsoft Solutions (Microsoft Solutions

Framework)Framework)Team ModelTeam Model

Deniz KILINÇ Volkan Deniz KILINÇ Volkan ABURABUR

Problems, problems, Problems, problems, problems...problems...

“This thing isunpredictable – wekeep discoveringnew problems”

“It’s just too difficult to use”

“We couldn’t getthe informationwe needed to do our work”

“We were unawareof how the work of

other team membersaffected our work”

“The projectwas late andover budget”

“What was built really isn’t what

we needed”

“It doesn’t meetour expectations –we’re not happy” “We didn’t

understand clearlywhat we were

supposed to do”

“We can’t get it to operate well in our

environment”

2W, 1H (What, Who, How)2W, 1H (What, Who, How)

Establish good communications

Goals to Success

Deliver within project constraints

Build to specifications

Release with issues identified and addressedDeploy smoothly and prepare well for ongoing operations

Enhance user effectiveness

“The project was late and over budget”

“What was built really isn’t what we needed”“This thing is unpredictable – we keep discovering new problems”“We can’t get it to operate well in our environment”

“It’s just too difficult to use”

Problems

Satisfy customers

Owner

“It doesn’t meet our expectations – we’re not happy”

?

?

?

?

?

?

“Needed information is not shared timely to all who need it”

?

MSF Team ModelMSF Team ModelDelivering the solution within project constraints

Satisfied customers

Enhanced user effectiveness

Smooth deployment and ongoing operations

Approval for release only after all quality issues are identified and addressed

Building to specification

DevelopmentDevelopment

TestTest

Release Management

Release Management

UserExperience

UserExperience

ProductManagement

ProductManagement

Program Management

Program Management

Clear Communication

MSF Team Model MSF Team Model HierarchyHierarchy

-No hierarchy between project members

-Everyone is equal

Project sponsorsProject sponsors Customers (business sponsors)Customers (business sponsors) End usersEnd users OperationsOperations ......

External StakeholdersExternal Stakeholders

Work toward a shared visionWork toward a shared vision Focus on business valueFocus on business value Stay agile, expect changeStay agile, expect change Empower team membersEmpower team members Foster open communicationsFoster open communications Establish clear accountability, shared Establish clear accountability, shared

responsibilityresponsibility

Team Model – PrinciplesTeam Model – Principles

Team of peersTeam of peers Customer-focused mindsetCustomer-focused mindset Product mindsetProduct mindset Zero defect mindsetZero defect mindset Willingness to learnWillingness to learn

Team Model – Key ConceptsTeam Model – Key Concepts

Use small, interdisciplinary teamsUse small, interdisciplinary teams Enable teams to work together at a Enable teams to work together at a

single sitesingle site Create a soultion design through Create a soultion design through

total team participationtotal team participation

Team Model – Proven Team Model – Proven PracticesPractices

DevelopmentDevelopment

TestTest

Release Management

Release Management

UserExperience

UserExperience

ProductManagement

ProductManagement

Program Management

Program Management

Communication

Team Model – Role ClustersTeam Model – Role Clusters

Functional areas

Responsibilities

Tasks

Program management

Project management

Drive overall solutiondesign

Manage functionalspecification

Maintain traceabilitymap

Liaise with otherproject teams oninteroperabilityissues

Solution architecture

Example

Role cluster (role)

Business valueMarketingCustomer advocacyProduct planning

Project managementSolution architectureProcess assuranceAdministrative services

Test planningTest engineeringTest reporting

InfrastructureSupportOperationsLogisticsCommercial release management

AccessibilityInternationalizationUser advocacyTraining/support materialUsability research and testingUser interface design

DevelopmentDevelopment

TestTest

Release Management

Release Management

UserExperience

UserExperience

ProductManagement

ProductManagement

Program Management

Program Management

Technology consultingImplementation architecture and designApplication developmentInfrastructure development

Functional Areas of Role Functional Areas of Role ClustersClusters

Operationsand

SupportGroups

Technology Focus

Business FocusUsers

Project Sponsor

Customer

Technology Architects and Steering Committees

Help Desk

Project Team

UserExperience

Development

Test

ReleaseManagement

ProductManagement

ProgramManagement

Extended TeamExtended Team

Use factors such as complexity, size, risk, Use factors such as complexity, size, risk, and skills for scaling and skills for scaling

Divide large teams into smaller teams, Divide large teams into smaller teams, which have lower process, management, which have lower process, management, and communication overhead and allow and communication overhead and allow faster implementationfaster implementation

Designate team leads for sub-teamsDesignate team leads for sub-teams Use core team to manage overall projectUse core team to manage overall project

Core team is composed of team leads and Core team is composed of team leads and program managementprogram management

Core team coordinates and synchronizes sub-Core team coordinates and synchronizes sub-teamsteams

Ways to Scale Up TeamsWays to Scale Up Teams

DesktopFeatureTeam

ProgramManagement

ProgramManagement

UserExperience

UserExperience

DevelopmentDevelopment

TestTest

File and Print FeatureTeam

ProgramManagement

ProgramManagement

UserExperience

UserExperience

DevelopmentDevelopment

TestTest

MessagingFeatureTeam

ProgramManagement

ProgramManagement

UserExperience

UserExperience

DevelopmentDevelopment

TestTest

Lead and Feature TeamsLead and Feature Teams

Lead Team

Combining Roles for Small Combining Roles for Small TeamsTeams

N

N N

N

N

N

N

N

N

N N N

P

P

P

P

P

P

P

P

P

P

U

U

U

U

U U

U

U

P Possible U Unlikely N Not Recommended

ProductManagement

ProductManagement

ProgramManagement

ProgramManagement DevelopmentDevelopment TestTest

UserExperience

UserExperience

ReleaseManagement

ReleaseManagement

ProductManagement

ProductManagement

ProgramManagement

ProgramManagement

DevelopmentDevelopment

TestTest

UserExperience

UserExperience

ReleaseManagement

ReleaseManagement

Roles Roles maymay be combined, but some combinations be combined, but some combinations pose pose risksrisks

UserExperience

UserExperience

ProductManagement

ProductManagement

TestTest

ProgramManagement

ProgramManagement

ReleaseManagement

ReleaseManagement

DevelopmentDevelopment

Small Team ExampleSmall Team Example