Is Your Project Out Of Control?

1. MSF Overview(Microsoft Solutions Framework)Eran KolberVice President – LIH LtdRegional Director – MicrosoftProduct Management Advisor – MSF Development Team (Seattle)v-erank@microsoft.comkolberey@lihgroup.com

2. Is Your Project Out Of Control?

3. Failed 28% Challenged 46% 26% Succeeded Standish Group Survey • Based on more than 30,000 projects • Challenged means completed over budget or past the original deadline

4. Root Causes of Failure • Separation of goal andfunction • Separation of businessand technology • Lack of common languageand process • Failure to communicateand act as a team • Processes that are inflexible to change “When projects fail, it’s rarely technical.” Jim Johnson, The Standish Group

5. Challenged Results • Average cost overrun:189% • Projects restarted:94% • Average time overrun:222% • Average functionality delivered:61%

6. MSF Defined

7. What is ? • Guidance to help organizations be more successful delivering IT Solutions: • Faster, • With fewer people, • Less risk, • While enabling higher quality results • A collection of principles, processes and best practices that work well together • Grouped into “Models & Disciplines”

8. MSF Models and Disciplines Models ProcessModel TeamModel Disciplines ProjectManagementDiscipline RiskManagementDiscipline ReadinessManagementDiscipline

9. Frameworks:Supplementing Methodologies • A methodology applies specific directions to a known destination • A framework, like a compass, verifies progress and provides directional guidance Plum Street Orange Street 1st Avenue 2nd Avenue 3rd Avenue . . . . . . 4th Avenue N . . W E . . Smith River . . . . S MSF

10. The Origin of MSF Microsoft Worldwide Products Groups Microsoft Consulting Services • Analyzes results from project teams and product groups • Contrasts these with industry practices and methods • Organizes and consolidates into “people and process” guidance ProvenPractices Microsoft Information TechnologyGroup Evolving since 1993 Microsoft Partners

11. Team Management Model

12. Team 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

13. Program Management Product Management Development Team of Peers User Experience Testing Release Management MSF Team Model

14. Why These 6 Roles? • Key goals need dedicated equally valued roles: • Customer Satisfaction: Product Manager • Project delivered within Project Constraints: Program Manager • Design and Implementation Based on Specification: Development • All Issues Known and Addressed: Testing • Users Performing Better: User Experience • Deployment, Admin, and Support: Release Management

15. Teams: Scaling Down Product Management Program Management Development Release Management User Experience Testing

16. Process Model

17. MSF Process Model DeploymentComplete Release ReadinessApproved Vision/Scope Approved MSF Project Plans Approved Scope Complete

18. Envisioning Phase • Deliverables • Vision/scopedocument • Project structuredocument • Initial riskassessment document

19. Alice: “Would you tell me please, which way I ought to go from here?” Cat: “That depends a good deal on where you want to get to.” Alice: “I don’t much care where …” Cat: “Then it doesn’t matter which way you go.” Alice in Wonderlandby Lewis Carroll Setting the Target

20. Using VersionedReleases to Keep Up With the Curve Technology Business Rate of Change Versioned Releases Obsolete Solution Traditional Release Study and Analysis Time in Six-Month Cycles

21. Planning Phase Deliverables: • Functionalspecifications • Master projectplan • Master projectschedule

22. Resources Schedule Features Defining the Scope Resources Envisioning Schedule Features Planning

23. Cost of Fixing a PoorlyDesigned Solution 100 80 60 40 20 Relative Cost Developing Stabilizing Deploying Envisioning Planning Project Phase

24. Developing Phase Deliverables: • Solution code • Build images • Training materials • Documentation • Deployment processes • Operational procedures • Support and troubleshooting • Marketing materials • Updated master plan and schedule

25. Testing the Solution Testing is part of the build cycle, not a standalone activity Release ReadinessApproved MSF Project PlansApproved ScopeComplete

26. Stabilizing Phase Deliverables: • Pilot review • Release-ready versions: • Source code andexecutables • Scripts and installation documentation • End-user help and training materials • Operations documentation • Release notes • Testing and bug reports • Project documents

27. MSF Deploying Phase Milestones and Deliverables • Deliverables • Operations andsupport informationsystems • Repository of allversions of docs,load sets, configs,scripts, and code • Project close-out report

28. Remember … You Don’t KnowWhat You Don’t Know!

29. Analyze andPrioritize RiskStatement MasterRisk List Identity Plan andSchedule Control Top nRisks Track andReport Learn RiskKnowledge Base,Concepts,and Processes MSF Risk Management Process

30. MSF ReadinessManagement Discipline • Use proactive vs.reactive approach • Treat readiness gaps as risks • Capture and manage team knowledge • Focus on individual, not organizational readiness • Remember – the need for team readiness spans the life of the project Define Assess KnowledgeSkillsAbilities Evaluate Change

31. Information Sources

32. More Information • www.microsoft.com/msf

33. Organizational Change. We Support It. v-erank@microsoft.com kolberey@lihgroup.com תודה!