Tài liệu Module 3: MSF Process Model pdf

Module 3: MSF Process Model Contents Overview Introduction to Process Models Applying the MSF Process Model Underlying Principles of the MSF Process Model 10 Review 15 Information in this document is subject to change without notice The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted Complying with all applicable copyright laws is the responsibility of the user No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation If, however, your only means of access is electronic, permission to print one copy is hereby granted Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property  1999 Microsoft Corporation All rights reserved Microsoft, MS-DOS, MS, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A and/or other countries The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted Other product and company names mentioned herein may be the trademarks of their respective owners MOC Project Advisor: Janet Wilson MOC Project Lead: Sharon Salavaria Program Manager/MSF Project Manager: Sharon Limbocker Program Manager/Technical Consultant: Dolph Santello Instructional Designer: Marilyn McCune (Independent) Product Manager: Jim Wilson Product Manager: Jerry Dyer Graphic Artist: Andrea Heuston (Artitudes Layout & Design) Editing Manger: Lynette Skinner Editors: Marilyn McCune (Independent) and Wendy Cleary (S&T Onsite) Production Support: Ed Casper (S&T Consulting) Manufacturing Manager: Bo Galford Lead Product Manager: Development Services: Elaine Nuerenberg Lead Product Manager: Mary Larson Group Product Manager: Robert Stewart Module 3: MSF Process Model Instructor Notes Module 3: MSF Process Model Presentation: 60 Minutes Activity A: 15 Minutes Activity B: 15 Minutes This module provides students with an introduction to the Microsoft Solutions Framework (MSF) Process Model, including an overview of process models (waterfall and spiral); a discussion of the MSF milestone-driven and phasebased process model; the underlying principles of the MSF model, including living documents, versioned releases, and project tradeoffs, and a synopsis of how the Process Model can be applied to other types of projects, such as enterprise architecture (EA), application development (AD), and infrastructure deployment (ID) At the end of this module, students will be able to: Describe what a phase-based, milestone-driven process model means Describe three principles that underlie the Process Model, including living documents, versioned releases, and managing project variables Describe how the Process Model changes to adapt to each of the following project types: an EA project, an AD project, and an ID project Materials and Preparation This section provides you with the materials and preparation needed to teach this module Materials To teach this module, you need the following materials: Microsoft® PowerPoint® file 1639A_03.ppt Module 3, “MSF Process Model” Flip chart or white board and pens for the activity Preparation To prepare for this module, you should: Read all of the materials for this module Complete the two activities Explore the MSF Web site at http://www.microsoft.com/msf Explore the DNS Web site at http://www.microsoft.com/dns iii iv Module 3: MSF Process Model Instructions for Activity A: Applying the MSF Process Model Description This activity uses the course schedule to demonstrate the Process Model Each module has an estimated amount of time for the presentation and the activity As discussed in module 0: “Introduction,” of course 1639a, Overview of Microsoft Solutions Framework, instructors should write the estimated class schedule on the board where students can see it In this activity, the instructor compares the estimated time for each module and activity to the actual completion time After demonstrating how the Process Model is applied, the instructor then leads the class through the application of the model to the course schedule Demonstrate how the Process Model is applied to any project by identifying the phases, major milestones, interim milestones, or deliverables for the course schedule Have the class identify the following: Phases Describe the phases in the class schedule Major milestones Specify any deliverables and major milestones associated with the course schedule Estimated time to complete this activity: 15 minutes Objectives Following is the learning objective for this activity: • Students will be able to apply the model to the course schedule by identifying course phases, major milestones, interim milestones, or deliverables Setup There are no special setup requirements for this activity Instructions for Activity B: Demonstrating the Impact of Versioned Releases Description The class participates in an activity that demonstrates the advantages of multiple versions of a product The activity is followed by the topic, “Versioned Releases.” In this activity, the instructor has one student volunteer complete a quick activity in front of the class, for example, snapping fingers, whistling, or a some other similar activity Three other students act as judges After the volunteer performs the activity, the judges respond by: Rating the activity on a scale of to 10 Describing what they liked and did not like about the activity Describing what the volunteer must for the judges to give the activity a 10 rating Module 3: MSF Process Model The volunteer incorporates the feedback and repeats the activity The judges rate the activity again The volunteer incorporates the feedback and, for the third and last time, repeats the activity The instructor writes down the ratings and feedback each time that the activity is performed After the volunteer has completed the activity for the third time, the ratings should be closer to 10 Estimated time to complete this activity: 15 minutes Objectives The learning objective for this activity is to: • Illustrate key concepts of version releases, including incremental releases, responding to changes in product scope, and providing critical features in a shorter time frame Setup There are no special setup requirements for this activity v vi Module 3: MSF Process Model Module Strategy Use the following strategy to present this module: Introduction to Process Models This section provides an introduction to process models Topics in this section include: • Process Models This topic introduces the concept of life cycle models and describes the two most popular models—the waterfall model and the spiral model Awareness of these models is important for students, because the Process Model is a combination of these two model types • The MSF Process Model Explains how the Process Model combines elements of the waterfall and spiral models to result in a model that is milestone-driven and phasebased Applying the MSF Process Model This topic takes the MSF Process Model and applies it to an EA project, an AD project, and then an ID project The intention of this section is to show that while the Process Model can be applied to any project, the process itself always remains phase-based and milestone-driven Topics in this section include: • The Phase-based Approach This topic describes the function of phases in the Process Model • The Milestone-driven Process This topic presents the two types of milestones used by the Process Model, major and interim milestones, and examples of the primary function of milestones in the Process Model Underlying Principles of the MSF Process Model This section discusses some of the principles that underlie the Process Model—living documents, versioned releases, and project tradeoffs It is important to emphasize to students that many concepts and principles underlie the Process Model, and that these are just some of them • Project Tradeoffs This topic presents the triangular model that is used to represent the relationship between project resources, schedule, and features • Versioned Releases This topic introduces the concept of versioned releases It is important to emphasize to students that versioned releases are a fundamental product development approach for large projects Some of the advantages of versioned releases are presented • Creating Living Documents Introduces the concepts of baseline early and freeze late and lists the advantages of using living documents Module 3: MSF Process Model vii Background on the Waterfall and Spiral Models The Waterfall Model In this model, each set of tasks must be completed before the next phase can begin The task-driven development life cycle usually results in a waterfall model with the following characteristics: Different teams handle each phase in the life cycle Each phase must be heavily documented to allow the new team to pick up where the old team left off Critical decisions are frozen early Testing only occurs at the end of the project Communication between team members is restricted by the limitations of written documentation The time spent writing and reading is expensive Critical information can be lost or omitted in this process, and the context of many decisions may fail to be communicated Each successive phase of the project places the team further away from the intimate knowledge of the customer’s needs that was gathered early in the project Large or complex projects that follow the waterfall model are also inherently unpredictable with regard to schedule and quality The development team may “go dark” for a long period of time without any true assessment of their progress or the issues that are being created by coding As a result, major bugs only become known toward the end of the project, when they are most costly to fix, and when they have the greatest impact on the release date Finally, the waterfall model tends to focus initially on customer requirements, rather than on a vision of what the available technology can for the user While this may seem trivial, it is important to recognize that the ultimate quality of any solution may depend on functionality that the end user never imagined A high quality solution will be the result of a clear vision of what the technology can matched with a clear understanding of the organization’s business needs A good Process Model will mandate more than the collection of user requirements as articulated by the customer viii Module 3: MSF Process Model The Spiral Model The spiral model was advocated by Barry Boehm and published in 1988.This model focuses on the continual need to refine the requirements and estimates for a project The spiral model can be very effective when used for rapid application development on a very small project This approach produces great synergy between the development team and the customer, because the customers are involved in all stages by providing feedback and signing off However, this model is still somewhat theoretical in nature There is little guidance on how to adapt, plan, or execute a project by using the spiral model Advantages of the spiral model: Iterative process Uses a synergistic approach Active customer participation Enhances creativity Disadvantages of the spiral model: Theoretical, not well supported model No guidelines on when to complete a phase Requires strong project management May lead to “jumping the code” and not enough analysis Module 3: MSF Process Model Overview Slide Objective To provide an overview of the module topics and objectives Lead-in In this module, you are introduced to the Process Model, underlying principles of the Process Model, and how the Process Model can be applied to a variety of project types Introduction to Process Models Applying the MSF Process Model Underlying Principles of the MSF Process Model At the end of this module, you will be able to: Describe the characteristics of the waterfall model, spiral model, and Microsoft Solutions Framework (MSF) Process Model Describe how the Process Model changes to adapt to each of the following project types: an enterprise architecture (EA) project, an application development (AD) project, and an infrastructure deployment (ID) project Describe three principles that underlie the Process Model, including living documents, versioned releases, and managing project variables Module 3: MSF Process Model Introduction to Process Models Slide Objective To introduce the topics presented in this section Lead-in In this section, you will learn about the different types of process models, as well as the elements of the Process Model Process Models The MSF Process Model There are different types of process models in use in business today The MSF Process Model originated from the process used by Microsoft to develop applications and evolved to combine some of the most effective, popular principles of process models into one model that can be applied across any project type—a phase-based and milestone-driven model Module 3: MSF Process Model Process Models Slide Objective To present examples of two popular life cycle models: the waterfall model and the spiral model Lead-in Two popular process models used in business today include the… Waterfall Model Good for complex projects Uses milestones as transition and assessment points Spiral Model Relies on iterations for improvement Does not have clear checkpoints Process models establish the order for project activities In this way, they represent the life cycle of a project Different types of process models are used in industry today The following are two of the more popular models: Waterfall model The waterfall model works well for complex projects as long as you can easily specify requirements at the beginning This model uses milestones as transition and assessment points Spiral model The spiral model sometimes works well because it relies on iterations for creativity and continued improvement But it is chaotic because it has no clear checkpoints Module 3: MSF Process Model The MSF Process Model Slide Objective To show how the MSF Process Model combines milestone-driven, phasebased principles of flexibility and iteration into one model Milestone Milestone ou r e On Ph as eF e as The MSF Process Model provides a structure for any type of project Ph Lead-in Milestone Milestone Milestone Milestone ree Th Ph as eT wo e as Ph Milestone Milestone Key Points Explain that the MSF Process Model illustration is not drawn to scale and so is not representative of the relative amount of time that each phase will take The MSF Process Model combines the best principles of process models, deriving the benefits of predictability from the milestone-based planning of the waterfall model, as well as the benefits of iteration and creativity from the spiral model The Process Model provides a project planning structure that consists of four distinct phases Each phase culminates in an externally visible milestone The naming of each phase, or milestone, depends on the type of project to which the model is applied One advantage of the Process Model is that it can be applied to any type of project Delivery Tip At this point, not explain milestones and phases; these topics are addressed in separate sections later in this module Module 3: MSF Process Model Applying the MSF Process Model Slide Objective To show the relationship between the three project types: enterprise architecture, infrastructure deployment, and application development EA Project EA Project EA Release EA Release Phase ID Project ID Project Phase EA Scope EA Scope Complete Complete EA Vision EA Vision Approved Approved Lead-in The MSF Process Model can be applied to any project Phase Phase EA Plan EA Plan Approved Approved AD Project AD Project The MSF Process Model can be applied to varying project types, including EA projects, AD projects, and ID projects EA projects include business process improvements, infrastructure deployment, business application development, data stores consolidation, business application systems consolidation, platform and infrastructure consolidation, and technology evaluations AD projects are the written code and application programs developed for a project, as well as the testing and troubleshooting, before the applications can be released for use in a production environment ID projects implement technology that has been piloted and stabilized and is ready to be released In any project, the Process Model consists of the following phases: Phase 1: envisioning phase During the envisioning phase, the team and the customer define the business requirements and the overal1 goals of the project All projects have an envisioning stage • The envisioning phase culminates in the vision-approved milestone, which indicates that the team and customer agree on the project direction Phase 2: planning phase All projects have a planning phase, which culminates in a plan-approved milestone • In an EA project, you are also developing the current environment and the desired state during the planning phase 6 Module 3: MSF Process Model Phase 3: developing phase All projects have a developing phase, but the activities are different for each type of project • EA and AD projects culminate in scope-complete milestones In an EA project, this milestone gives key project members the opportunity to identify and address issues before the product ships The scope-complete milestone for an AD project indicates that all features are complete and that the product is ready for external testing and stabilization • An ID project culminates in a release milestone, which indicates that the team has tested and piloted the project and is prepared to perform a deployment Phase 4: stabilizing phase All projects have a stabilizing phase, but the activities are different for each type of project • Activities for EA and AD projects culminate with a release milestone The EA release milestone indicates customer acceptance of the product The AD release milestone indicates that the product is shipped, and the ownership of the product changes from the development team to the operations and support team • The stabilizing phase for an ID project culminates in a deployment complete milestone, which indicates that the deployment plan has been fulfilled Module 3: MSF Process Model The Phase-based Approach Slide Objective To describe the function of the phases in the Process Model Lead-in In the Process Model, phases function as follows… Segmenting Projects into Phases Organize the team Facilitate communication Facilitate deliverable-based milestones Projects can be segmented into logical, high-level activities, which then constitute phases of the project: envisioning, planning, developing, and stabilizing The function of each of the phases in the Process Model is to: Organize the team Phases provide guidance as to what type of activities should be conducted at each point in the project Facilitate communication Phases can be used as a communication tool to convey to external key stakeholders what the project team is currently working on Facilitate deliverable-based milestones Fundamental to each phase is an end that culminates with a deliverable-based milestone indicating the transition from one set of activities to another Module 3: MSF Process Model The Milestone-driven Process Slide Objective To describe milestones Lead-in Milestones that function within the Process Model include the following… Types of Milestones Major—culminates in a deliverable, and transitions between phases Interim—indicates early progress and segments large work efforts into workable pieces Function of Milestones Used as review and synchronization points Used to assess progress and to make mid-course corrections Represents team and customer agreement to proceed Key Points Differentiate between major and interim milestones Major milestones are external variables, for example, a product deliverable Interim milestones are internal team milestones that are used to segment the project, for example, project dates The Process Model uses two types of milestones: major and interim milestones Types of Milestones Major milestones serve to transition from one phase to another and to transition responsibility from one role to another Major milestones are times when all team members synchronize their deliverables Deliverables are physical evidence that the team has reached a milestone Achieving a major milestone represents team and customer agreement to proceed Interim milestones indicate early progress and segment large work efforts into workable pieces Function of Milestones Milestones are used as: Review and synchronization points, not freeze points An opportunity for the team to assess progress and make mid-course corrections A way to represent team and customer agreement to proceed when a milestone is achieved Module 3: MSF Process Model Activity A: Applying the MSF Process Model Slide Objective To introduce the activity Lead-in In this activity, you will apply the MSF Process Model to the course schedule In this activity, the instructor leads the class through the application of the MSF Process Model to the course schedule Instructions for Activity Identify the following: Phases Describe the phases in the class schedule Major milestones Specify any major milestones, interim milestones, or deliverables associated with the course schedule Estimated time to complete this activity: 15 minutes 10 Module 3: MSF Process Model Underlying Principles of the MSF Process Model Re so ur Three principles that underlie the MSF Process Model are project tradeoffs, versioned releases, and living documents le du he Sc Lead-in ce s Slide Objective To present some of the principles of a successful MSF Process Model Features Project Tradeoffs Project Tradeoffs Versioned Releases Versioned Releases Living Documents Living Documents The MSF Process Model relies on many principles, concepts, and practices, including project tradeoffs, versioned releases, and living documents Module 3: MSF Process Model 11 Project Tradeoffs Slide Objective To present the triangular model used to represent project tradeoffs lle du ed he Sc Sc This illustration of project tradeoffs indicates how project variables exist in a triangulated relationship Re so urc es Lead-in Features The variables in any project are resources (people and money), schedule (time), and features (the product and its quality) Those variables exist in a triangulated relationship As the team develops a product, it will inevitably have to make tradeoffs among the project variables The key to project success is finding the right balance among resources, schedule, and features After the team has established the triangle, any change to one of its variables (or sides of the triangle) requires a correction to one of the variables to maintain project balance, including, potentially, the same variable in which the change first occurred A project is successful when the customer believes that the team has made the right tradeoffs, so the team should ask the customer about priorities early and often 12 Module 3: MSF Process Model Activity B: Demonstrating the Impact of Versioned Releases Slide Objective To introduce the activity Lead-in In this activity, you will quickly design and create a product This activity involves class participation The purpose of this activity is to explore the impact of multiple releases of a product Instructions for Activity One student volunteers to complete a quick activity in front of the class Three other students act as judges After the volunteer performs the activity, the judges respond by: Rating the activity on a scale of to 10 Describing what they liked and did not like about the activity Describing what the volunteer must for the judges to give the activity a 10 rating The volunteer incorporates the feedback and repeats the activity The judges rate the activity again The volunteer incorporates the feedback, and for the third and last time, repeats the activity Estimated time to complete this activity: 15 minutes Module 3: MSF Process Model 13 Versioned Releases Slide Objective To illustrate the concept of versioned releases Version Lead-in Version Functionality Versioned releases are an approach to product development Version Time Key Points Versioned releases enable the project team to provide the features that are the most critical for functionality in a shorter time frame This is possible because the team can focus on those features and not become distracted by trying to include every desirable feature in the first release Versioned releases are a fundamental project technique that divides large projects into multiple versioned releases, where the first release deliverers the core product, and later releases add features incrementally until the product matches the project vision By using versioned releases, teams can provide the most critical pieces for a product in a shorter time frame because the team does not need to include every desirable piece in the first release Versioned releases also enable a project team to respond to changes in scope, schedule, and risks during product development Versioned releases are advantageous because they: Force closure on project issues Set clear and motivational goals for all team members Manage the uncertainty and change in project scope Encourage continuous and incremental feature delivery Enable shorter time to delivery or release 14 Module 3: MSF Process Model Creating Living Documents Slide Objective To present the terms baseline early and freeze late Lead-in Two recommendations for creating living documents are baseline early and freeze late Baseline Early Baseline planning efforts begin as early as possible for an earlier development start Freeze Late Consider documents as dynamic and subject to change Delivery Tip Living documents should be subject to version control in the same way that a team uses version control when creating software Functional Specifications Vision Document Project Plans Project Schedule Risk Management Document Living Documents Living Documents Creating living documents enables a team to arrive at a balance between too little and too much planning Teams often question how they can plan just enough, but not too much The answer offered by the creation of livingdocuments is that you should baseline early and freeze late Baseline early To baseline early means that project teams should baseline they’re planning efforts as soon as possible and move on to developing the solution, even if that means leaving some questions unanswered Freeze late To freeze late means that as long as the team considers documents to be dynamic and subject to change, it can add answers and details along the way The advantage of this approach is that it gets teams out of a paralysis that can result from too much analysis Rather than continuing to plan until they have addressed every detail, the project team members can move on as soon as they have addressed enough details to facilitate moving forward Module 3: MSF Process Model 15 Review Slide Objective To reinforce module objectives by reviewing key points Lead-in The review questions cover some of the key concepts taught in the module Delivery Tip In addition to the questions, evaluate whether the module objectives have been achieved If you determine that an objective has not been fulfilled, consider repeating the appropriate content before proceeding to the next module Introduction to Process Models Applying the MSF Process Model Underlying Principles of the MSF Process Model What is a process model? A process model is a model that establishes the order for project activities, from start to project completion What are milestones, and why are they important? Milestones are a technique used to transition from one point of a project into another point of the project Milestones can be used as review and synchronization points, progress assessment points, points for team and customer agreement, or to indicate where project deliverables occur What are living documents, and why are they important? Living documents refer to documents that are dynamic Because living documents are not static, they enable a team to move on to developing the product instead of becoming paralyzed at an early stage in the project while trying to finalize every detail 16 Module 3: MSF Process Model What are versioned releases, and why are they important? Versioned releases are an approach to product development that divides large projects into multiple versioned releases; the first release delivers the core product deliverables, and later releases add features incrementally until the product matches the team’s vision Versioned releases enable a project team to provide the most critical parts of a product in a shorter time frame because the team does not need to include every desirable feature of the product in each release What are the three project variables, and why is their relationship important? The three project variables are resources (people and money), schedule (time), and features (the product and its quality) The relationship of the variables is important because they form the basis for determining project tradeoffs The key to project success is in finding the right balance among the variables  ... types of process models, as well as the elements of the Process Model Process Models The MSF Process Model There are different types of process models in use in business today The MSF Process Model. .. milestone-driven model Module 3: MSF Process Model Process Models Slide Objective To present examples of two popular life cycle models: the waterfall model and the spiral model Lead-in Two popular process models... next module Introduction to Process Models Applying the MSF Process Model Underlying Principles of the MSF Process Model What is a process model? A process model is a model that establishes the