MSF Process Model DeploymentComplete Create Living Documents Baseline Early, Freeze Late Daily builds Release ReadinessApproved Vision/Scope Approved MSF Milestone : Used to plan and monitor project progress and schedule major deliverables Project Plans Approved Scope Complete [1,5]
MSF is an Iterative process Version 3 Version 2 Version 1 Functionality Time Force closure on project issues Set clear and motivational goals with all team & stakeholder1 Manage the uncertainty and change in project scope Encourage continuous and incremental feature delivery Enable shorter time to market 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.
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.
Master project plan & Master project schedule
Technology Validation Complete 1 Functional Specification Baselined Plan Master Project Plan Baselined Master Project Schedule Baselined Supporting Environments Set Up Project Plans Approved Change Control Methodology 2 Goal
Customers and team members have agreed in detail on what is to be delivered and when.
Planning Phase Technology Validation Complete 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. 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.
Planning PhaseFunctional specification BaseLined Team analyzes and documents requirements in a list or tool. Business requirements User requirements Operational requirements System requirements [TFS Logistics and Rollout Plan] 1 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. 3
Traceability 1 The 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 design Logical design Physical design 3 2 4 Once the functional spec is baselined, detailed planning can begin.
Project Tradeoff Matrix Change Control Methodology Avoid Scope Creep Given fixed ____________, we will choose a ___________ and adjust ___________ as necessary.
Recommended Focus Creativity by Evolving Features and Constraining Resources Establish Fixed Schedules Schedule for an Uncertain Future Buffer Use Small Teams, Working in Parallel with Frequent Synchronization Points Break Large Projects into Manageable Parts Apply No-Blame Milestone Reviews 1 Use Prototyping Use Frequent Builds and Quick Tests Cycle Rapidly Avoid Scope Creep Bottom-Up Estimating