The project manager should review the WBS dictionary, as this is a document that provides detailed information about each element in the work breakdown structure (WBS). The WBS is a hierarchical decomposition of the project scope into smaller and manageable components, called work packages. The WBS dictionary is a complementary document that describes the scope, deliverables, activities, resources, costs, risks, and quality requirements of each work package. The WBS dictionary helps the project manager and the project team to understand the work that needs to be done, and to avoid scope creep or ambiguity1. By reviewing the WBS dictionary, the project manager can identify what useful information is missing, and update it accordingly.
The other options, the project charter and scope statement, the requirements traceability matrix, and the business requirement documents (BRD), are not the best documents to review in this situation. The project charter and scope statement are high-level documents that define the project purpose, objectives, scope, deliverables, assumptions, constraints, and stakeholders. They do not provide detailed information about the work packages or the work breakdown structure2. The requirements traceability matrix is a document that links the project requirements to the project objectives, deliverables, and test cases. It helps to ensure that the project meets the stakeholder expectations and the business needs. It does not provide detailed information about the work packages or the work breakdown structure3. The business requirement documents (BRD) are documents that describe the business problem, the solution, and the benefits of the project. They do not provide detailed information about the work packages or the work breakdown structure4.
1 A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 5.4.2.3 2 A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 4.1.3.1 and 5.3.3.1 3 Business Analysis for Practitioners: A Practice Guide, Chapter 4.3.4 4 Business Analysis for Practitioners: A Practice Guide, Chapter 2.2.2
Submit