Académique Documents
Professionnel Documents
Culture Documents
Page |1
PMBOK
PrepBook
5.1
5.2
Collect Requirements
5.3
Define Scope
5.4
Create WBS
5.5
Validate Scope
5.6
Control Scope
In this Workbook
Read the article: Student Tips for Building a WBS written by Kay Wais, PMP from
www.successfulprojects.com in this workbook.
Take a look at the PMP Sample Test Questions from PMI . This is a (very) small collection of
PMP Exam sample questions that PMI has officially published.
Take a look at the CAPM Sample Test Questions from PMI . This is an (extremely) small
collection of CAPM sample questions that the PMI has officially published. CAPM questions
are much easier than PMP questions; however you may come across one or two like this on your
PMP certification exam.
Listening
Listen to Episode 55 of The PMO Podcast with Mark Perry: Recommendations for Informal
Projects Part I-The Simple WBS and learn more about the Work Breakdown Structure (WBS).
o
Page |2
Listen to Episode 09 of The Controlling Chaos Podcast with Dina Henry Scott, PMP and Lee
Scott, PMP: Work Breakdown Structures and learn about the importance of the WBS in project
scope.
o
Viewing
Watch complimentary PM PrepCast L00.32 Finding the Best Answer to Sample Questions.
o
Go Beyond!
An outstanding way to network and to be exposed to industry trends. Your chapter may offer
discounts on PMP Exam workshops.
Find a study-buddy.
o
Attend your local PMI Chapter dinner meeting. Ask the people at the registration desk to
direct you to the person who can put you in touch with other attendees studying for the exam.
Be sure the others are as dedicated as you. Study time is a precious commodity and
you dont want to waste it.
My Additional Actions
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
Page |3
Question Number
My Answer
Correct
Incorrect
Question 01
Question 02
Question 03
Question 04
Question 05
Question 06
Question 07
Question 08
Question 09
Question 10
Question 11
Question 12
Question 13
Question 14
Question 15
Total Number
% Correct
_____%
To calculate the % correct, divide the total correct by 0.15. Example: If you have 13 correct then calculate 13 / 0.15 = 86.6%
Page |4
Page |5
Correct Answer
Question 01
Question 02
Question 03
Question 04
Question 05
Question 06
Question 07
Question 08
Question 09
Question 10
Question 11
Question 12
Question 13
Question 14
Question 15
Page |6
Page |7
Question 3: For unknown reasons, your manager has suddenly become a negative stakeholder on
your project. He is now asking you to incorporate multiple changes into the project scope.
Although you have the ultimate authority over the project and you have managed to avoid such
requests, some requests look reasonable to you. Which of the following documents can help you
identify which changes require a change request?
A.) Scope Management Plan
B.) Configuration Management Plan
C.) Schedule Management Plan
D.) Quality Management Plan
Correct answer is B
Explanation: The Scope Management Plan outlines how the overall project scope will be defined,
managed and controlled. However, it does not document which changes require a change request
and which do not. Actually, that depends upon the situation. If any change impacts one or more
project baselines, a change request should be created. Otherwise, minor changes do not require
change requests. The Configuration Management plan defines those items that are configurable,
those items that require formal change control, and the process for controlling such items.
Reference: PMBOK Guide 5th Edition, pages 138
Page |8
Student Tips for Building a WBS that will both help your
project and earn a good grade on a WBS assignment
by Kay Wais, PMP.
Successful Projects, LLC, www.successfulprojects.com
Structure is not a statement. The work breakdown structure is often confused with scope statement.
Both come early in a projects life cycle. WBS is an outline of work to be done.
Exclude the Distractions and Details. A well-crafted WBS includes all of the work needed to complete
the project and purposefully excludes all the anticipated, but unnecessary, diversions and distractions that
would slow it down. Dont include technical specifications or work instructions inside the WBS. Dont try to
write the WBS using full sentences.
Know the two key terms. There are summary tasks and work packages in a WBS. Summary tasks are
just there for organizational purposes. The work packages are where the actual work resides. Work
packages get estimated and delegated. Summary tasks do NOT get estimated and delegated.
Beware the stand-alone work package. A summary task with just one work package under it is a huge
red flag that your WBS work is incomplete.
Think deliverables. A WBS specifies the major and subordinate deliverables so it is best to write it in
terms of nouns as opposed to actions. Remember that approvals are a deliverable.
Decompose to the level of delegation and to where you can accurately estimate. Make sure that
each WBS element has someone who is clearly accountable for its completion. Decompose that
deliverable to the point where the time and cost can be accurately estimated.
Bigger projects demand longer legs. WBS levels increase when a project is large, complex and timeconsuming. These increasingly more detailed levels are often referred to as long legs. Deliverables are
pushed further into the future on long-legged projects.
A good WBS helps prevent project delay or failure. Omitting WBS development and proceeding
directly to a Gantt chart or other network diagram may unnecessarily delay the project. Creating a WBS
that is not deliverables-focused may lead to project failure.
Practice the art of progressive elaboration. Increase the legs of a WBS until a level is reached that
provides the needed insight for effective project management. At that finite end point, one person is
responsible for one independent element, and there are clear, objective criteria for measuring the
elements progress and completion.
Plan to Use your WBS. For the assignment you probably do not have to track the percent that all of the
work is done, but the WBS is where you would plan to do this tracking. You may want to build in a method
for this at the start. If youre using project management software, that is done for you. However if you are
using something like Word or Excel, it might be helpful to add a columns such as assigned and %
complete immediately to help you prepare for that.
Page |9
Focus Groups
Focus groups are guided by a trained moderator. Prequalified stakeholders and subject matter experts
are gathered and then channeled by the moderator to learn about their expectations and attitudes about
the proposed product, service, or result. This is achieved through an interactive discussion. Compared to
interviews, focus groups are designed to be more spontaneous.
Facilitated Workshops
Facilitated workshops are meetings that bring together a group of individuals who are best qualified to
identify and discuss product and project requirements. Some key benefits of these workshops are that
they bring diverse often cross-functional representatives together so a big picture view and impact are
captured, potential issues identified early and resolved quickly, stakeholder differences are reconciled in a
well-controlled environment, and trust and important relationships are fostered between participants,
which can lead to improved communication and consensus building. An example of a facilitated workshop
is a JAD or Joint Application and Design/Development session. These are typically called and facilitated
by business analysts and include key stakeholders, subject matter experts, and the development team. In
this way the design and development team can much better understand the context and subtleties of
each requirement. As a result the development team is much more effective and the number of
development cycles can be dramatically decreased.
P a g e | 10
e. Affinity Diagram: An affinity diagram is useful for creating a cause and effect diagram whereby
ideas are collected, sorted, and related ideas grouped together. This process is repeated until all
the ideas are grouped and/or sub-grouped, which helps with management of the ideas.
Observations
Observations offer a direct way of viewing the individual, their environment, how their jobs or tasks are
performed, and the process they follow. This is particularly effective on cases where the detailed process
is difficult to articulate or when the people are reluctant to explain their requirements. Another term that
refers to observation, job shadowing may be done with the observer viewing the user on the job.
Observation may also be accomplished through the use of a participant observer who performs the
process or procedure in order to experience how it is done, which helps uncover hidden requirements or
factors not initially noticed through observation.
Prototypes
Prototypes, or models, are built before the actual product in order to obtain feedback on requirements
sooner. Because the prototypes are tangible, this model allows the stakeholders to experiment and see
possible outcomes rather than just discussing abstract representations or assuming their requirements.
The concept of progressive elaboration is supported by prototyping because it is used on mock up
creation, user experimentation, feedback generation, and prototype revision. All these feedback cycles
formulated from experiments are designed to eventually be sufficient to complete or design the final
output.
Benchmarking
Benchmarking is primarily a compare and contrast activity between different organizations that may have
a bearing on the project. Most often actual and planned practices such as processes or operations are
compared with the goal of: establishing best practices, work toward continuous improvement of existing
practices, as well as deriving a basis for measuring the performance of the requirements gathering
process.
Context Diagrams
Context diagrams take advantage of the power of representing a system or product graphically. The
Context Diagram shows the system under consideration as a single high-level process and then shows
the relationship that the system has with other external entities (systems, organizational groups, external
data stores, etc.).
Document Analysis
Document Analysis is a practice that can help elicit requirements and identify information relevant to the
requirements. It describes the act of reviewing the existing documentation often of comparable business
processes or systems in order to extract pieces of information that are relevant to the current project, and
therefore should be considered as project requirements. Some more common documents that are
analyzed are business process models, use cases, requirements specifications, and RFPs. Existing
P a g e | 11
documentation can be scoured for an understanding of key functions, business rules, business entities,
and business entity attributes. Document analysis may also be necessary when stakeholders are not
available to offer insight into existing business processes or systems.
P a g e | 12
P a g e | 13
Date
2014-04-30
Comments
Original
P a g e | 14