Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

MSF Process model


Published on

Published in: Technology, Business
  • Be the first to like this

MSF Process model

  1. 1. 向微软学习MSF<br />2011-3-7<br />
  2. 2. 主题<br />1. MSF概述<br />2. 团队模型<br />3. 过程模型<br />4. 风险管理准则<br />5. 项目管理准则<br />6. 就绪管理准则<br />
  3. 3. MSF Process Model<br />DeploymentComplete<br />Create Living Documents<br />Baseline Early, Freeze Late<br />Daily builds<br />Release ReadinessApproved<br />Vision/Scope Approved<br />MSF<br />Milestone :<br />Used to plan and monitor project progress and schedule major deliverables <br />Project Plans Approved<br />Scope Complete<br />[1,5]<br />
  4. 4. MSF is an Iterative process<br />Version 3<br />Version 2<br />Version 1<br />Functionality<br />Time<br />Force closure on project issues<br />Set clear and motivational goals with all team & stakeholder1<br />Manage the uncertainty and change in project scope<br />Encourage continuous and incremental feature delivery<br />Enable shorter time to market<br />MSF recommends that solutions be developed by building, testing and deploying core functionality. Later sets of features are added. This is known as a version release strategy.<br />
  5. 5. Guidelines for Versioned Releases<br />• Create a multi-release plan.<br />• Deliver core functionality first.<br />• Cycle through iterations rapidly.<br />• Establish change control.<br />• Stop creating new versions when they no longer add value.<br />
  6. 6. Iterations <br />Interim Milestones<br />
  7. 7. Envision Phase<br />Deliverables<br /><ul><li>Vision/scope document [ TFS Vision]
  8. 8. Project structure document [TFS Project Structure 1]
  9. 9. Risk assessment document[ Self Define Excel 2 ]</li></ul>Core Team Organized<br />Envision<br />Vision/Scope Baselined<br />The primary team role driving the envisioning phase is the product management role.<br />Vision/Scope Approved<br />Goals<br /><ul><li>During the envisioning phase, business requirements must be identified and analyzed [BRD3] ,the project team and the customer have agreed on the overall direction for the project.
  10. 10. A general timetable for delivery.</li></li></ul><li>Envision Phase<br />Recommended<br />TNet<br />
  11. 11. Planning Phase<br />Deliverables<br /><ul><li>Functional specifications []
  12. 12. Risk management plan[]
  13. 13. Master project plan & Master project schedule[] </li></ul>Technology Validation Complete 1<br />Functional Specification Baselined<br />Plan<br />Master Project Plan Baselined<br />Master Project Schedule Baselined<br />Supporting Environments Set Up<br />Project Plans <br />Approved<br />Change Control Methodology 2<br />Goal<br /><ul><li>Customers and team members have agreed in detail on what is to be delivered and when.</li></li></ul><li>Planning Phase Technology Validation Complete<br />During technology validation, the team evaluates the products or technologies that will be used to build or deploy the solution to ensure that they work according to vendor’s specifications. <br />This is the initial iteration of an effort that later produces a proof of concept and, ultimately, the development of the solution itself.<br />Identify risks and update risk management plan 2.<br />Another activity that must be completed at this milestone is baselining the customer environment 1.<br />The primary team role driving the technology Validation phase is the program management role.<br />
  14. 14.
  15. 15. Planning PhaseFunctional specification BaseLined<br />Team analyzes and documents requirements in a list or tool.<br />Business requirements<br />User requirements<br />Operational requirements<br />System requirements [TFS Logistics and Rollout Plan]<br />1<br />The functional specification describes in detail how each feature is to look and behave. It also describes the architecture and the design for all the features.<br />3<br /><ul><li>Instructions to developers on what to build.
  16. 16. Basis for estimating work.
  17. 17. Agreement with customer on exactly what will be built.
  18. 18. Point of synchronization for the whole team.</li></ul>Traceability 1<br />The design process gives the team a systematic way to work from abstract concepts down to specific technical detail.<br />User profiles & Usage scenarios [ TFS-Persona definition2]<br />Conceptual design<br />Logical design<br />Physical design 3<br />2<br />4<br />Once the functional spec is baselined, detailed planning can begin.<br />
  19. 19. Planning Phase Functional specification BaseLined<br />Vision<br />Approved<br />Conceptual Design Baseline<br />Project Plan<br />Approved<br />Conceptual Design<br />Logical Design Baseline<br />Logical Design<br />Physical Design Baseline<br />Physical Design<br />
  20. 20. Planning Phase Master Project Plan BaseLined<br />deployment plan<br />pilot plan<br />purchasing plan<br />facilities plan<br />test plan<br />training plan<br />communication plan<br />capacity plan<br />security plan<br />budget plan<br />
  21. 21. Planning Phase Master Project Schedule BaseLined<br />
  22. 22. Planning Phase Supporting Environments Set Up<br />
  23. 23. Planning Phase<br />Recommended<br />TNet<br />
  24. 24. Project Tradeoff Matrix<br />Change Control Methodology <br />Avoid Scope Creep<br />Given fixed ____________, we will choose a ___________ and adjust ___________ as<br />necessary.<br />
  25. 25. Recommended<br />Focus Creativity by Evolving Features and Constraining Resources<br />Establish Fixed Schedules<br />Schedule for an Uncertain Future <br /> Buffer<br />Use Small Teams, Working in Parallel<br />with Frequent Synchronization Points<br />Break Large Projects into Manageable Parts<br />Apply No-Blame Milestone Reviews 1<br />Use Prototyping<br />Use Frequent Builds and Quick Tests<br />Cycle Rapidly<br />Avoid Scope Creep<br />Bottom-Up Estimating<br />
  26. 26. MSF各角色在不同阶段的职能<br />