#1: What document sets initial boundaries for the project scope?
A. Project scope statement
B. Requirement traceability matrix
C. Project charter
D. Work breakdown structure
Correct Answer: C
Explanation: At the start of a project, a PM should create and get a sign-off on the project charter. The charter contains the high-level scope and stakeholder requirements as known at that moment. Therefore, this document sets the initial boundaries for the project scope. Learn more about the project charter.
Scope Management Plan Template
(For Software Projects)
Most software project managers don’t know what goes into a Scope Management Plan. So, they simply don’t write it out. Unfortunately, this often leads to problems.
Get my template and use it as a starting point. In addition, you get access to all related scope management resources I have.
This template will eliminate the guesswork for you. With minor adjustments, you’ll be proud to present your scope management plan to the team and stakeholders.GET THE TEMPLATE
#2: The requirements traceability matrix helps a project manager to do the following:
A. Connect requirements to other aspects of the project.
B. Triage requirements.
C. Identify and resolve conflicts in requirements.
D. All of the above.
Correct Answer: D
Explanation: The main benefit of the requirements traceability matrix is the connection of requirements to other project artifacts, for example, with business needs, test cases, WBS elements, etc. You can gain all the other benefits by including the required information in RTM. Learn more about the Requirements Traceability Matrix.
#3: On Friday evening, Delana (the project owner) dragged you to a Zoom meeting. She asked to include an additional feature that has unclear relation to the project objectives. What project documents may help you make an argument against adding the new scope of work in the middle of a project?
A. Project charter and project scope statement
B. Work breakdown structure
C. Contract and risk register
D. Resources management plan
Correct Answer: A
Explanation: The project charter may contain a business case, business justification, and project objectives. The project scope statement describes all the main deliverables of the project. Ideally, project owners should have signed off on the scope statement. At the very least, you can make a trade-off based on previous agreements.
#4: What project management techniques may help you identify requirements?
A. Delphi technique
B. Bottom-up estimation
C. Decomposition
D. Critical chain method
Correct Answer: A
Explanation: Delphi technique is the only one that can help with requirements identification. It’s a powerful technique that allows for collecting unbiased opinions from subject matter experts when they cannot reach a consensus. Watch a video about Delphi Technique.
#5: Decomposition is a technique that helps you to break down a project into smaller, more manageable pieces of work. Whom should you include in scope decomposition sessions:
A. HR managers
B. People who will perform the work
C. CEO of the company
D. Customers
Correct Answer: B
Explanation: You should always include people who will perform the work. Even if you did project decomposition before you acquired the project team, you should verify the decomposition results with the team members who will implement the scope.
Learn how to decompose a project into tasks form this example.
#6: A tool that helps you to decompose the project into smaller, more manageable pieces is called:
A. Requirements Traceability Matrix
B. Statement of work (SOW)
C. Contract
D. Work Breakdown Structure
Correct Answer: D
Explanation: Work Breakdown Structure helps you to decompose project scope into deliverables and work packages. These are tangible and verifiable pieces of the project.
Work breakdown structure is a cornerstone tool in project management. You must know key concepts of a WBS.
#7: Imagine that in the middle of the project, your team member comes to you and informs you that he forgot to include tasks required to prepare documentation for API you need to create. He will need about four hours. Suddenly, you realize that you have 14 such APIs to document. How do we call such a scenario:
A. Scope bloat
B. Scope creep
C. Requirements bloat
D. Requirements creep
Correct Answer: B
Explanation: Whenever you need to perform more work to finish a deliverable, it’s called scope creep. That’s a critical concept a project manager must learn to control. Learn how to control project scope here.
#8: At the end of the project, you hand off all eight deliverables to the customer. The customer returned to you in a few days with numerous small change requests and defects for each deliverable. What should you have done to avoid such a situation?
A. Plan scope verification and acceptance processes for each deliverable.
B. Write a detailed contract that prevents changes at the end of the project.
C. Communicate that changes are not a part of this project.
D. Create a quality assurance plan
Correct Answer: A
Explanation: A project manager should continuously control the project scope’s implementation. You should ensure that the project team creates deliverables in accordance with the customer’s expectations. Ideally, you need to get acceptance of each deliverable as soon as they are ready and tested. It will allow you to get feedback when you still have reserves of time and resources.
#9: Who is responsible for the requirements identification process?
A. Business Analyst
B. Project Team
C. Project Manager
D. Customers
Correct Answer: C
Explanation: The project manager is responsible for all aspects of the project. A business analyst and project team may help you execute requirements identification. Nevertheless, you are responsible for organizing, planning, and facilitating all required activities. Therefore, you need to understand how scope management works as a whole.
#10: Which of the following is a piece of requirements documentation?
A. User Story
B. System specification
C. Service Level Agreement
D. All of the above
Correct Answer: D
Explanation: A, B, and C may contain requirements for the product or service you need to create. Therefore, these are all different forms of requirements for documentation. Here are two great articles on how to collect requirements:
- How to Collect Requirements (as a Project Manager)
- Requirements Gathering Example (Real Software Project)
Get Scope Management Plan Template
Unfortunately, this article was just one piece of a complex project scope management framework: Many other processes happen before and after this one.
If one part doesn’t work, the whole system breaks.
My Scope Management Plan Template connects all processes and tools into one cohesive system. It also provides access to other articles and videos on scope management.
Don’t put your projects and reputation at risk. Ensure you know how scope management works in the real world.
All successful project managers know it’s better to learn from someone else’s experience (aka lessons learned). Tap into my 12 years of practical IT experience and get the Scope Management Plan Template.