Give Ad Hoc Direction is a key activity within the Directing a Project Process in PRINCE2 7. This activity enables the Project Board to provide guidance, make decisions, and respond to situations that arise between formal stage boundaries or scheduled reporting periods.
The Project Board members a…Give Ad Hoc Direction is a key activity within the Directing a Project Process in PRINCE2 7. This activity enables the Project Board to provide guidance, make decisions, and respond to situations that arise between formal stage boundaries or scheduled reporting periods.
The Project Board members are typically senior executives with other responsibilities, so they cannot be involved in day-to-day project management. However, projects rarely progress exactly as planned, and situations emerge that require board-level input or decisions. Give Ad Hoc Direction addresses this need by establishing a mechanism for ongoing governance throughout the project lifecycle.
This activity covers several important functions. First, it allows the Project Board to respond to exception reports when the project manager identifies that tolerances may be exceeded. The board can then decide whether to approve an exception plan, request changes, or take other corrective action.
Second, the board provides informal advice and guidance when the project manager needs clarification on strategic matters, stakeholder concerns, or organizational priorities. This ensures alignment between the project and broader business objectives.
Third, Give Ad Hoc Direction enables the board to make decisions on escalated issues or risks that fall outside the project manager's authority. This maintains appropriate governance while keeping the project moving forward.
Fourth, the board can respond to external changes affecting the project, such as shifts in business strategy, market conditions, or regulatory requirements.
The activity emphasizes management by exception, meaning the board intervenes only when necessary rather than micromanaging. This approach respects both the project manager's authority and the board members' limited availability.
Effective ad hoc direction requires clear communication channels between the project manager and board members, well-defined escalation procedures, and mutual understanding of decision-making authorities. This ensures timely responses to emerging situations while maintaining proper project governance.
Give Ad Hoc Direction - PRINCE2 Foundation V7 Complete Guide
Introduction to Give Ad Hoc Direction
Give Ad Hoc Direction is a critical activity within the Directing a Project process in PRINCE2. It represents the ongoing responsibility of the Project Board to provide guidance, make decisions, and respond to situations that arise between formal decision points throughout the project lifecycle.
Why Give Ad Hoc Direction is Important
This activity is essential because projects rarely proceed exactly as planned. The Project Board must remain engaged and accessible to:
• Provide timely responses to requests for advice from the Project Manager • Make decisions that fall outside the Project Manager's delegated authority • React to external events or changes that impact the project • Ensure the project continues to align with corporate, programme, or customer strategies • Maintain momentum by preventing delays caused by waiting for scheduled board meetings • Support the Project Manager in navigating complex stakeholder situations
What Give Ad Hoc Direction Actually Is
Give Ad Hoc Direction encompasses all informal communications and decisions made by the Project Board outside of the formal stage boundary assessments. This includes:
• Responding to exception reports - When tolerances are forecast to be exceeded • Providing advice - Guidance requested by the Project Manager • Making off-cycle decisions - Approvals needed between formal reviews • Reacting to external influences - Corporate changes, market shifts, or regulatory updates • Communicating with stakeholders - Representing the project at senior levels
How Give Ad Hoc Direction Works
The process operates continuously from project initiation through to closure:
1. Triggers for Ad Hoc Direction: • Exception reports from the Project Manager • Requests for advice or decisions • External events affecting the project • Issues escalated beyond the Project Manager's authority • Changes to corporate strategy or priorities
2. Project Board Responses: • Provide requested advice or guidance • Make decisions on escalated issues • Approve or reject exception plans • Premature closure authorization if required • Update project tolerances or constraints
3. Communication Methods: • Can be conducted through meetings, emails, or other agreed channels • Does not require formal Project Board meetings for every decision • Individual board members may respond within their areas of responsibility
Key Principles of Give Ad Hoc Direction
• Management by Exception - The Board only intervenes when tolerances are threatened or specific decisions are required • Continued Business Justification - All direction should consider whether the Business Case remains valid • Defined Roles and Responsibilities - Board members respond according to their specific roles (Executive, Senior User, Senior Supplier) • Timely Response - Delays in providing direction can cause project delays and increased costs
Exam Tips: Answering Questions on Give Ad Hoc Direction
Tip 1: Understand the Timing Remember that Give Ad Hoc Direction occurs throughout the project, not just at stage boundaries. Questions may test whether you know when this activity is appropriate versus formal authorization points.
Tip 2: Know the Triggers Be familiar with what prompts ad hoc direction - particularly exception reports, requests for advice, and external influences. Exam questions often present scenarios where you must identify the correct trigger.
Tip 3: Recognize the Participants The Project Board provides ad hoc direction, and the Project Manager receives it. Questions may try to confuse you about who has authority to give direction.
Tip 4: Link to Management by Exception Many questions connect ad hoc direction to the management by exception principle. Understand that the Board delegates authority through tolerances and only gets involved when those tolerances are threatened.
Tip 5: Exception Plan Scenarios A common exam scenario involves the Project Manager producing an exception report and the Board responding with direction. Know that the Board can request an exception plan, give the Project Manager advice, or even authorize premature closure.
Tip 6: Distinguish from Authorize Activities Do not confuse Give Ad Hoc Direction with formal authorization activities like authorizing a stage or project. Ad hoc direction is informal and responsive, while authorization is planned and structured.
Tip 7: Remember the Business Case When providing ad hoc direction, the Project Board should always consider the impact on the Business Case. Questions may test whether you understand this ongoing responsibility.
Common Exam Question Types
• Scenario-based: Given a situation, identify what type of ad hoc direction is needed • Role identification: Who provides or receives ad hoc direction • Trigger recognition: What circumstances require ad hoc direction • Process placement: Understanding that this sits within Directing a Project • Principle connection: Linking ad hoc direction to PRINCE2 principles