PK0-005 — Frequently Asked Questions

The most appropriate technique is observation. This method involves watching individuals perform their tasks in their actual work environment. It is particularly useful for understanding the context of work, identifying unspoken requirements, and uncovering process inefficiencies that stakeholders might not mention in an interview or survey. It provides a more objective view of the current state.

A project manager should use the team's average velocity (the average number of story points completed per sprint) to forecast the project's completion. By dividing the total remaining story points in the project backlog by the average velocity, the manager can estimate the number of sprints required to complete the work. This provides a data-driven forecast for the project's end date.

This is best classified as a spear phishing attack, specifically a type known as 'whaling'. Spear phishing is a targeted phishing attack against a specific individual or organization. 'Whaling' is a form of spear phishing that targets high-profile executives like a CEO or CFO. The goal is to trick the recipient into performing an action, such as transferring funds or revealing sensitive information.

The project scope statement is the document that defines the product success criteria. It includes a detailed description of the project's deliverables and the work required to create them. Crucially, it also contains the acceptance criteria, which are the conditions that must be met for deliverables to be accepted by the stakeholders, thereby defining what constitutes a successful product.

The best course of action is to reschedule the meeting to a time when all key stakeholders can attend. The kickoff meeting is a critical event for aligning everyone on the project's goals, scope, roles, and communication plan. The absence of key stakeholders can lead to misunderstandings and a lack of buy-in, so it is essential to ensure their participation, even if it means delaying the meeting.

The project manager should first document the new legislation as a project risk or issue and then initiate the formal change control process. This involves submitting a change request to detail the impact of the new law on the project's budget, schedule, and scope. The change control board (CCB) will then review the request and decide whether to approve the necessary budget increase.

A Request for Quotation (RFQ) is the most appropriate document. An RFQ is used when the project requirements are well-defined and standardized. Its primary purpose is to compare prices and commercial terms from different vendors for a specific product or service, making it ideal for procuring commodities like cabling services where the main differentiator is often cost.

The project manager should first use an issue log. The issue log is a fundamental project document used to record, monitor, and manage all issues that arise during the project lifecycle, including bugs found during testing. It ensures that each issue is tracked, assigned to an owner, and resolved in a timely manner, providing a central record of all project problems.

This represents the 'exploit' risk response strategy. Exploiting is a strategy for positive risks (opportunities). It involves taking specific actions to ensure that the opportunity definitely happens. By leveraging the existing API, the team is actively capitalizing on an opportunity to add value or a new feature to their project, rather than just hoping for it.

Extreme Programming (XP) is often considered the most suitable methodology for this scenario. XP is designed for small, co-located teams and excels in environments with volatile or rapidly changing requirements. Its core practices, such as pair programming, test-driven development (TDD), and continuous integration, provide the discipline and flexibility needed for a small team to adapt quickly and maintain high code quality.

The project manager should immediately add the new stakeholder to the stakeholder register, documenting their name, role, contact information, and key details. Following this, the manager must assess and record the stakeholder's level of interest, influence, and potential impact on the project. Finally, the stakeholder engagement plan should be updated to define the strategy for communicating with and managing this new stakeholder.

A Gantt chart is the best tool for this purpose. A Gantt chart provides a visual timeline of the project schedule, showing the start and end dates of all tasks. This visual representation makes it easy to identify tasks that are scheduled to occur at the same time (overlapping tasks), allowing the project manager to see where resources might be over-allocated and make adjustments to balance the workload.

An example of an operational security control is the enforcement of a clean desk policy. Operational controls are the day-to-day procedures and mechanisms put in place to protect the project and its assets. A clean desk policy, which requires employees to secure sensitive documents and lock their computers when away from their desks, is a procedural control that mitigates the risk of unauthorized access to information.

Personally Identifiable Information (PII) is any data that can be used to identify a specific individual. Common examples that a project manager must protect include a person's full name, home address, email address, social security number (or national ID), passport number, and driver's license number. Protecting PII is a critical aspect of project security and privacy compliance.

The critical path is identified as the longest sequence of dependent tasks from the project's start to its finish. It represents the shortest possible time in which the project can be completed. To find it, you map out all possible paths through the network diagram and calculate the total duration for each. The path with the longest total duration is the critical path. Any delay to a task on this path will directly delay the entire project.