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 />
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 />
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 />
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.
A general timetable for delivery.</li></li></ul><li>Envision Phase<br />Recommended<br />TNet<br />
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 />
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.
Agreement with customer on exactly what will be built.
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 />