PRINCE2 Agile Practitioner Free Sample Questions

Collaboration is the most effective behavior to foster here. The issue is a systemic one involving the product owner's availability, which is a key stakeholder interface. Actively collaborating with the product owner and their functional manager to agree on dedicated time addresses the root cause of the decision-making bottleneck. While transparency and self-organization are important, they do not resolve the fundamental resource conflict. Exploration is not the primary behavior needed to solve this problem.

In a typical PRINCE2 Agile project with a fixed deadline (Time) and budget (Cost), Scope and Benefits are the primary targets that are flexed. This allows the project to deliver the most valuable features (MoSCoW prioritization) within the fixed constraints, ensuring a viable product is delivered on time and on budget even if not all originally conceived features are included.

A low Agilometer score for communication highlights a significant risk. The most appropriate and pragmatic response is to formally address it in the communication management approach within the PID. Investing in tools that facilitate face-to-face (video) interaction and defining core hours for synchronous collaboration directly mitigates the risk of poor communication in a distributed team. Email stand-ups are a poor substitute for rich communication. Full co-location is often prohibitively expensive and impractical. Simply accepting the risk ignores the Agilometer's purpose.

False. While agile events like sprint reviews and release planning provide vital input and can make the 'Managing a Stage Boundary' process much leaner, they do not completely replace it. The PRINCE2 process ensures governance by requiring the project manager to report stage performance, update the business case and project plan, and create a plan for the next stage for the project board to formally authorize continued work. These governance activities go beyond the scope of typical agile team-level ceremonies.

The 'Focus on Products' principle is about understanding and defining what needs to be delivered, including the quality criteria. In a Scrum context, the Definition of Done (DoD) is the key mechanism for ensuring quality. By incorporating the mandatory government standards into the DoD, the project manager ensures that every product increment delivered by the team meets these essential, non-negotiable quality criteria, thereby correctly applying the principle in an agile way.

This is the most comprehensive and appropriate PRINCE2 Agile approach. It correctly identifies Scope and Benefits as flexible given the fixed Time and Cost. It directly addresses the 'easy to release' risk by creating a work package to improve the deployment process early on. It tackles the 'customer doesn't need everything' risk by instituting a formal, collaborative prioritization process (MoSCoW) through workshops. This strategy proactively manages the identified risks within the project's constraints.

This correctly describes the flow of information in PRINCE2 Agile. The delivery team's progress is captured at a detailed, frequent level (e.g., in Checkpoint Reports or via information radiators). The project manager then synthesizes this information, focusing on progress against stage tolerances and the business case, into a less frequent, higher-level Highlight Report for the project board. This keeps the board informed at the right level of detail.

PRINCE2 Agile guidance clearly suggests that the Team Manager role is the most natural fit for a Scrum Master. The Team Manager is responsible for managing the delivery team and ensuring products are created to the required quality, which aligns well with the Scrum Master's responsibilities of facilitating the Scrum process and removing impediments for the delivery team.

A spike is a specific type of user story or task that is used to gain knowledge or answer a question, thereby reducing technical or functional uncertainty. It is timeboxed and intended to provide just enough information to make a decision. This is the perfect agile technique for quickly investigating the two technology options to determine feasibility.

Kanban is a flow-based system where work is 'pulled' by the team as they have capacity. Therefore, a Work Package for a Kanban team should be framed as a queue of prioritized items that the team can draw from. In contrast, a Work Package for a Scrum team is typically a set of objectives or features to be achieved within a specific timebox (the sprint). The structure reflects the fundamental difference between flow-based and timeboxed agile approaches.