Scope Baseline

Correct Answer: Submit a change request for the new component

In Project Management, when a stakeholder requests to add a new component that was not initially considered, the best practice is to 'Submit a change request for the new component'. This is because any changes to the scope of the project should be documented and assessed for its impact on the project's schedule, cost, and resources. On the other hand, 'Include the new component without reviewing the impact' is not a good practice because it could potentially derail a project. Adding a new component could lead to escalated costs, delays or impact the quality, which is why it's important to assess the impact beforehand. 'Deny the request as it was not part of the initial scope' can also not be considered as a best practice. Even though it's important to stick with the initial plan, the purpose of project management is also to be flexible and adaptive to changes to some extent. The fourth answer 'Ask the stakeholder to fund the additional component' can work in certain scenarios, but it's not the immediate step of action. First, a change request should be submitted, then you can negotiate on the funding and responsibility depending on the analysis of the impact.

Correct Answer: Project scope statement

The correct answer is 'Project scope statement'. The Project Scope Statement defines the project's deliverables and the work required to create those deliverables. It thoroughly describes the project's outcome and aligns with the project sponsor's expectations. On the other hand, the 'Work breakdown structure' break downs the project into smaller, manageable sections, but it doesn't necessarily contain the desired outcome. The 'WBS dictionary' provides detailed information about each component in the WBS, but it also doesn't detail the desired outcome. Lastly, the 'Project management plan' outlines the strategy for managing the project, but it doesn't capture the project's specific scope or desired outcome.

Correct Answer: WBS dictionary

The 'WBS dictionary' is the best answer. The WBS dictionary provides detailed information about each task or deliverable mentioned in the Work Breakdown Structure (WBS). It adds more specifics which might include task duration, resources required, who's responsible for completion, etc. This makes it the most comprehensive information source for tasks included in the WBS. The 'Project scope statement' is not the best answer because it doesn't provide detailed task information. It mainly defines what is and what is not part of the project's scope. The 'Project schedule' does contain information about tasks but not in a detailed manner like the WBS dictionary; it focuses more on the timing aspect. The 'Activity list' is also incorrect because it simply lists out the activities without providing as much detailed information like the WBS dictionary.