Your SlideShare is downloading. ×
MSF Process model
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

MSF Process model

1,050
views

Published on

Published in: Technology, Business

1 Comment
0 Likes
Statistics
Notes
  • Be the first to like this

No Downloads
Views
Total Views
1,050
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
21
Comments
1
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. 向微软学习MSF
    2011-3-7
  • 2. 主题
    1. MSF概述
    2. 团队模型
    3. 过程模型
    4. 风险管理准则
    5. 项目管理准则
    6. 就绪管理准则
  • 3. 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]
  • 4. 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.
  • 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 Phase
    Deliverables
    • Vision/scope document [ TFS Vision]
    • 8. Project structure document [TFS Project Structure 1]
    • 9. Risk assessment document[ Self Define Excel 2 ]
    Core Team Organized
    Envision
    Vision/Scope Baselined
    The primary team role driving the envisioning phase is the product management role.
    Vision/Scope Approved
    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.
    • 10. A general timetable for delivery.
  • Envision Phase
    Recommended
    TNet
  • 11. Planning Phase
    Deliverables
    • Functional specifications []
    • 12. Risk management plan[]
    • 13. 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.
  • 14.
  • 15. 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
    • Instructions 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 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.
  • 19. Planning Phase Functional specification BaseLined
    Vision
    Approved
    Conceptual Design Baseline
    Project Plan
    Approved
    Conceptual Design
    Logical Design Baseline
    Logical Design
    Physical Design Baseline
    Physical Design
  • 20. Planning Phase Master Project Plan BaseLined
    deployment plan
    pilot plan
    purchasing plan
    facilities plan
    test plan
    training plan
    communication plan
    capacity plan
    security plan
    budget plan
  • 21. Planning Phase Master Project Schedule BaseLined
  • 22. Planning Phase Supporting Environments Set Up
  • 23. Planning Phase
    Recommended
    TNet
  • 24. Project Tradeoff Matrix
    Change Control Methodology
    Avoid Scope Creep
    Given fixed ____________, we will choose a ___________ and adjust ___________ as
    necessary.
  • 25. 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
  • 26. MSF各角色在不同阶段的职能