Free L5M8 Practice Test Questions and Answers (2026)

The methodology described is Agile. Key characteristics mentioned in the scenario, such as welcoming changing requirements and conducting daily 'scrum' meetings, are fundamental principles of the Agile approach. Agile is an iterative project management philosophy that prioritizes flexibility, customer collaboration, and rapid delivery in response to change. Scrum is one of the most popular frameworks used to implement Agile, and the daily scrum is a core ceremony within this framework for team synchronization and progress tracking. This approach is particularly effective for complex projects like software development where requirements are expected to evolve.

A. project diamond: This is a model for classifying projects based on their characteristics (novelty, technology, complexity, pace), not a methodology for executing them.

B. waterfall: This is a linear, sequential methodology where requirements are fixed at the start, and changes are difficult and discouraged, which is the opposite of the scenario.

D. Lean: While Lean principles can be complementary to Agile, its primary focus is on eliminating waste. The specific term 'scrum' is a hallmark of the Agile framework.

1. Schwaber, K., & Sutherland, J. (2020). The Scrum Guide. Scrum.org. This official guide defines the Scrum framework, which is a subset of Agile. It explicitly details the "Daily Scrum" (p. 9) as a 15-minute event for the Developers of the Scrum Team to inspect progress and adapt the plan for the next 24 hours.

2. Beck, K., et al. (2001). Manifesto for Agile Software Development. Agile Alliance. This foundational document states a core value as "Responding to change over following a plan," which directly supports the scenario's mention of welcoming changing requirements.

3. Shenhar, A. J., & Dvir, D. (2007). Reinventing project management: The diamond approach to successful growth and innovation. Harvard Business Press. Chapter 2 introduces the Diamond Model as a framework for project classification, distinguishing it from execution methodologies like Agile or Waterfall.

4. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Section 1.2.4.4 describes the Waterfall method as having "sequential phases" where "the project team proceeds to the next phase only when the previous phase is complete," highlighting its inflexibility to change.

The Critical Path Method (CPM) is a project modeling technique where the "critical path" represents the sequence of scheduled activities that determines the duration of the project. It is defined as the longest path through the project network, measured in terms of total time or duration. The sum of the durations of the activities on the critical path equals the shortest possible time to complete the entire project. Any delay to an activity on this path will directly result in a delay to the project's overall completion date. The path is not determined by the number of tasks or their complexity, but solely by their cumulative duration.

A. The critical path is determined by total duration, not the quantity of steps. A path with fewer steps can be longer if those steps have longer durations.

B. The path is measured by time, not the number of individual activities. A path with many short activities may be shorter than a path with a few long activities.

D. Complexity is a subjective measure and not the metric used in CPM. The method relies on the objective and quantifiable measure of time duration.

1. Vanhoucke, M. (2012). Project Management with Dynamic Scheduling: Baseline Scheduling, Risk Analysis and Project Control. Springer Science & Business Media. In Chapter 2, "The Critical Path Method," it is stated: "The critical path is the longest path from the unique start node to the unique end node of the network and its length is equal to the minimal project duration." (p. 19).

2. Liberatore, M. J., & Pollack-Johnson, B. (2013). "Improving project management decision making by modeling quality." IEEE Transactions on Engineering Management, 60(3), 547-557. The paper defines the critical path as "the longest duration path of activities through the project network, which determines the minimum project completion time." (Section II.A, para. 1). DOI: https://doi.org/10.1109/TEM.2012.2221993

3. Eppinger, S. D., & Browning, T. R. (2012). Design Structure Matrix Methods and Applications. MIT Press. In the context of project scheduling, the text explains: "The longest path of dependent tasks through the network is called the critical path because it determines the total time required to complete the project." (Chapter 7, p. 158).

4. MIT OpenCourseWare. (2005). 1.040 Project Management, Lecture 6: Project Scheduling: PERT/CPM. Massachusetts Institute of Technology. The lecture notes state: "The critical path is the longest path through the network. The length of the critical path is the project duration." (Section: The Critical Path Method (CPM), Slide 11).

A RACI (Responsible–Accountable–Consulted–Informed) matrix lists every project task against each stakeholder group and assigns one of the four RACI roles. By doing so it explicitly shows 1) which stakeholders must take part (Responsible or Accountable) and 2) which merely receive communications (Consulted or Informed). Hence it is the standard model for mapping stakeholder involvement and communication requirements in projects.

A. STEEPLED – Environmental scanning tool (Social, Technological, Economic, etc.); does not map individual stakeholders or communication lines.

C. Kraljic – Portfolio matrix for classifying purchased items by supply risk and impact on profit; unrelated to stakeholder communication.

D. Mendelow – Plots stakeholders by power × interest; indicates priority but not specific involvement levels or communication modes.

1. PMI, A Guide to the Project Management Body of Knowledge (PMBOK® 6th ed.), 2017, §9.1.2.1 “Responsibility Assignment Matrix”, pp. 318-319 – explains RACI and its use to define stakeholder involvement and communications.

2. CIPS, Level 5 Advanced Diploma, Module L5M8 “Project and Change Management”, Study Guide, 2021, Learning Outcome 1, pp. 18-19 – describes the RACI matrix as a method for identifying who is involved and how to communicate with them.

3. MIT OpenCourseWare, Course 15.761 “Operations Management – Special Topics: Project Management”, Lecture Notes 6, slide 14 – illustrates RACI chart and notes its role in clarifying communication with stakeholders.

An evolutionary approach to change is characterised by slow, gradual, and incremental adjustments. A significant disadvantage of this method is the inherent lack of immediacy. Without a compelling event or a "burning platform" to create a sense of urgency, stakeholders may not perceive the necessity for change. This can lead to complacency, inertia, and active resistance from individuals who are comfortable with the existing processes and see no immediate reason to alter their behaviour. The slow pace can make the change initiative seem less important, thus undermining the momentum required for successful implementation.

A. change is implemented too quickly that it may fail

This describes a revolutionary or 'big bang' approach, which is the opposite of a slow, gradual evolutionary strategy.

C. there is a lack of political capital to move the change along quickly

This is not a disadvantage inherent to the approach itself. In fact, a gradual approach may require less upfront political capital than a radical, disruptive one.

D. the change cannot take advantage of favourable circumstances

While a slow pace can make it harder to react to sudden opportunities, the word "cannot" is too absolute. The more fundamental issue is the lack of urgency which drives reluctance.

---

1. Kotter, J. P. (2012). Leading Change. Harvard Business Review Press. In Chapter 3, "Establishing a Sense of Urgency," Kotter argues that the single biggest error in change management is the failure to create sufficient urgency. Evolutionary approaches, by their nature, often fail to generate this critical momentum, leading to the complacency and reluctance described in the correct answer.

2. Burnes, B. (2017). Managing Change (7th ed.). Pearson Education. Chapter 10 discusses the emergent (evolutionary) approach to change. A key criticism highlighted is that its slow, incremental nature may not be sufficient to overcome organisational inertia and resistance, particularly when there is no clear and present crisis to galvanise action (p. 421-423).

3. Dunphy, D., & Stace, D. (1993). The strategic management of corporate change. Human Relations, 46(8), 905-920. This paper contrasts incremental (evolutionary) change with transformative change. It notes that incremental strategies are ill-suited for rapid adaptation, as they fail to generate the necessary momentum and urgency, making them vulnerable to employee resistance when a faster pace is required (p. 907). https://doi.org/10.1177/001872679304600801

The Executive is a key role on a Project Board, typically within a structured project management methodology like PRINCE2. This individual is the ultimate decision-maker and is accountable for the project's success, ensuring it remains viable and aligned with business objectives (a single point of accountability). They are responsible for balancing the competing interests of the business, users, and suppliers, thereby managing potential conflicts. The Executive is also responsible for commissioning the project and appointing the project management team, which includes the other members of the Project Board (the Senior User and Senior Supplier) and the Project Manager.

A. promotes the desired user outcomes: This is the primary responsibility of the Senior User, who represents the interests of those who will use the project's final products.

D. represents those that design and develop the project products: This is the role of the Senior Supplier, who represents the interests of those creating the project's specialist products.

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

Appendix C, Section C.3 (Executive): This section details the Executive's responsibilities, stating they are "ultimately accountable for the project’s success" (supports B), must "balance the demands of the business, user and supplier" (supports C), and are responsible for "appointing the project management team (including the rest of the Project Board and the Project Manager)" (supports E).

Appendix C, Sections C.4 (Senior User) and C.5 (Senior Supplier): These sections explicitly define the roles described in options A and D, assigning them to the Senior User and Senior Supplier respectively, confirming they are not the Executive's roles.

2. University of Cambridge, Institute for Manufacturing (IfM). (n.d.). Project Management - PRINCE2. Courseware.

In its description of the PRINCE2 framework, the course materials outline the Project Board structure. It specifies that the Executive "is appointed by corporate or programme management" and is responsible for "appointing the rest of the Project Board and the Project Manager." It also emphasizes the Executive's role in owning the Business Case, making them the single point of accountability for the project's value.

The initiation stage is the first formal phase of the project lifecycle. It is during this stage that the project is officially authorized, typically through the creation and approval of a project charter. This charter defines the project's objectives, identifies key stakeholders, appoints the project manager, and, crucially, assigns the high-level budget. Following this formal authorization, a kick-off meeting is held. This meeting serves to officially launch the project, align all stakeholders on the project's goals and scope, and formally transition the project from approval into the detailed planning phase.

A. The strategic stage precedes project initiation and involves identifying potential projects and developing a business case, not formally assigning a budget or holding a kick-off meeting.

C. The planning stage follows initiation. The kick-off meeting has already occurred, and the team uses the assigned budget to create detailed financial and resource plans.

D. The design stage is part of the project's execution phase, occurring much later, after the project has been initiated, planned, and formally kicked off.

---

1. CIPS Official Course Book - L5M8 Innovation in Procurement and Supply. The standard project management lifecycle model presented in CIPS materials outlines the 'Initiation' or 'Concept and Initiation' phase as the point where a project is defined, its feasibility is confirmed, and it is formally authorised. This authorisation includes the project charter which contains the preliminary budget and scope, leading directly to the project kick-off. (Note: Specific page numbers vary by edition, but this is covered in the chapter on Project Management).

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). The Initiating Process Group includes the 'Develop Project Charter' process (Section 4.1). The project charter is the document that "formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities" (p. 75). This includes the approved summary budget. The kick-off meeting is described as a key activity for stakeholder alignment at the start of the project, typically concluding the initiation phase or starting the planning phase.

3. Kerzner, H. (2017). Project Management: A Systems Approach to Planning, Scheduling, and Controlling (12th ed.). Wiley. In the discussion of project lifecycles, the initial phase (often termed 'Feasibility' or 'Initiation') is where "initial budget estimates are made" and upon approval, the project is formally started with a kick-off meeting to assemble the team and stakeholders. (Chapter 3: Project Management Life Cycles).

The scenario describes a significant organisational change with negative consequences for employees (staff reductions). The Change Cycle, often adapted from the Kübler-Ross model, describes the emotional stages people go through in response to such events. The initial reaction to the announcement of a disruptive change, especially one involving job losses, is a sense of loss—of security, routine, and colleagues. This is immediately followed by doubt and uncertainty about the future, the rationale for the change, and one's own position. These two stages represent the primary emotional and cognitive responses at the beginning of the change curve, preceding later stages like discovery and acceptance.

A. acceptance: This is a later stage in the Change Cycle, where employees begin to embrace the new situation and move forward.

B. discovery: This is a middle stage where individuals start to explore the new system and their new roles, signifying a move towards acceptance.

D. discomfort: While discomfort is experienced early, it is a general feeling that results from the more specific and primary reactions of loss and doubt.

1. Cameron, E., & Green, M. (2019). Making Sense of Change Management: A Complete Guide to the Models, Tools and Techniques of Organizational Change (5th ed.). Kogan Page.

Page 118, Chapter 5, 'Individual Change': The book discusses the Change Curve, noting that the initial phase following a change announcement is characterized by shock and denial, which is fundamentally a reaction to a perceived loss. The subsequent stage involves emotions like fear, anger, and self-doubt as individuals grapple with the implications of the change.

2. University of California, Berkeley. (n.d.). Change Management Toolkit: The Change Curve. UC Berkeley HR.

Section: 'The Change Curve': This university resource explains that the curve begins when a change is introduced, leading to a "dip in morale and performance." The initial stages are described with terms like shock, fear, and denial, all of which are rooted in a sense of loss. The subsequent stage of "resistance" is characterized by doubt, frustration, and uncertainty.

3. Kübler-Ross, E. (1969). On Death and Dying. Scribner.

Part I, Chapter 3-7: While the original context is grief, this foundational work is the basis for the Change Cycle. The initial stages of Denial and Anger are direct responses to a significant loss. The emotional turmoil described in these early stages inherently includes feelings of uncertainty and doubt about the situation and the future. This model is widely applied to organizational change to understand employee reactions.

An entropy event in an organizational context refers to a significant, often sudden, external shock that increases disorder, uncertainty, and complexity. A force majeure event—such as a natural disaster, pandemic, or act of war—is a prime example. It originates from the external environment, is beyond the organization's control, and introduces a high degree of chaos. Managing such an event requires non-standard, creative leadership to navigate the instability and restore order, which directly aligns with the question's premise.

A large-scale restructure leading to 100s of redundancies is an internal management decision, not an event originating from the external environment.

An increase in taxes is an external regulatory change, but it typically lacks the sudden, chaotic, and highly disruptive nature of a true entropy event.

An important project deadline is missed is an internal operational failure, not a disruptive event from the external environment.

1. Katz, D., & Kahn, R. L. (1978). The Social Psychology of Organizations (2nd ed.). Wiley. In their open systems theory (Chapter 2), they describe entropy as the tendency of systems to move towards disorganization. A major external shock, like a force majeure event, is a massive injection of entropy that the organization must counteract to survive.

2. Christopher, M., & Peck, H. (2004). Building the Resilient Supply Chain. The International Journal of Logistics Management, 15(2), 1-13. This paper discusses the sources of risk to supply chains, categorizing them as internal and external. Force majeure events are cited as key external environmental risks that cause major disruptions (i.e., entropy). (See Section: "Where does supply chain risk come from?", p. 4). https://doi.org/10.1108/09574090410700275

3. Mitroff, I. I., & Anagnos, G. (2001). Managing Crises Before They Happen: What Every Executive Needs to Know About Crisis Management. AMACOM. The authors differentiate between normal problems and true crises (entropy events), noting that crises are often triggered by major external events that threaten the organization's viability and require unconventional management approaches.

Weather prediction is an example of an open-ended change situation. This is because weather systems are complex, dynamic, and influenced by a vast number of interacting variables. Consequently, neither the precise future state (the 'what') nor the exact causal mechanisms leading to that state (the 'how') can be known with certainty. Open-ended situations are characterized by high ambiguity and unpredictability, requiring adaptive and emergent strategies to navigate, which is precisely the nature of meteorology.

A. closed change: This is incorrect because a closed change has a clearly defined outcome and method, whereas weather forecasting is inherently uncertain.

B. contained change: This is incorrect because in a contained change the goal ('what') is known but the method ('how') is not. In weather prediction, the goal itself (the future weather) is the uncertainty.

D. certain change: This is incorrect as it is a contradiction in terms. Weather prediction is probabilistic and deals with uncertainty, not certainty.

---

1. CIPS L5M8 Study Guide: Chartered Institute of Procurement & Supply. (2018). L5M8 Innovation in Procurement and Supply Study Guide. Stamford, UK: Profex Publishing. In Chapter 3, 'Change Management,' the guide defines open-ended problems as situations where neither the 'what' nor the 'how' is known, citing complex and unpredictable environments as examples.

2. Academic Publication (Project Management Typology): Turner, J. R., & Cochrane, R. A. (1993). Goals-and-methods matrix: coping with projects with ill defined goals and/or methods of achieving them. International Journal of Project Management, 11(2), 93-102. This paper's framework classifies projects based on the clarity of goals and methods. Weather prediction falls into Type 4 projects ('a walk in the fog'), where both goals and methods are unclear, aligning with the 'open-ended' concept. DOI: https://doi.org/10.1016/0263-7863(93)90017-H90017-H).

3. Foundational Text (Change Typology): Obeng, E. (1994). All Change!: The Project Leader's Secret Handbook. Financial Times/Prentice Hall. This book is a foundational source for the classification of change/project types, including 'closed' (Painting by Numbers), 'contained' (Quest), and 'open-ended' (A Walk in the Fog), which directly supports the classification of an unpredictable situation like weather forecasting.

A Project Report, often called a status or progress report, is a key communication tool used by a Project Manager to inform stakeholders about the project's performance. Its primary purpose is to provide a concise and clear summary. Including a RAG (Red, Amber, Green) status (B) offers an immediate visual indicator of the project's overall health across key areas like budget, schedule, and scope. A list of current issues (C) is also critical, as it informs stakeholders of the specific obstacles and challenges the project team is actively managing, which may require stakeholder intervention or awareness. These two elements are standard components of effective project reporting.

A. Project reports are typically concise summaries for stakeholders, especially senior management. Mandating 5–10 pages of detail is contrary to the principle of clear, brief communication and is not a standard expectation.

D. The stakeholder management plan is a strategic document created during the project initiation phase. It is not included in regular progress reports, which focus on performance and current status.

1. Association for Project Management (APM). (2019). APM Body of Knowledge (7th ed.).

Section 3.3.5, 'Reporting': This section emphasizes that reporting should be timely, relevant, and appropriate for the audience, providing progress against the plan and highlighting exceptions. This supports the use of summary tools like RAG status (a form of exception reporting) and lists of key issues, rather than lengthy, detailed documents (refuting A).

Section 4.1.5, 'Issue management': This section details the process of managing issues, a key part of which is communicating their status. A project report is the formal vehicle for this communication (supporting C).

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

Chapter 21, 'Management products', Section 21.2.10, 'Highlight Report': The PRINCE2 methodology specifies the 'Highlight Report' as the standard report from the Project Manager to the Project Board. Its template explicitly includes sections for the status of the stage and project (often using traffic lights/RAG) and for 'Major issues and risks'. This directly supports options B and C.

Section 21.2.2, 'Communication management approach': This document (analogous to a stakeholder management plan) is defined as a baseline management product created during initiation, confirming it is not part of a regular progress report (refuting D).

3. University of Washington. (n.d.). Project Management Center for Excellence, Templates.

The 'Project Status Report' template provided as a standard tool includes sections for "Overall Project Health" (with RAG indicators for Schedule, Scope, Budget, and Overall) and a dedicated section for "Issues". This serves as a practical example from a reputable institution that aligns with answers B and C.

'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.