Professional Documents
Culture Documents
Information Technology Project Management Providing Measurable Organizational Value 5th Edition Marchewka Solutions Manual 1
Information Technology Project Management Providing Measurable Organizational Value 5th Edition Marchewka Solutions Manual 1
Teaching Strategies
From my experience, I have seen many projects become challenged as result of the pro-
ject team not properly defining or managing the project’s scope. Being able to define ex-
actly what needs to be done requires a clear direction. Therefore, it is important that the
project stakeholders understand the project’s goal or MOV before trying to define the
work that has to be done. The students should understand that there is an important link
between the project’s MOV and scope.
Scope is really the deliverables that the project team must deliver. This chapter has been
updated in the new edition to include the revised scope management processes in the
third edition of the PMBOK® Guide. In short, the revised scope management process in-
cludes a “create work breakdown structure” process. However, I believe it is important
not to confuse scope with activities. While both may be considered “work,” it is im-
portant that the project team (and students) separate deliverables from activities or tasks.
Project scope, defined in terms of tangible, verifiable products or deliverables, provides a
clearer focus and direction. Moreover, it sets clearer expectations for all the stakeholders
involved. Subsequently, activities or tasks are actions to create the work products. This
can lead to people being busy, but accomplishing little.
The students should understand that we must put a boundary around the project’s scope
much like a fence to keep certain things in and other things out. The project manager
should act as a gatekeeper so that once the project scope is defined only work products
that will help us achieve the MOV (without increasing schedule and budget unneces-
sarily) should be let in. Once again, the concept of the triple constraint should be revis-
ited to highlight the relationships between scope, schedule, and budget. This chapter in-
troduces several tools for defining the project’s scope. Some tools like a context DFD or
use case diagram come from the MIS/Software Engineering bodies of knowledge, while
the deliverable structure chart and table have been adapted or inspired by the work of
Graham McLeod and Derek Smith. Once we have a clear understanding of the work
products we call scope, we can use the WBS introduced in the next chapter to create
work packages that include phases, deliverables, activities or tasks, and milestones. This
WBS becomes the foundation for developing the detailed baseline project plan that yields
the project schedule and budget.
This chapter also introduces a number of approaches and tools for estimating the project
activities. Although there is no perfect estimation tool, having an understanding and
clear definition of the project deliverables can provide a higher degree of confidence in
our estimates. I also like to point out to the students that there are two basic approaches
to project estimation. The first is the traditional project management approach (i.e., time
boxing, top-down, bottom-up, and the Delphi technique), which may be better suited for
estimating project-oriented scope/deliverables. However, the most difficult (and perhaps
the most important) deliverable to estimate is the system solution – especially if a custom
system artifact is to be designed and developed. It is important the students appreciate
the fact that we will not have a clear idea of what this system will even look like until we
are well into the SDLC. However, we need to know enough about the system solution at
this point to develop a realistic and usable project plan. To estimate the product-oriented
deliverable/scope, a software engineering approach may be more useful. The tools for
estimating the schedule and budget associated with the creation and delivery of the sys-
tem may be best suited using such tools as function point analysis, COCOMO, and heu-
ristics (with limited effectiveness using the traditional counting of lines of code).
➢ This chapter introduces the six PMBOK® scope management processes called
scope planning, requirements collection, scope definition, create-work breakdown
structure, scope validation, and scope control. The work breakdown structure pro-
cess is used to create the project schedule in the next chapter.
➢ Scope can be classified or viewed as being product or project scope. Project scope
centers on the deliverables defined in the ITPM. This includes the business case,
project charter, baseline plan, etc. On the other hand, product scope focuses on the
product of the project – in other words, the information system solution. Product
scope concerns the features, functionality, or requirements of the system.
➢ Several tools for defining the project’s scope are introduced. These tools include
the use case diagram and the deliverable structure chart.
➢ Once the project’s scope is defined, it must be verified and controlled against scope
leap and creep. Scope grope is a situation that may arise if the scope was never de-
fined properly in the first place. Subsequently, the project team may try to grope
their way in terms of finding a direction.
➢ The WBS is an important and widely used tool for planning projects. Unfortu-
nately, there is no general standard or accepted WBS style or approach. Since the
WBS must be tied to the project’s scope (and in turn to the project’s MOV), the
WBS should follow a work package approach that breaks up the project into
phases, with each phase tied to one or more deliverables. Moreover, each delivera-
ble should include specific tasks (or activities) that represent actions needed to
complete the deliverable. Examples of the work package concept can be found in
the Husky Air case examples that are part of the instructor’s materials.
➢ Deliverables and milestones are tightly linked. Deliverables are the specific work
products defined in the project’s scope. Milestones represent quality checks to
show that deliverables and phases have not only been completed, but completed
according to predefined standards. Milestones also play other important roles such
as cruxes or proof of concepts, and tend to keep the project team focused because a
project team that hits its milestones should be on track.
The Triple Constraint describes the relationship among scope, schedule, and budget.
The project is balanced or “in harmony” when the schedule and budget support the pro-
ject’s scope in order to achieve the MOV. The project becomes imbalanced when scope
increases without adjusting schedule and budget accordingly.
The term scope is used to define the work boundaries and deliverables of the project so
what needs to get done, gets done—and only what needs to get done, gets done.
• Scope planning: The development of a scope management plan that defines the pro-
ject’s scope and how it will be verified and controlled throughout the project.
• Scope definition: A detailed scope statement that defines what work will and will not be
part of the project and will serve as a basis for all future project decisions.
• Create work breakdown structure: The decomposition or dividing of the major project
deliverables into smaller and more manageable components.
• Scope verification: Confirmation and formal acceptance that the project’s scope is accu-
rate, complete, and supports the project’s MOV.
• Scope change control: Ensures that controls are in place to managed proposed scope
changes once the project’s scope is set. These procedures must be communicated and
understood by all project stakeholders.
Scope planning is a process for defining and documenting the project work. More specifi-
cally, a project’s scope defines all the work, activities, and deliverables that the project
team must provide in order for the project to achieve its MOV. It is an important step in
Another document from Scribd.com that is
random and unrelated content:
A Russian professor, who was interested in political movements merely
as an observer, explained Zinoviev’s curious tenacity in office in this
way: “The Communists,” he said, “insist so strongly upon party
discipline and party loyalty that they have never been able to face the
fact that Zinoviev is not a leader.”
Zinoviev’s appearance is against him. He is short, heavily built, flabby.
Yet he is not devoid of vanity; he is the most photographed man in
Russia. And while he has little imagination, he has real dramatic sense,
he has a way of staging everything.
At Baku, at one moment he had the Easterners unsheathing their swords
and declaring a holy war; at another moment he had a group of
Mohammedan women in the gallery tearing off their veils. All this was
distinctly impressive and dramatic, but the real drawback was that the
effect of the second act almost ruined the effect of the first.
I often wonder if a man can be a great leader, and be utterly devoid of
humor. When Zinoviev says anything clever he is not even aware of it
and invariably spoils it by a second act.
During the Kronstadt uprising the Esthonian government, with its wish
father to its thought, sent a wire to Petrograd which read: “What sort of
government have you in Petrograd?” And Zinoviev replied: “The same
government that has been here since 1917.”
If he could only have stopped at that one sentence he might have been
able to lead a world revolution, or at least catch the imagination of the
workers. Instead he insisted upon being didactic. He wired page after
page, delivering an orthodox Marxian lecture! But the International is
not without men of talent and daring. There are men under Zinoviev—
Italians, Frenchmen, Germans, Bulgarians, Americans, with real fire and
ability.
Bucharin, editor of Pravda, is by far the most brilliant of the Russians.
No matter how much one may disagree with Bucharin, one must concede
his brilliancy. The Letts have an exceptionally able group in the
International. Some of these men were actually in power during the brief
time that Latvia was “red.” The leader of the group is a stately old man
called Stootchka. For four months he was President of Latvia.
PETER STOOTCHKA
Peter Stootchka is one of those advisers and assistants of Lenin that the
world has not yet discovered. He is a man of capacious mind and one of
Lenin’s closest friends. He is a lawyer by profession and for many years
was the editor of a Lettish progressive paper in Riga. He was exiled to
Siberia for some criticism of the Tsar’s government.
He was the first Commissioner of Justice under the Soviets and only
resigned his post to accept one as President of Latvia. When Riga fell he
went back to Moscow, took up quarters near Lenin in the Kremlin, and
there he remains.
It was Stootchka who wrote the Soviet constitution, as well as most of
the present laws. Evidently he did not always find writing laws an easy
task. He often confessed his inability to judge just how the personal and
family life would grow up around the great economic change which had
taken place. Stootchka is nearly seventy and he felt that he might be a
little old-fashioned in regard to some matters, especially concerning
marriage and divorce. In the end he left it for those most concerned to
decide.
One afternoon he called into his office five young Russian women, all
typical revolutionists, and said to them: “For centuries women have been
oppressed, they have been the victims of prejudice, superstition and the
selfish desires of men. In writing the marriage laws I don’t mind if
women have even a slight advantage over men. What I am concerned
with most is to see that they get full justice. So I have asked you here as
representatives of the new order. Think these matters over and give me
your conclusions.”
Naturally, these conclusions had to be voted on by the All-Russian
Congress of Soviets, but since they were passed and written, it is now an
historical fact that five young women are the real authors of the new and
rather free marriage laws.