MSF is an iterative process model used by Microsoft for project management. It consists of envision, planning, and development phases. In the envision phase, requirements are identified and the overall project direction is agreed upon. In the planning phase, detailed plans are created for what will be delivered and a schedule is established. Functional specifications are documented and validated. The development phase consists of iterative development where functionality is added incrementally in versions until the project is complete.

1. 向微软学习MSF2011-3-7

2. 主题1. MSF概述2. 团队模型3. 过程模型4. 风险管理准则5. 项目管理准则6. 就绪管理准则

3. MSF Process ModelDeploymentCompleteCreate Living DocumentsBaseline Early, Freeze LateDaily buildsRelease ReadinessApprovedVision/Scope ApprovedMSFMilestone :Used to plan and monitor project progress and schedule major deliverables Project Plans ApprovedScope Complete[1,5]

4. MSF is an Iterative processVersion 3Version 2Version 1FunctionalityTimeForce closure on project issuesSet clear and motivational goals with all team & stakeholder1Manage the uncertainty and change in project scopeEncourage continuous and incremental feature deliveryEnable shorter time to marketMSF 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.

5. Guidelines for Versioned Releases• Create a multi-release plan.• Deliver core functionality first.• Cycle through iterations rapidly.• Establish change control.• Stop creating new versions when they no longer add value.

6. Iterations Interim Milestones

7. Envision PhaseDeliverablesVision/scope document [ TFS Vision]

8. Project structure document [TFS Project Structure 1]

9. Risk assessment document[ Self Define Excel 2 ]Core Team OrganizedEnvisionVision/Scope BaselinedThe primary team role driving the envisioning phase is the product management role.Vision/Scope ApprovedGoalsDuring 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. A general timetable for delivery.Envision PhaseRecommendedTNet

11. Planning PhaseDeliverablesFunctional specifications []

12. Risk management plan[]

13. Master project plan & Master project schedule[] Technology Validation Complete 1Functional Specification BaselinedPlanMaster Project Plan BaselinedMaster Project Schedule BaselinedSupporting Environments Set UpProject Plans ApprovedChange Control Methodology 2GoalCustomers and team members have agreed in detail on what is to be delivered and when.Planning Phase Technology Validation CompleteDuring 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. This is the initial iteration of an effort that later produces a proof of concept and, ultimately, the development of the solution itself.Identify risks and update risk management plan 2.Another activity that must be completed at this milestone is baselining the customer environment 1.The primary team role driving the technology Validation phase is the program management role.

15. Planning PhaseFunctional specification BaseLinedTeam analyzes and documents requirements in a list or tool.Business requirementsUser requirementsOperational requirementsSystem requirements [TFS Logistics and Rollout Plan]1The 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.3Instructions to developers on what to build.

16. Basis for estimating work.

17. Agreement with customer on exactly what will be built.

18. Point of synchronization for the whole team.Traceability 1The design process gives the team a systematic way to work from abstract concepts down to specific technical detail.User profiles & Usage scenarios [ TFS-Persona definition2]Conceptual designLogical designPhysical design 324Once the functional spec is baselined, detailed planning can begin.

19. Planning Phase Functional specification BaseLinedVisionApprovedConceptual Design BaselineProject PlanApprovedConceptual DesignLogical Design BaselineLogical DesignPhysical Design BaselinePhysical Design

20. Planning Phase Master Project Plan BaseLineddeployment planpilot planpurchasing planfacilities plantest plantraining plancommunication plancapacity plansecurity planbudget plan

21. Planning Phase Master Project Schedule BaseLined

22. Planning Phase Supporting Environments Set Up

23. Planning PhaseRecommendedTNet

24. Project Tradeoff MatrixChange Control Methodology Avoid Scope CreepGiven fixed ____________, we will choose a ___________ and adjust ___________ asnecessary.

25. RecommendedFocus Creativity by Evolving Features and Constraining ResourcesEstablish Fixed SchedulesSchedule for an Uncertain Future BufferUse Small Teams, Working in Parallelwith Frequent Synchronization PointsBreak Large Projects into Manageable PartsApply No-Blame Milestone Reviews 1Use PrototypingUse Frequent Builds and Quick TestsCycle RapidlyAvoid Scope CreepBottom-Up Estimating

26. MSF各角色在不同阶段的职能