Module 3: MSF Process Model v
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.
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 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.
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 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.
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 1
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.
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.
2 Module 3: MSF Process Model
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.
Module 3: MSF Process Model 3
Process Models
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.
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…
4 Module 3: MSF Process Model
The MSF Process Model
Milestone
Milestone
Milestone
Milestone
Milestone
Milestone
Milestone
Milestone
P
h
a
s
e
O
n
e
P
h
a
s
e
F
o
u
r
P
h
a
s
e
T
h
r
e
e
P
h
a
s
e
T
w
o
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.
Module 3: MSF Process Model 5
Applying the MSF Process Model
EA Scope
Complete
EA Scope
Complete
EA Plan
Approved
EA Plan
Approved
EA Vision
Approved
EA Vision
Approved
EA Release
EA Release
ID Project
ID Project
AD Project
AD Project
EA Project
EA Project
Phase 1
Phase 2
Phase 3
Phase 4
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.
Slide Objective
To show the relationship
between the three project
types: enterprise
architecture, infrastructure
deployment, and application
development.
Lead-in
The MSF Process Model
can be applied to any
project.
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.
Không có nhận xét nào:
Đăng nhận xét