Module 1:Module 1:Introduction to MSFIntroduction to MSF

Module 3

MSF OverviewMSF Overview

Module 10: Course SummaryModule 10: Course SummaryModule 5: The Planning PhaseModule 5: The Planning Phase

Module 9: MSF DisciplinesModule 9: MSF DisciplinesModule 4: The Envisioning PhaseModule 4: The Envisioning Phase

Module 8: The Deploying PhaseModule 8: The Deploying PhaseModule 3: The MSF Process Model Module 3: The MSF Process Model

Module 7: The Stabilizing PhaseModule 7: The Stabilizing PhaseModule 2: The MSF Team ModelModule 2: The MSF Team Model

Module 6: The Developing PhaseModule 6: The Developing PhaseModule 1: Introduction to MSFModule 1: Introduction to MSF

Module 3

Frozen in the Past

Climbing Out

Avoiding the Abyss

In the Abyss

Falling In

Competitive

LeadingMoving Ahead

The IT LandscapeThe IT Landscape

Organizations are at different points on the IT landscape

Module 3

Past Simple but

monolithic  Slow-changing Tactical focus Cost-driven

Potential Simple Fast-changing Strategic focus Value-driven

IT Abyss Excessive complexity Ineffective delivery Rising costs

The IT AbyssThe IT Abyss

Module 3

Standish Group SurveyStandish Group Survey

• From the September 1998 issue of PM Network• Based on more than 23,000 projects• Challenged means completed over budget or past

the original deadline

Challenged

Succeeded

Failed 28%28%46%46%

26%26%

Module 3

“When projects fail, it’s rarely technical.”

Jim Johnson, The Standish Group

Root Causes of FailureRoot Causes of Failure

ÂSeparation of goal and functionÂSeparation of business and

technologyÂLack of common language

and processÂFailure to communicate and

act as a teamÂProcesses that are inflexible

to change

Module 3

Framework: Supplementing MethodologiesFramework: Supplementing Methodologies

1st Avenue Plum

Str

eet

Ora

nge

Stre

et

. .Smith River

2nd Avenue

3rd Avenue

4th Avenue

.. ...

S

MSF

. EW

. .N. .. .A methodologyapplies specific directions to a known destinationA framework, like a compass, verifies progress and provides directional guidance

A framework is a methodology partner!

Module 3

Origins of MSFOrigins of MSF

Microsoft Worldwide Products Groups

MicrosoftInformationTechnology

MicrosoftServices

Microsoft Partners

Best Practices

25 years of Microsoft experience

MSF evolution:7+ years

Module 3

One IT Lifecycle One IT Lifecycle –– Multiple PerspectivesMultiple Perspectives

MicrosoftSolutions

Framework

CommonDisciplines

&Shared

Responsibility

MicrosoftOperationsFramework

Module 3

MSF Models and DisciplinesMSF Models and Disciplines

Risk Management Discipline—Increasing the potential for success

Project Management Discipline—Managing and meeting commitments

Readiness Management Discipline—The right skills at the right time

Risk Management Discipline—Increasing the potential for success

Project Management Discipline—Managing and meeting commitments

Readiness Management Discipline—The right skills at the right time

Module 2:Module 2:The MSF Team ModelThe MSF Team Model

Module 3

MSF OverviewMSF Overview

Module 10: Course SummaryModule 10: Course SummaryModule 5: The Planning PhaseModule 5: The Planning Phase

Module 9: MSF DisciplinesModule 9: MSF DisciplinesModule 4: The Envisioning PhaseModule 4: The Envisioning Phase

Module 8: The Deploying PhaseModule 8: The Deploying PhaseModule 3: The MSF Process Model Module 3: The MSF Process Model

Module 7: The Stabilizing PhaseModule 7: The Stabilizing PhaseModule 2: The MSF Team ModelModule 2: The MSF Team Model

Module 6: The Developing PhaseModule 6: The Developing PhaseModule 1: Introduction to MSFModule 1: Introduction to MSF

Module 3

Team Goals for SuccessTeam Goals for Success

ÂSatisfied customersÂDelivery within project constraintsÂDelivery to specifications that are

based on user requirementsÂRelease after addressing all known issuesÂEnhanced user performanceÂSmooth deployment and ongoing management

Module 3

Team of PeersTeam of Peers

 Is a team whose members relate as equalsÂHas specific roles and responsibilities for

each memberÂEmpowers individuals in their rolesÂHolds members accountable for the success

of their rolesÂDrives consensus-based decision-making ÂGives all team members a stake in the

success of the project

Module 3

ProgramManagement

ProgramManagement

DevelopmentDevelopment

TestingTesting

ReleaseManagement

ReleaseManagement

UserExperience

UserExperience

ProductManagement

ProductManagement

MSF Team Model and Role ClustersMSF Team Model and Role Clusters

Communication

Module 3

Not a Traditional Organizational ChartNot a Traditional Organizational Chart

Testing

Developer

ProjectManager

ReleaseMgt.

Developer

AnalystUser Education

Module 3

Product Management Role ClusterProduct Management Role Cluster

ÂActs as customer advocate to the teamÂActs as team advocate to the customerÂDrives shared project visionÂManages customer expectationsÂDevelops, maintains, and executes the

business caseÂDrives feature identification and prioritizationÂDevelops, maintains, and executes the

communications plan

ProductManagement

ProductManagement

Module 3

Program Management RoleProgram Management Role

ÂDrives the overall processÂManages resource allocationÂManages the project schedule and reports

project statusÂManages the product scope and specificationÂFacilitates team communication and

negotiationÂDrives overall critical trade-off decisions

ProgramManagement

ProgramManagement

Module 3

Development RoleDevelopment Role

ÂBuilds and tests features to meet the specification and customer expectationsÂParticipates in designÂEstimates time and effort to complete each featureÂServes the team as a technology consultant

DevelopmentDevelopment

Module 3

TestingTestingTesting RoleTesting Role

ÂDevelops testing strategy, plans, and scriptsÂManages the build processÂConducts tests to accurately determine the status

of product developmentÂParticipates in setting the quality bar

Module 3

User Experience RoleUser Experience Role

ÂActs as team advocate to the end userÂActs as end-user advocate to the teamÂParticipates in defining user requirementsÂParticipates in designing featuresÂDesigns and develops user support systemsÂDrives the usability process

UserExperience

UserExperience

Module 3

ReleaseManagement

ReleaseManagement

Release Management RoleRelease Management Role

ÂActs as team advocate to operations ÂActs as operations advocate to the teamÂPlans and manages product deploymentÂParticipates in design, focusing on manageability,

supportability, and deployabilityÂSupports the product during beta testingÂTrains operations and help desk personnel for

product release

Module 3

Scaling for Small ProjectsScaling for Small Projects

ProgramManagement

ProgramManagement DevelopmentDevelopment TestingTesting Release

ManagementRelease

ManagementUser

ExperienceUser

ExperienceProduct

ManagementProduct

Management

ProgramManagement

ProgramManagement

DevelopmentDevelopment

TestingTesting

ReleaseManagement

ReleaseManagement

UserExperience

UserExperience

ProductManagement

ProductManagement

NoNPossibleP UnlikelyU

PP

PPP

P P

P PP

UU

UUU

UU

UNN

N

N NN

NNN

N N N

Module 3

Example: Feature Teams Example: Feature Teams

DevelopmentDevelopment

TestingTestingUserExperience

UserExperience

ProgramManagement

ProgramManagement

DevelopmentDevelopment

TestingTestingUserExperience

UserExperience

ProgramManagement

ProgramManagement

DevelopmentDevelopment

TestingTestingUserExperience

UserExperience

ProgramManagement

ProgramManagement

ProgramManagement

ProgramManagement

DevelopmentDevelopment

TestingTesting

ReleaseManagement

ReleaseManagement

UserExperience

UserExperience

ProductManagement

ProductManagement Lead

Team

UITeam

PrintingTeam

CoreTeam

Module 3

Example: Function TeamExample: Function Team

Group ProductManagement

Evangelism

PublicRelations

Marketing

Product Planning

ProductManagement

ProductManagement

Module 3:Module 3:The MSF Process ModelThe MSF Process Model

Module 3

MSF OverviewMSF Overview

Module 10: Course SummaryModule 10: Course SummaryModule 5: The Planning PhaseModule 5: The Planning Phase

Module 9: MSF DisciplinesModule 9: MSF DisciplinesModule 4: The Envisioning PhaseModule 4: The Envisioning Phase

Module 8: The Deploying PhaseModule 8: The Deploying PhaseModule 3: The MSF Process Model Module 3: The MSF Process Model

Module 7: The Stabilizing PhaseModule 7: The Stabilizing PhaseModule 2: The MSF Team ModelModule 2: The MSF Team Model

Module 6: The Developing PhaseModule 6: The Developing PhaseModule 1: Introduction to MSFModule 1: Introduction to MSF

Module 3

Two Common Process Models Two Common Process Models

ÂProcess models establish the order for activities within a project lifecycleÂTwo process models are popularÉThe waterfall modelÉThe spiral (or rapid application development) model

Module 3

The MSF Process ModelThe MSF Process Model

ÂThe MSF Process Model combines the benefits of waterfall and spiral modelsÉMilestone-based process ÉFlexible and iterative process

Module 3

The MSF Process Model The MSF Process Model

Module 4:Module 4:The Envisioning PhaseThe Envisioning Phase

Vision/Scope Approved MilestoneVision/Scope Approved Milestone

Module 3

MSF MSF OverviewOverview

Module 10: Course SummaryModule 10: Course SummaryModule 5: The Planning PhaseModule 5: The Planning Phase

Module 9: MSF DisciplinesModule 9: MSF DisciplinesModule 4: The Envisioning PhaseModule 4: The Envisioning Phase

Module 8: The Deploying PhaseModule 8: The Deploying PhaseModule 3: The MSF Process ModelModule 3: The MSF Process Model

Module 7: The Stabilizing PhaseModule 7: The Stabilizing PhaseModule 2: The MSF Team ModelModule 2: The MSF Team Model

Module 6: The Developing PhaseModule 6: The Developing PhaseModule 1: Introduction to MSFModule 1: Introduction to MSF

Module 3

Vision/Scope ComponentsVision/Scope Components

 Why you want to do project? => Problem Statement  What you want the solution to be? => Vision Statement  What you will do to build it? => Solution Concept Who will use the solution? => User Profile What you want to accomplish? => Business Goals  How you plan to accomplish it? => Design Goals

Module 3

Project Scope

Define ScopeDefine Scope

 Solution Scope: The full set of features and deliverables included in the solution

 Project Scope: The work performed by the team to deliver each item in the solution scope

Solution Scope

Project Scope

Solution Scope

Project Scope

Module 3

Manage Project TradeManage Project Trade--OffsOffs

Reso

urce

s

Reso

urce

s

Reso

urce

s

FeaturesFeaturesFeaturesSchedule

Schedule

Schedule

Module 3

Project TradeProject Trade--off Matrixoff Matrix

ChosenChosenFixedFixed AdjustableAdjustable

ScheduleSchedule

FeaturesFeatures

ResourcesResources

Reso

urce

s

Reso

urce

s

Reso

urce

s

FeaturesFeaturesFeatures

Schedule

Schedule

Schedule

Module 5:Module 5:The Planning PhaseThe Planning PhaseProject Plan Approved MilestoneProject Plan Approved Milestone

Module 3

MSF OverviewMSF Overview

Module 10: Course SummaryModule 10: Course SummaryModule 5: The Planning PhaseModule 5: The Planning Phase

Module 9: MSF DisciplinesModule 9: MSF DisciplinesModule 4: The Envisioning PhaseModule 4: The Envisioning Phase

Module 8: The Deploying PhaseModule 8: The Deploying PhaseModule 3: The MSF Process ModelModule 3: The MSF Process Model

Module 7: The Stabilizing PhaseModule 7: The Stabilizing PhaseModule 2: The MSF Team ModelModule 2: The MSF Team Model

Module 6: The Developing PhaseModule 6: The Developing PhaseModule 1: Introduction to MSFModule 1: Introduction to MSF

Module 3

What Could Have Been Sufficient

What Could Have Been Sufficient

Result of the Design

Result of the Design

What the User Described

and the Analyst Understood

What the User Described

and the Analyst Understood

Result of Implementation

Result of Implementation

Planning the SolutionPlanning the Solution

What the User Needed

What the User Needed

Module 3

Suggested Interim MilestonesSuggested Interim Milestones

Module 6:Module 6:The Developing PhaseThe Developing Phase

Scope Complete MilestoneScope Complete Milestone

Module 3

MSF OverviewMSF Overview

Module 10: Course SummaryModule 10: Course SummaryModule 5: The Planning PhaseModule 5: The Planning Phase

Module 9: MSF DisciplinesModule 9: MSF DisciplinesModule 4: The Envisioning PhaseModule 4: The Envisioning Phase

Module 8: The Deploying PhaseModule 8: The Deploying PhaseModule 3: The MSF Process ModelModule 3: The MSF Process Model

Module 7: The Stabilizing PhaseModule 7: The Stabilizing PhaseModule 2: The MSF Team ModelModule 2: The MSF Team Model

Module 6: The Developing PhaseModule 6: The Developing PhaseModule 1: Introduction to MSFModule 1: Introduction to MSF

Module 3

Creating Living DocumentsCreating Living Documents

ÂWhat it meansÉBaselining documents as early

as possibleÉFreezing documents as late as

possibleÂWhy it is importantÉAvoids “analysis paralysis”ÉEstablishes a structured change

control process

Module 3

Suggested Interim MilestonesSuggested Interim Milestones

Module 3

Internal ReleasesInternal Releases

Getting the product to a known state and incrementally building upon it

Internal Release 1

Internal Release 2

6 to 8 weeks

Feature Development

2 to 4 weeks 2 to 3 weeks

Testing andStabilizing

Buffer Time

AcceptanceTesting

MilestoneReview

Module 3

ZeroZero--Defect MindsetDefect Mindset

Committing to the highest possible level of quality within project constraints

ÂTeam members must understand the required quality level for their workÂWork is not complete until it reaches that level

of qualityÂThe zero-defect mindset is embodied inÉTask deliverablesÉMilestones

Module 3

Daily BuildDaily Build

Building the product in an shippable form on a daily basis

A public daily build isÉA strong indicator that a team is functionalÉA way to make the product and its progress visibleÉThe heartbeat of the development process

Module 7:Module 7:The Stabilizing PhaseThe Stabilizing Phase

Release MilestoneRelease Milestone

Module 3

MSF OverviewMSF Overview

Module 10: Course SummaryModule 10: Course SummaryModule 5: The Planning PhaseModule 5: The Planning Phase

Module 9: MSF DisciplinesModule 9: MSF DisciplinesModule 4: The Envisioning PhaseModule 4: The Envisioning Phase

Module 8: The Deploying PhaseModule 8: The Deploying PhaseModule 3: The MSF Process ModelModule 3: The MSF Process Model

Module 7: The Stabilizing PhaseModule 7: The Stabilizing PhaseModule 2: The MSF Team ModelModule 2: The MSF Team Model

Module 6: The Developing PhaseModule 6: The Developing PhaseModule 1: Introduction to MSFModule 1: Introduction to MSF

Module 3

Suggested Interim MilestonesSuggested Interim Milestones

Module 3

Bug ConvergenceBug Convergence

Marking the point at which the rate of bugs fixed exceeds the rate of bugs found

 Indicates that the solution is becoming stableÂMay be difficult to recognize due to variations in bug

countsÂDefines a trend rather than a specific date

Module 3

ZeroZero--Bug ReleaseBug Release

Reaching the first release to testing after all active bugs have been resolved

ÂRequires a heightened bug-triaging processÂClearly marks the beginning of the endgame Is the moment when development catches up to

testing Is the process of reaching zero bugs and then

working to stay there

Module 3

EndgameEndgame

Driving the product to a releasable state

ÂRepresents the closing moves for the projectÂBegins with the effort to reach the zero-bug

releaseÂForces bug management into a much more

focused triaging process Is the point in the project where shipping takes

precedence over everything else

Module 3

FixedFixed--Ship Date MindsetShip Date Mindset

Focus on Shipping

BetaBug Convergence

Zero-Bug Release

Release CandidateGolden Release

Release0

ActiveBugs

Time

Module 8:Module 8:The Deploying PhaseThe Deploying Phase

Deployment Complete MilestoneDeployment Complete Milestone

Module 3

MSF OverviewMSF Overview

Module 10: Course SummaryModule 10: Course SummaryModule 5: The Planning PhaseModule 5: The Planning Phase

Module 9: MSF DisciplinesModule 9: MSF DisciplinesModule 4: The Envisioning PhaseModule 4: The Envisioning Phase

Module 8: The Deploying PhaseModule 8: The Deploying PhaseModule 3: The MSF Process ModelModule 3: The MSF Process Model

Module 7: The Stabilizing PhaseModule 7: The Stabilizing PhaseModule 2: The MSF Team ModelModule 2: The MSF Team Model

Module 6: The Developing PhaseModule 6: The Developing PhaseModule 1: Introduction to MSFModule 1: Introduction to MSF

Module 3

Suggested Interim MilestonesSuggested Interim Milestones

Module 3

Site Deployments Complete Interim MilestoneSite Deployments Complete Interim Milestone

ÂAccess to the solution by all targeted users ÂPossible revisit of some sites based on

feedback from site satisfaction surveys ÂStart of a concentrated effort to finish

stabilization and close out the project

Module 3

Deliverables

ÂOperation and support information systemsÉProcedures and processesÉKnowledge base, reports, logbooks

ÂRepository for all versions of:ÉDocumentation (architecture diagrams, etc.)ÉCode developed during the projectÉProject close-out reportÁFinal versions of all project documentsÁCustomer/user satisfaction dataÁDefinition of next steps

Deliverables for the Deploying PhaseDeliverables for the Deploying Phase

Module 9:Module 9:MSF DisciplinesMSF Disciplines

Module 3

MSF OverviewMSF Overview

Module 10: Course SummaryModule 10: Course SummaryModule 5: The Planning PhaseModule 5: The Planning Phase

Module 9: MSF DisciplinesModule 9: MSF DisciplinesModule 4: The Envisioning PhaseModule 4: The Envisioning Phase

Module 8: The Deploying PhaseModule 8: The Deploying PhaseModule 3: The MSF Process ModelModule 3: The MSF Process Model

Module 7: The Stabilizing PhaseModule 7: The Stabilizing PhaseModule 2: The MSF Team ModelModule 2: The MSF Team Model

Module 6: The Developing PhaseModule 6: The Developing PhaseModule 1: Introduction to MSFModule 1: Introduction to MSF

Module 3

MSF DisciplinesMSF Disciplines

 Risk Management Discipline—Increasing the potential for success

 Readiness Management Discipline—The right skills at the right time

 Project Management Discipline—Managing and meeting commitments

Module 3

Managing Project Risks

Module 3

Risk DefinedRisk Defined

ÂDefinitionsÉ Dictionary: “Possibility of loss or injury”

Webster’s Collegiate Dictionary, 10th editionÉ Common: A problem waiting to happen É Any event or condition that can cause an

unplanned impact or outcome of a project ÂCharacteristicsÉ Inherent in every projectÉ Neither intrinsically good nor badÉ Not something to fear, but something

to manage

The greatest risk is not taking one!

Module 3

Risk Management in MSFRisk Management in MSF

 Project Risk – The possibility of a negative outcome that is assumed in order to pursue an opportunity for gain in the project

 MSF risk management disciplineÉ Distinguishes risks from issues or problems that exist

already (“known problems”)É Defines a risk management process for proactively

identifying, analyzing, and addressing risks É Increases the likelihood of success in a project by minimizing

the potential for failure

Module 3

Analyze andPrioritize

Analyze andPrioritize

MasterRisk List

Top nRisks

Plan andSchedulePlan andSchedule

Identify

RiskStatement

ControlControl

The MSF Risk Management ProcessThe MSF Risk Management Process

LearnLearnRiskKnowledge Base,

Concepts,and Processes

Track andReport

Track andReport

Module 3

Creating Risk StatementsCreating Risk Statements

…we may ship with more bugs

Total Lossor

Opportunity Cost

Risk Statement

Risks must be clearly stated

ConsequenceConditionRootCause

ThereforeThe development and test roles have been

combined in this project

Module 3

Module SummaryModule Summary

MSF risk management is:Â Comprehensive – It addresses all of the elements in a

project (people, process, and technology elements)Â Systematic – It incorporates a six-step, reproducible

process for project risk management Continuous – It is applied throughout the project life cycle Proactive – It seeks to prevent or lessen impact of risk

occurrences Flexible – It can accommodate a wide range of quantitative

and qualitative risk analysis methodologies. Future-oriented – It is committed to individual and

enterprise level learning

Lesson 3: The MSF Readiness Discipline

Module 3

MSF: Readiness DefinedMSF: Readiness Defined

 Readiness—Current versus desired state of knowledge, skills and abilities of individuals in an organization

 Individual readiness—Current state of individual knowledge, skills and abilities versus that needed for project role

 Organizational readiness—Current state of collective degree of readiness used in both strategic planning and in evaluating capability to achieve successful adoption and realization of a technology investment

Module 3

Readiness Discipline ScopeReadiness Discipline Scope

 Focuses on the areas of knowledge, skills, and abilities for the individual, solution and enterprise architecture levels—not organizational readiness

Module 3

Readiness Management ProcessReadiness Management Process

Module 3

Readiness Management TasksReadiness Management Tasks

 Define:É ScenariosÉ CompetenciesÉ Proficiencies

 Assess:É Measure knowledge, skills, abilitiesÉ Analyze gapsÉ Create learning plans

 Change:É TrainÉ Track progress

 Evaluate:É Review resultsÉ Manage knowledge

Lesson 4: The MSF Project Management Discipline

Module 3

Microsoft Project ManagementMicrosoft Project Management

 Project Management is a serviceÉProvides assistance vs. control ÉRisk-driven scheduling

 All team members can and must contributeÉBottom-up estimationÉMotivated teams are more effective

 Half-complete tasks are not enoughÉGet something done every weekÉDon’t “go dark”

 Avoid bureaucracy—stay lean and agileÉEvery process and deliverable has a purpose

Module 3

Specialization of Program Management Role ClusterSpecialization of Program Management Role Cluster

Module 3

 KontaktÉ modulo3 GmbH

Michael W. DietrichKarl-Rudolf-Straße 17240215 Düsseldorffon: 0 8 00 - 87 67 2000mail: Michael.W.Dietrich@modulo3.de

 Further InformationÉ http://www.modulo3.deÉ http://www.Microsoft.com/MSF

 Q&AÉ Ihre Fragen (soweit noch nicht gestellt ;)