CompTIA PK0-005 Practice Test

Explanation:
The project manager and team should review assumptions and constraints for input to the risk register during the planning phase of a project. Assumptions are statements that are considered to be true for the purpose of planning, but may or may not be valid in reality. Constraints are factors that limit the project scope, time, cost, quality, or resources. Both assumptions and constraints can introduce risks to the project, which are uncertain events or conditions that can have a positive or negative impact on the project objectives. The risk register is a document that records the identified risks, their causes, impacts, probabilities, responses, owners, and status. Reviewing assumptions and constraints can help the project manager and team identify, analyze, prioritize, and plan for the potential risks that may affect the project12.
The other options are not the correct activities that the team should do during the planning phase of a project. Identifying and assessing stakeholders (option A) is an activity that is done during the initiating phase of a project, not the planning phase. Stakeholders are individuals or groups that have an interest or influence in the project, and their identification and assessment is important to define the project scope, objectives, and success criteria, and to establish a communication plan12. Holding daily status meetings (option B) is an activity that is done during the executing and monitoring and controlling phases of a project, not the planning phase. Daily status meetings are short and frequent meetings where the project team members report on their progress, issues, and plans for the next day. Daily status meetings can help the project manager track the project performance, resolve problems, and communicate updates12. Removing access and planning the project sign-off (option C) is an activity that is done during the closing phase of a project, not the planning phase. Removing access is a security measure to ensure that the project resources do not have access to the project systems, data, or assets after the project is completed. Planning the project sign-off is a process to obtain the formal acceptance and approval of the project deliverables from the stakeholders and customers12.

Explanation: A business case documents the rationale and expected benefits of a project. This document is essential for project approval and aligns with CompTIA Project+ guidance on project initiation and planning.

Explanation: Documenting artifacts is the main reason for creating and maintaining project documents that relate to the management of the project, not the project deliverables. Artifacts are used to define, support, and align the project work to the project requirements and business goals. They also serve as a source of information and evidence for future projects, audits, reviews, and lessons learned1. Documenting artifacts helps to capture the project’s history, performance, outcomes, and best practices, which can be useful for organizational learning and improvement2.

Explanation: A gantt chart is a visual representation of a project timeline that shows the tasks, durations, dependencies, and resources of a project in a horizontal bar chart format. A gantt chart can help a project manager to plan, monitor, and control the project progress, scope, and quality. A gantt chart is different from a milestone chart, which only shows the key events or deliverables of a project without the details of the tasks. A gantt chart is also different from a PERT chart, which is a network diagram that shows the logical relationships and sequence of tasks in a project. A gantt chart is also different from a WBS, which is a hierarchical breakdown of the project scope into smaller and manageable components.

Explanation: The rules of engagement are the guidelines and expectations that define the relationship between the contractor and the company. They may include topics such as communication, confidentiality, access, security, performance, and compliance. The project manager should reinforce the rules of engagement with the contractor to ensure that they understand and respect the boundaries and protocols of the company. This will help to avoid any potential conflicts, misunderstandings, or breaches of contract. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 7: Project Stakeholder Management, p. 239; Contractor Rules of Engagement - Cox Enterprises, p. 1; Legal Considerations for Engaging Contractors | LegalVision

Explanation: Regression testing is a type of testing that is done on an existing system to ensure that the previous functionality still works after a change has been made. Regression testing is a process of retesting or verifying that a software system or application still performs as expected after it has been modified or updated with new features, bug fixes, patches, etc. Regression testing can help to detect any errors or defects that may have been introduced by the change and ensure that no functionality has been broken or degraded.