MSF v4 - Shorter

7/29/2019 MSF v4 - Shorter

1/38

TEAVNOST: 200

Microsoft SolutionsFramework MSF v4

Rafal LukawieckiStrategic Consultant

[email protected] Botticelli Ltd

This presentation is based on work by Microsoft TechNet, MSDN and various Microsoft authors including, withspecial thanks: Ramprabhu Rathnam, Tony Northrup, and Austin Wilson


2/38

TEAVNOST: 200

2

Objectives Convince you that non-technical

reasons impact project success a lot

Show you an approach to productmanagement that has proven to bevery successful

Explain the recent developments


3/38

TEAVNOST: 200

3

Agenda

Introduction to Frameworks

Components of MSF v3 and v4 Future


4/38

TEAVNOST: 200

4

Introduction:Why Projects Fail?

What are Frameworks?


5/38

TEAVNOST: 200

5

MSF Microsoft Solutions Framework

Established in 1991, made public in 1993 (v1),

fully revised in 1998 (v2), January 2003 (v3)and now in March 2006 (v4)

Product development framework for creatingsoftware and infrastructure deployment

Related to MOF, Microsoft OperationalFramework

Which concentrates on the management of ITinfrastructure


6/38

TEAVNOST: 200

6

IT Lifecycle

Microsoft Operations Framework

Microsoft Solutions Framework


7/38

TEAVNOST: 200

7

Does it Work? Yes, as long as you chose the right

bits of MSF for your project

High-profile projects that used MSF

www.nasdaq.com andwww.marriott.com (Aris Corp, now

Ciber, www.ciber.co.uk)UK Government Gateway (eGov)

Visual Studio, Windows 2003, Windows

XP
http://www.nasdaq.com/http://www.marriott.com/http://www.ciber.co.uk/http://www.ciber.co.uk/http://www.marriott.com/http://www.nasdaq.com/


8/38

TEAVNOST: 200

8

Whats a Framework? Unlike a methodology, a framework

is a set ofconceptual tools and best

practices

However, in many ways MSF v4 iscloser to a methodology than v3


9/38

TEAVNOST: 200

9

When projects fail, itsrarely technical.

Jim Johnson, The Standish Group

Root Causes of Failure Separation of goal and

function

Separation of business and

technology

Lack of common language andprocess

Failure to communicate and

act as a team

Processes that are inflexibleto change

Solution?

A good and tested framework!

Average cost overrun:45%

Time overrun:

63%Functionality delivered onaverage:67%

Standish Group


10/38

TEAVNOST: 200

10

Evolution fromMSF v3 to v4


11/38

TEAVNOST: 200

11

MSF Partner Council Who Advised v4

2
http://www.eds.com/http://www.eds.com/


12/38

TEAVNOST: 200

12

Evolution to MSF v4

13


13/38

TEAVNOST: 200

13

Status MSF v3 is fully released and available

Study course MOC #1846

MSF v4 for Application Development (both Agileand CMMI) have just shipped on 29 March 2006

Download guidance from www.microsoft.com/msf

MSF v4 for Infrastructure Deployment and other

flavours (Solutions, Consulting, etc.) are underdevelopment at present

This is news! Good news.

14
http://www.microsoft.com/msfhttp://www.microsoft.com/msf


14/38

TEAVNOST: 200

14

Agility Agility of the development process is the

key to being able to cope with inevitable

changes (spec, environment, business) orplanning errors

The price of it is a certain unpredictabilityof the process

Finish date, final cost, feature set

Generally, agility is great for small andmedium projects in existing and tested

dev environments

15


15/38

TEAVNOST: 200

15

CMMI Capability-Maturity Model Integration describes 5 (or 6)

levels of process-based predictability of an organisation (ordepartment) in terms of their ability to produce qualitysoftware

Level 5 is best. Most companies are 0 or 1. MSF v4 can helpyou work at level 3 or more.

Moving towards higher levels is done by adopting highlypredictable (but not so agile) processes

Great for larger or more formal projects, especially in morecritical environments

By the way, MSF and CMMI are not strangers: KPMGpublished a paper on how MSF v1 could help you with CMMalready in 1995!

16


16/38

TEAVNOST: 200

16

Observation MSF v3 seems moreformal than

MSF for Agile Software Development

We lose some of the structure andmodelling from v3 and replace themwith a more integrated agile process

MSF v3 seems lessformal thanMSF for CMMI Process Improvement

Structures from v3 are becoming more

process-improvement oriented

17


17/38

TEAVNOST: 200

17

What About Extreme

Programming? Extreme Programming (XP), which was created

after MSF, has similarities Similarities regarding the Zero Defect Mindset and Daily

Builds

XP is less predictable than necessary for moreformal projects But great for very agile projects

MSF for Agile Software Development seems more

predictable, controllable and even more agilethan XP MSF CMMI Process Improvement, naturally, is

less agile than XP, but seems the mostpredictable

18


18/38

TEAVNOST: 200

18

Key Componentsof MSF

19


19/38

TEAVNOST: 200

19

A Team of Peers (v4 Agile)

20


20/38

TEAVNOST: 200

20

Scaling the Team Model Feature &

Function

TeamsTechnique

Example:

21


21/38

TEAVNOST: 200

21

Designing Software within MSF UML (Unified Modelling Language) has a

great tradition, though we may need to

evolve towards a service-orientedapproach

UML2? Perhaps, but its possible to be moredirect in design.

Domain Specific Languages! Great conceptual integration both with MSF

and with the tools (VSTS)

Further, possible, integration with SDM and

DSI

22


22/38

TEAVNOST: 200

22

Project Management in v4 One of the most powerful features of

Visual Studio Team System is its

automation of project managementWorkstreams, Work Items, and Roles

concepts

Uses Team Foundation ServerRelies on Microsoft Project-style

planning documents

23


23/38

TEAVNOST: 200

MSF Process Model v3

Project PlansApprovedScopeComplete

Release ReadinessApproved

DeploymentComplete

Vision/ScopeApproved

MSF

24


24/38

TEAVNOST: 200

Envision

Plan

Build

Stabilize

Deploy

Release 1

MSFv4

25


25/38

TEAVNOST: 200

Process Modelling in v4 MSF v4 introduces a new model ofGovernance

and Enactmentwhich replace the traditional

process model This caters for different types of processes, which

are now defined at the level of methodology,

rather than the framework

This makes MSF v4 much more suited to work inteams both very small and very big, as opposed

to what v3 could have ever catered for

27


26/38

TEAVNOST: 200

Iterations Achievement of a pre-determined level of

quality

Based on planning of feature-sets Mechanism to correct project plan deviations

28


27/38

TEAVNOST: 200

Governance Process mapped onto specific iterations

29


28/38

TEAVNOST: 200

Cycles The foundation of every days co-

ordinated work of the team

30


29/38

TEAVNOST: 200

Daily (Nightly) BuildBuilding the product ina deployable form on a

daily basis

A daily build is

A strong indicator that a team is functional

Guarantee against component integration problems A way to make the product and its progress visible

The heartbeatof the development process

A key function of VSTF (see later)

32


30/38

TEAVNOST: 200

Quality CriteriaKnowing When You Can Ship

MSF v4 defines:

Minimum Acceptance Level (Scenarios) Relates to Core Functionality Set

Test Thresholds

Code Coverage for Unit Tests

Other, context-driven (bugs per developer)

VSTS manages tracking and reporting ofthese quality criteria during all phases ofthe project

33


31/38

TEAVNOST: 200

Work Items Activities and Workstreams manage the

concept of a work item, which describes

an assignable, individual piece of effortthat needs to be done:

Bug

Quality of Service Requirement

Scenario

Risk (not yet in the beta of VSTS, but soon)

Task

34


32/38

TEAVNOST: 200

ProcessModule

Phase

Iteration

Activity

parentwork1..*

subwork1..*

Role

work

1..*

performer

1

Step

parentwork1

subwork1..*

WorkProduct

ResponsibilityKind

1..* work_product_responsibility

1..* responsibleRole0..*

output1..*

1..*

input0..*

ProjectTask

1

0..*

WorkItem

StateMachine

lifeCycle 1

*

WorkProductItem

WorkActivityItem

enacts

Assignment

1 0..*

0..1

0..1

1

0..*

enacts0..1

enacts

0..1

enacts

0..1

Guidance

Discipline

SecurityGroup

enacts

Artifact

enacts

SourceArtifact

PortalArtifact

ReferencedArtifact

PatternsCookbook

enacts

ProcessHelp

enacts

ActivityInclusion

Constraint

constrainedElement

State

WorkProductInState

Process

Model

35


33/38

TEAVNOST: 200

Team System Ingenious: tool that implements MSF!

As soon as you create a new project in VSTS you get tochose which version of MSF v4 you want to use!

VS 2005 TS manages the flow of work itemsbetween team members, as well as overlookstheir progress

Individual versions for Developer Architect Tester

Reporting and management tools for projectmanager and other team members Includes Outlook, Excel and Project Support

36


34/38

TEAVNOST: 200

Future

37


35/38

TEAVNOST: 200

MSF and Software Development Without a doubt, the emphasis of MSF v4

is on software development

The MSF team is now firmly a part of theVisual Studio group within Microsoft

Tying the framework to the tools (VSTS)was the masterstroke that gave MSF a

very prosperous future And vice-versa: the method adds value to the

tools, beyond what any Microsoft competitorcould offer today

38


36/38

TEAVNOST: 200

MSF for Infrastructure

Deployment While initially there was a little confusion,

it has now been confirmed that MSF v4will cater for Infrastructure Deployment

too While the detail is being finalised, please

consider using MSF v3 or MOF for purelyinfrastructure deployment oriented

projects Consider using the more flexible processapproaches from v3

Soft skills, whichever version, like all goodideas, age only like wine, anyway

39


37/38

TEAVNOST: 200

Summary Projects fail for non-technical reasons

A framework such as MSF fixes those

problem You dont have to use all of MSF at once

If you use some bits you increase your

chance of succeeding Visual Studio Team System is a

marvellous implementation of MSFprinciples

40


38/38

TEAVNOST 200

Resources www.microsoft.com/msf

MSF for Agile Software Development: lab.msdn.microsoft.com/teamsystem/workshop/msfagile/defau

lt.aspx MSF for CMMI Process Improvement:

lab.msdn.microsoft.com/teamsystem/workshop/msfcmmi/default.aspx

MSF v3: msdn.microsoft.com/vstudio/enterprise/msf/

MSF Forum: forums.microsoft.com/msdn/ShowForum.aspx?ForumID=63

MOF: www.microsoft.com/mof
http://www.microsoft.com/msfhttp://lab.msdn.microsoft.com/teamsystem/workshop/msfagile/default.aspxhttp://lab.msdn.microsoft.com/teamsystem/workshop/msfagile/default.aspxhttp://lab.msdn.microsoft.com/teamsystem/workshop/msfcmmi/default.aspxhttp://lab.msdn.microsoft.com/teamsystem/workshop/msfcmmi/default.aspxhttp://msdn.microsoft.com/vstudio/enterprise/msf/http://forums.microsoft.com/msdn/ShowForum.aspx?ForumID=63http://www.microsoft.com/mofhttp://www.microsoft.com/mofhttp://forums.microsoft.com/msdn/ShowForum.aspx?ForumID=63http://msdn.microsoft.com/vstudio/enterprise/msf/http://lab.msdn.microsoft.com/teamsystem/workshop/msfcmmi/default.aspxhttp://lab.msdn.microsoft.com/teamsystem/workshop/msfcmmi/default.aspxhttp://lab.msdn.microsoft.com/teamsystem/workshop/msfagile/default.aspxhttp://lab.msdn.microsoft.com/teamsystem/workshop/msfagile/default.aspxhttp://www.microsoft.com/msf

Documents

MSF v4 - Shorter