msf process model
TRANSCRIPT
主题
1. MSF概述1. MSF概述
2. 团队模型 2. 团队模型
5. 项目管理准则5. 项目管理准则
6. 就绪管理准则 6. 就绪管理准则
3. 过程模型3. 过程模型
4. 风险管理准则4. 风险管理准则
MSF Process Model
Project Plans Approved
Scope Complete
Release ReadinessApproved
DeploymentComplete
Vision/Scope Approved
MSFMilestone :
Used to plan and monitor project progress and schedule major deliverables
[1,5]
Create Living DocumentsBaseline Early, Freeze LateDaily builds
MSF is an Iterative process
Time
Functionality
Version 1
Version 2
Version 3
Force closure on project issuesSet clear and motivational goals with all team & stakeholder1
Manage the uncertainty and change in project scopeEncourage continuous and incremental feature deliveryEnable 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.
Iterations
Interim Milestones
Goals 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.
ENVISION
CORE TEAM ORGANIZED
VISION/SCOPE BASELINED
VISION/SCOPE APPROVED
Envision Phase
The primary team role driving the envisioning phase is the product management role.
Deliverables Vision/scope document [ TFS Vision] Project structure document [TFS Project Structure 1] Risk assessment document[ Self Define Excel 2 ]
Envision Phase
Recommended
TNet
Planning Phase
Deliverables Functional specifications [] Risk management plan[] Master project plan & Master project
schedule[]
Goal Customers and team members have agreed in detail on what is to
be delivered and when.
TECHNOLOGY VALIDATION COMPLETE 1
FUNCTIONAL SPECIFICATION BASELINED
MASTER PROJECT PLAN BASELINED
MASTER PROJECT SCHEDULE BASELINED
SUPPORTING ENVIRONMENTS SET UPPROJECT PLANS APPROVED
PLA
N
Change Control Methodology 2
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 Phase Functional specification BaseLined
Team analyzes and documents requirements in a list or tool.
Business requirementsUser requirementsOperational requirementsSystem requirements [TFS Logistics and Rollout Plan]
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 designLogical designPhysical design 3
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.
Instructions to developers on what to build.
Basis for estimating work. Agreement with customer on
exactly what will be built. Point of synchronization for the
whole team.
1
2
3
Once the functional spec is baselined, detailed planning can begin.
4
Planning Phase Functional specification BaseLined
Project PlanApproved
Project PlanApproved
Physical Design Baseline
Conceptual Design
Logical Design
Physical Design
VisionApproved
VisionApproved
Logical Design Baseline
Conceptual Design Baseline
Planning Phase Master Project Plan BaseLined
deployment planpilot planpurchasing planfacilities plantest plantraining plancommunication plancapacity plansecurity planbudget plan
Planning Phase Master Project Schedule BaseLined
Planning Phase Supporting Environments Set Up
Planning Phase
Recommended
TNet
Project Tradeoff Matrix
Given fixed ____________, we will choose a ___________ and adjust ___________ asnecessary.
Change Control Methodology
Avoid Scope Creep
Recommended
Schedule for an Uncertain Future Buffer
Use Small Teams, Working in Parallelwith Frequent Synchronization Points
Break Large Projects into Manageable Parts
Bottom-Up Estimating
Avoid Scope Creep
Cycle Rapidly
Use Frequent Builds and Quick Tests
Use Prototyping
Apply No-Blame Milestone Reviews 1
Establish Fixed Schedules
Focus Creativity by Evolving Features and Constraining Resources
MSF 各角色在不同阶段的职能
构思 计划 开发 稳定 部署
产品管理总体目标客户识别远景目标文档
概要设计业务需求分析沟通计划
客户预期 沟通计划执行发行计划
客户反馈评估验收
程序管理
设计目标解决方案概念项目结构
概要设计与逻辑设计功能规格主项目计划主项目进度预算
功能规格管理项目跟踪计划修订
项目跟踪Bug 测试
解决方案项目范围稳定性管理
开发原型开发和技术选型可行性分析
技术评估逻辑和物理设计开发计划、进度开发评价
代码开发平台开发配置文档
Bug 解决代码优化
问题的重新评估与解决对提升到开发组的问题的文件
用户体验用户功能和性能需求 场景及用例
用户需求本地化 / 可获得的需求用户文档、培训计划
培训修正培训计划可用性测试界面设计
用户手册培训资料
培训培训进度管理
测试测试方法测试接受标准
设计评估测试需求测试计划和进度安排
功能测试问题识别文档测试测试计划修订
测试Bug 报告和状态配建测试
性能测试问题的重新评估与解决
发布管理部署需求运行管理与支持运行接受标准
设计评估运行需求运行与发布的计划与进度安排
发布检验表发布与试行计划、时间部署点的检查表
是运行与支持发布计划运行与支持培训
站点部署管理变更批准