'Resource allocation syndrome' describes a common dysfunction in multi-project environments where an organization has too many active projects relative to its available resources. The root cause is this fundamental imbalance, which forces key resources to be spread thinly across multiple projects. This leads to constant multitasking, priority shifts, and delays as projects compete for the same limited pool of people, equipment, or facilities. Consequently, no single project receives the focused attention required for efficient completion, resulting in overall organizational inefficiency and project gridlock.

B. resources are underused

This is the opposite of the condition. The syndrome is characterized by the over-commitment and contention for resources, not their under-utilisation.

C. team members do not wish to finish projects

This describes a motivational or behavioural issue. The syndrome is a systemic problem rooted in organisational planning and portfolio management, not individual willingness.

D. lack of funding for projects

While funding secures resources, the syndrome is about the mismanagement of available resources across too many concurrent projects, not necessarily a lack of money.

1. Engwall, M., & Jerbrant, A. (2003). The resource allocation syndrome: the prime challenge of multi-project management? International Journal of Project Management, 21(6), pp. 403-409. The paper defines the syndrome as "a situation where there is an imbalance between the number of projects in a firm and its available resources to perform these projects." (Abstract, p. 403). DOI: https://doi.org/10.1016/S0263-7863(02)00113-800113-8)

2. Goldratt, E. M. (1997). Critical Chain. The North River Press. This foundational text explains the negative effects of multitasking in multi-project environments, which is a primary symptom of the resource allocation syndrome. It argues that attempting to advance all projects simultaneously with limited resources is a core cause of project delays (Chapters 1-4).

3. Meredith, J. R., Shafer, S. M., Mantel Jr, S. J., & Sutton, M. M. (2017). Project Management: A Managerial Approach. 10th ed. John Wiley & Sons. Chapter 7, "Resource Allocation," discusses the problems of resource loading and leveling, highlighting that when resource demands from multiple projects exceed availability, conflicts and delays are inevitable.

The Project Initiation Document (PID) is a cornerstone document in structured project management, particularly within methodologies like PRINCE2 which heavily influence CIPS curriculum. It is created during the initiation stage to provide a comprehensive foundation for the project.

The PID is a "living document." While it is formally created and baselined before the main execution stages begin, it is reviewed and can be updated at the end of each management stage. This ensures that the project's justification, scope, and plans remain valid and aligned with evolving circumstances (B).

Furthermore, the PID must present a balanced and realistic view. It consolidates the business case, which includes benefits and objectives (positives), alongside costs, constraints, assumptions, and a detailed risk assessment (negatives). This comprehensive picture is essential for the Project Board to make informed decisions about authorising and continuing the project (D).

A. it is created once at the beginning of the project and reviewed at the end

This is incorrect. The PID is a dynamic management product that is reviewed and updated at key decision points, such as the end of each management stage, not just at the project's conclusion.

C. it includes only the positive aspects of the project such as what the project will achieve

This is incorrect. A PID that omits risks, constraints, and other negative aspects would be misleading and would fail to provide a sound basis for project control and governance.

1. AXELOS. (2017). Managing Successful Projects with PRINCE2® (6th ed.). TSO (The Stationery Office).

Section 20.1, Purpose: "The purpose of the Project Initiation Documentation is to define the project, in order to form the basis for its management and an assessment of its overall success... The Project Initiation Documentation is a living product that should always reflect the current status, plans and controls of the project."

Section 20.4, Derivation and Format: "The Project Initiation Documentation is compiled during the initiating a project process... It is subject to formal change control and should be checked at stage boundaries (during a managing a stage boundary process) to see if any changes are required."

Appendix A, Section A.21, Project Initiation Documentation: This section lists the required composition, which includes the Business Case, Risk Management Approach, and Project Plan, all of which detail both positive and negative aspects (e.g., benefits vs. costs and risks).

2. Turner, J. R. (2014). The Handbook of Project-Based Management: Leading Strategic Change in Organizations (4th ed.). McGraw-Hill.

Chapter 10, Project Definition: Discusses the creation of a project definition report or PID. It emphasizes that this document must contain a thorough analysis of "constraints, assumptions, and risks" (p. 245) in addition to the project's objectives and scope, providing a complete picture for stakeholders to approve the project.

3. The Open University. (n.d.). M815: Project Management. Courseware.

Block 2, Part 3: Project start-up and initiation: The course materials, aligned with Association for Project Management (APM) and PRINCE2 standards, describe the PID (or equivalent Project Management Plan) as a document that is developed in the initiation phase and is updated through formal change control as the project progresses. It explicitly states the need to document risks, issues, and constraints.

Darryl is acting as a 'specialist' change agent. This type of agent is selected for their deep subject matter expertise and credibility within a specific area. They are typically internal employees tasked with leading focused, often incremental, changes. Their success relies on their ability to influence colleagues and gain buy-in through their recognised knowledge and reputation, rather than formal authority alone. The scenario explicitly highlights Darryl's "expertise in the subject matter" and the company's reliance on his "credibility" to ensure staff "embrace the proposed changes," which are characteristic of the specialist role.

A. transformer: A transformer is a change agent, typically a senior leader, who drives large-scale, strategic, and cultural shifts, which is inconsistent with the incremental change described.

C. enforcer: An enforcer uses hierarchical power and authority to implement change, often in a top-down manner. Darryl is relying on credibility and expertise, not enforcement.

D. independent: An independent change agent is an external consultant brought in for objectivity. Darryl is an internal Project Manager at the company, not an external party.

---

1. Buchanan, D., & Boddy, D. (1992). The Expertise of the Change Agent: Public Performance and Backstage Activity. Prentice Hall. This foundational text explores the role of change agents, emphasizing that their effectiveness is often derived from specific expertise (a specialist function) and the political skills to build credibility and support for change initiatives. The concept of a specialist aligns with their description of an agent whose influence stems from knowledge rather than just formal position.

2. Caldwell, R. (2003). Models of Change Agency: a Fourfold Classification. British Journal of Management, 14(2), pp. 131-142. Caldwell’s research classifies change agents and distinguishes between internal and external roles, as well as leadership styles. The specialist role fits within the internal agent category, whose influence is based on expert power rather than the coercive power of an 'enforcer' or the broad strategic vision of a 'transformer' (often termed a change leader). (See pp. 134-136 for typologies). DOI: https://doi.org/10.1111/1467-8551.00270

3. Senior, B., & Swailes, S. (2016). Organizational Change. 5th ed. Pearson Education. Chapter 9, "The Role of the Change Agent," discusses various types of change agents. It differentiates internal agents, like Darryl, from external (independent) agents. It also contrasts change management styles, where a specialist would use a collaborative or consultative approach based on their expertise, as opposed to a directive or coercive style associated with an enforcer.

Force Field Analysis, developed by Kurt Lewin, is a change management tool used to diagnose a situation by identifying the forces that are driving change and the opposing forces that are restraining it. In Benito's case, the team lacks understanding of the motivations (driving forces) and has low morale (a restraining force). By using this tool collaboratively, Benito can visually map out the reasons for the restructure (e.g., increased efficiency, market competition) and also acknowledge the team's concerns (e.g., fear of job insecurity, difficulty with new procedures). This process fosters understanding, encourages participation, and helps the team collectively find ways to weaken the restraining forces and support the change.

A. SWOT analysis is a strategic planning tool to assess an organisation's internal strengths/weaknesses and external opportunities/threats, not for managing team dynamics during a change.

B. STEEPLE analysis is a macro-environmental scanning tool to assess external factors affecting an organisation; it is not suitable for addressing internal team morale and procedural changes.

D. Multiple Cause Diagram (or Fishbone Diagram) is a root-cause analysis tool used to identify the potential causes of a specific problem, not to explain the rationale for a strategic change.

1. Cummings, T. G., & Worley, C. G. (2015). Organization development and change (10th ed.). Cengage Learning. In Chapter 2, "The Nature of Planned Change," Lewin's model is discussed, highlighting Force Field Analysis as a method to "diagnose the equilibrium by identifying the driving and restraining forces" (p. 31) to manage the change process effectively.

2. Burnes, B. (2020). The Origins of Lewin’s Three-Step Model of Change. The Journal of Applied Behavioral Science, 56(1), 32-59. This article reviews Lewin's work, explaining that Force Field Analysis is fundamental to his model. It is described as a framework for "identifying and evaluating all the forces that are promoting or hindering a particular change" (p. 45), making it ideal for helping a team understand the context of a change initiative.

3. CIPS (Chartered Institute of Procurement & Supply). (2019). Managing Ethical and Responsible Sourcing (L5M8 Course Book). Profex Publishing. Chapter 4, 'Managing change in the supply chain,' details various change management models. It presents Force Field Analysis as a practical tool for identifying barriers and enablers of change, which is essential for gaining team buy-in and addressing resistance, as faced by Benito.

The scenario describes a classic functional organizational structure. In this model, the organization is grouped by areas of specialization within different functional departments (e.g., engineering, marketing, finance). When a project requires input from multiple departments, the work is passed sequentially from one department to the next to complete its specific portion. Authority remains with the functional managers, and there is no single, overarching project manager with authority across all departments involved in the project. This departmental, siloed approach is the defining characteristic of a functional structure for managing projects.

B. projectized: This structure is organized entirely around projects, with a dedicated Project Manager having high authority. The scenario explicitly states there is no overarching PM.

C. matrix: This is a hybrid model where team members report to both a functional manager and a project manager, which is not the case here.

D. downstream: "Downstream" refers to the direction of workflow or activities in a process (e.g., in a supply chain), not a formal type of organizational structure.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Project Management Institute. In Section 2.4.4.1, "Functional Organization," it states, "In a functional organization... each department will do its project work independently of other departments." (p. 47).

2. Larson, E. W., & Gray, C. F. (2021). Project Management: The Managerial Process (8th ed.). McGraw-Hill Education. Chapter 3, "Organization: Structure and Culture," describes the functional structure: "The project is passed from one functional department to the next once its segment of the project is completed." This text is standard courseware in many university project management programs.

3. Kerzner, H. (2017). Project Management: A Systems Approach to Planning, Scheduling, and Controlling (12th ed.). Wiley. Chapter 3, "Organizational Structures," details the functional structure, highlighting that projects are managed within the existing functional hierarchy and coordination is handled by upper management, not a dedicated project manager.