Microsoft Solutions Framework v4

1
Microsoft Solutions Framework v4

• Rafal Lukawiecki
• Strategic Consultant Director
• Project Botticelli Ltd
• rafal_at_projectbotticelli.co.uk

2
Objectives

• Introduce MSF and related frameworks
• Briefly explain the main components of MSF v3
• Explain the new aspects of MSF v4 for Agile
  Software Development
• Discuss the future

3
MSF

• Microsoft Solutions Framework
• Established in 1991, last fully released major
  revisions in 1998 and January 2003 (v3)
• Project development framework for software
  development and infrastructure deployment
• Related to MOF, Microsoft Operational Framework
• Which concentrates on the management of IT
  infrastructure

4
Lifecycle of IT
Microsoft Solutions Framework
Plan
Operate
Build
Deploy
Microsoft Operations Framework
5
Project Failure Rates
Succeeded
Challenged
Failed
28
23
49
2000
26
28
46
1998
27
40
33
1995
16
31
53
1994
This chart depicts the outcome of the 30,000
application projects in large, medium,and small
cross-industry U.S. companies tested by The
Standish Group since 1994. Source The Standish
Group International, Extreme Chaos, The Standish
Group International, Inc., 2000
6
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 and www.marriott.com (Aris Corp,
  now Ciber, www.ciber.co.uk)
• UK Government Gateway (eGov)
• Visual Studio, Windows 2003, Windows XP

7
Whats a Framework?

• Unlike a methodology, a framework is a set of
  conceptual tools and best practices
• Is that good?
• Yes, because it is easier to apply, more flexible
  and less restrictive
• Yes, because it combines well with methodologies
  (RUP, Prince 2, etc.)
• No, because you have to make choices

8
Is It For Everyone?

• Some parts of MSF will work for every project
• Most of MSF v3 is for larger projects
• How small is large enough?
• 3-12 months (best of all 4-6) and with a team of
  at least 3 (best of all 4-11)
• Or more, by using built-in team scaling tools,
  such as Feature Teams
• MSF v4 works very well even for smallest projects

9
Root 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
• Solution?
• A good and tested framework!

When projects fail, its rarely technical. Jim
Johnson, The Standish Group
Average cost overrun 45 Time overrun
63 Functionality delivered on average
67 Standish Group
10
Evolution to Version 4
11
Status

• MSF v3 is fully released and available
• Study course MOC 1846
• MSF for Agile Software Development is in Beta and
  expected to ship with Visual Studio 2005 Team
  System
• Download documents from www.microsoft.com/msf
• MSF for CMM Improvement is pre-beta
• Await further announcements

12
Key MSF v3/v4 Components
13
Key MSF Components
Models
ProcessModel
TeamModel
Disciplines
ReadinessManagementDiscipline
RiskManagementDiscipline
ProjectManagementDiscipline
14
A Team of Peers (v3)
Communication
15
A Team of Peers (v4)
16
Scaling The Model

• You can combine some roles to teams as small as 3
  people
• Do not combine some (like Product and Program
  Manager, or anything with Developer)
• You can scale it to 10, 100s and 1000s by using
  two methods
• Functional Teams (many people for one role)
• Feature Teams (sub-teams for each feature)

17
Project Management

• As of v3, full alignment with PMIBOK (Project
  Management Institute Body of Knowledge)
• Traditionally MSF has not been a project
  management method, but a project framework for
  product development
• As of v4 there is a strong emphasis on integrated
  project management

18
Project Management in v4

• One of the most powerful features of Visual
  Studio Team System is its automation of project
  management
• Workstreams, Work Items, and Roles concepts
• Uses Team Foundation Server
• Relies on Microsoft Project-style planning
  documents

19
MSF Process Model v3
DeploymentComplete
Release ReadinessApproved
Vision/Scope Approved
MSF
Project Plans Approved
Scope Complete
20
Process Modelling in v4

• MSF Agile does emphasises the principle of
  Governance through Checkpoints and formalises the
  concept of Tracks
• This largely replaces a formal process model
• One is expected, however, in the MSF for CMM
  Improvement (MSF Formal) approach
• This makes MSF v4 more suited to work in smaller
  teams than v3 could have catered for

21
Tracks

• Tracks overlap each other and are controlled by
  checkpoints
• Envision
• Plan
• Build
• Stabilize
• Deploy
• Continuous

22
Cycles

• The foundation of every days co-ordinated work
  of the team

23
Iterations

• Achievement of a pre-determined level of quality
• Based on planning of feature-sets
• Mechanism to correct project plan deviations

24
Work Items

• Activities and Workstreams manage the concept of
  a work item, which describes an assignable,
  individual piece of effort that needs to be done
• Bug
• Quality of Service Requirement
• Scenario
• Risk
• Task

25
Team System

• VS 2005 TS manages the flow of work items between
  team members, as well as overlooks their progress
• Individual versions for
• Developer
• Architect
• Tester
• Reporting and management tools for project
  manager and other team members
• Includes Outlook, Excel and Project Support

26
Risk Management Process
Risk Statements
2. Analyze
1. Identify
Risk Assessment Document Top 10
Retired Risks
3. Plan
5. Control
4. Track
27
Risk Management in v4

• The formal process is de-emphasised
• The discipline is, however, implemented through a
  Risk work item
• With own activities and workstreams

28
Future
29
MSF Agile

• Without a doubt, a most excellent development of
  MSF
• Great support in VS TS
• Power of the tools makes this one of the best
  environments to automate software production

30
MSF Formal

• MSF for CMM Improvement is likely to take a more
  formal approach to project management
• Will be very useful for repeated or larger
  projects
• Might be particularly useful in consulting
  engagements
• No clear time frame at present

31
MSF for Infrastructure Deployment

• This aspect of MSF v3 is likely to be integrated
  into MOF
• Some aspects of MSF Formal might support purely
  deployment-oriented projects
• In the meantime, please consider using MSF v3 for
  those projects

32
Summary

• Projects fail for non-technical reasons
• A framework such as MSF fixes that 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 MSF principles