MSF Microsoft Solutions Framework Past and present Peter

MSF: Microsoft Solutions Framework Past and present Peter Williams, Microsoft Ltd.

Agenda • A Brief History of MSF • MSF Core • MSF and Visual Studio Team system • MSF for Agile Software Development • MSF for CMMI® Process Improvement • Real World Experiences

A Brief History of MSF Offering ‘Dynamics’ MSF v 1 1994 21 Rules 1995 MSF v 3 MSF v 2. 5 Solutions Dev Discipline (SDD) Principles of … Essentials App Dev (PAD) + Exam Infra Deploy (PID) Ent Arch (PEA) Comp Des (PCD) 1997 1999 2002 MSF v 4 Core Agile CMMI … 2005 -06

MSF Core: What It’s Not • MSF Core is not a methodology • It’s a framework • It requires instantiation for the specific solution domain • Not a magic sauce • Not specific to software development • Although Visual Studio Team System provides two instantiations which are specific to software development • MSF for Agile Software Development • MSF for CMMI® Process Improvement

MSF Core • A collection of best practices gathered from the product groups and the field • Key elements • Mindsets (key concepts) • Foundational Principles • Models • Disciplines • Proven practices • Recommendations

MSF Core Mindsets • • • Team of Peers Quality is everyone’s business every day Pride of workmanship Deliver on your commitments Focus on business value Solution mindset Design for qualities of service Trusting mindset Continual learning mindset Reuse and extend

MSF Core Foundational Principles • • • Foster open communications Work towards a shared vision Empower team members Establish clear accountability and shared responsibility Incremental delivery of value Stay agile, expect and adapt to change Invest in quality Learn from all experiences Partner with customers Early and frequent deployments Design early with specific examples

MSF Core Models • Team model • Based on advocacy creating natural checks and balances • Governance & Enactment (Process) model • Appropriate level of governance • Iterative, versioned releases, etc. • Risk management model • Proactive risk management

MSF Core Team Model Program Management Architecture Solution Delivery Product Management Solution Definition Solution Design Advocacy Groups Development Solution Construction / Verification Natural Checks and balances User Experience Solution Usability and User readiness Test Release Management Solution Deployment Solution Validation

MSF Core Advocacy Business Focus Users Operatio ns Support User Experience Product Management Test Custom er Project Team Development Operatio ns Release / Operations Technology Focus Program Management Architecture Technology Architects Project Sponso r Solution s Architec ts

Scaling Down: Combining Advocacy Groups Product Management Program Management N Architecture Development Test User Experience Release / Operations N N P P U P N U U U P U U U N N N P P Program Management N Architecture N P Development N N P Test P U U N User Experience P U U N P Release / Operations U U U N P Possible Unlikely Not recommended U U

Scaling Up: Feature Teams User Experience Program Management Development User Experience Fulfillment Catalog Test Program Management Test Release Management Development User Experience Site Engine & Design Test

MSF Version 4 Governance & Enactment Model • Enactment Tracks • Envision Deploy • Plan • Build • Stabilise • Deploy Stabilise Enactment Envision • Governance Track • Checkpoint-based Build Plan Governance

Governance Examples • MSF for Agile Software Development implements a very lightweight governance model

Governance Examples • MSF for CMMI® Process Improvement implements a more rigorous governance model

MSF Core Risk Management Model • Proactive Management • Identify • Analyse and Prioritise • Plan and Schedule • Track and Report Status • Control Risks • Learn from Risks

MSF and Visual Studio Team System enacts Visual Studio 2005 Team System guides Microsoft Solutions Framework

Enacting MSFv 4 ‘Core’ Application Development MSF for Agile Software Development Infrastructure MSF for CMMI® Process Improvement Discipline Family Product

Enacting MSF v 4 CMMI Infrastructure Agile MSF v 3

Real World Usage • Globally within Microsoft • Used by Microsoft Services since 1994 • Used by Microsoft Internal operations • Based on product group principles and best practices • Closer to home within Microsoft • Used by the UK Solution Development Group to deliver large-scale enterprise solutions • Use by other external organisations

UK Enterprise Solutions built with MSF NBP Tax Credits Online digital curriculum

Personal Experiences • Core principles and approach very similar to the product group approach. Some differences due to the nature of solution development. • A very good success rate on very challenging projects.

Favourite aspects of MSF • Team model • Common goal • Two-way advocacy not just ‘gathering’ requirements • Platform for trade offs • All disciplines represented from the start • All disciplines participate in the design • Small multi-disciplinary teams • Co-location • Motivational

Favourite aspects of MSF • Envisioning track • Forming a vision • Opening up possibilities never before imagined • User experience as a first-class citizen • An area often neglected in other approaches • Base line early and freeze late • Expecting change • Iterative development • Rehearsal for go-live

Favourite Aspects of MSF • Ship every day • Build is not enough • A team exercise • Build hand-off • Repeatable platform builds • Triage • One representative per discipline • ‘Quaker’ consensus

Questions?