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

Contents Overview 1 Introduction to Process Models 2 Applying the MSF Process Model 5 Underlying Principles of the MSF Review 15 Module 3: MSF Process Model... Instructor Notes Modu

Contents

Overview 1

Introduction to Process Models 2

Applying the MSF Process Model 5

Underlying Principles of the MSF

Review 15

Module 3: MSF Process Model

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

Instructor Notes Module 3: MSF Process Model

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 phase-based 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

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 1 to 10

Describing what they liked and did not like about the activity

Describing what the volunteer must do 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

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

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 phase-based

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

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 do 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 do 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

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

Overview

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

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

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

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

Waterfall Model

Spiral Model

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

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…

The MSF Process Model

Milestone

Milestone

Milestone Milestone

Pha

se O ne

Phas

e Four

Ph ase Th

wo

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

Slide Objective

To show how the MSF

Process Model combines

milestone-driven,

phase-based principles of flexibility

and iteration into one model

Lead-in

The MSF Process Model

provides a structure for any

type of project

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

Delivery Tip

At this point, do not explain

milestones and phases;

these topics are addressed

in separate sections later in

this module