"Scope management is the process of defining what work is required and then making sure all of that work - and only that work - is done." defines PMP Exam Prep. The difference between product scope and project scope is that the project scope is the work the project will do to deliver the product of the project. The product scope defines the requirements of the product and what end result is wanted. While taking the exam, Rita Mulcahy suggests remembering to be assertive and not allow unnecessary work to attach to the project. You should be in the mindset of properly protecting the project.
Review historical records, perform "expert interviews", create focus groups, brainstorm, use a nominal group technique, as well as a Delphi technique, mind maps, affinity diagrams, questionnaires and surveys, observation, group decision-making to help collect requirements. A nominal goup technique is when the most useful ideas generated during brainstorming are rated. Rita describes Delphi as follows, "With the Delphi technique, a request for information is sent to experts who participate anonymously, their responses are compiled, and he results are sent back to them for further review until consensus is reached."
PMP Exam Prep provides a list of ways to remember work breakdown structure (WBS):
- Is a graphical picture of the hierarchy of the project.
- Identifies all the deliverables to be completed - If it is not in the WBS, it is not part of the project.
- Is the foundation upon which the project is built.
- Is very important.
- Should exist for every project.
- Forces you to think through all aspects of the project.
- Can be reused for other projects.
- Does NOT show dependencies.
No comments:
Post a Comment