E2: Managing projects

Answer: A. Project objectives are typically measured across time, cost and quality together, so a project that meets its time and cost targets but fails to meet the agreed specification has only partially met its overall objectives - quality is not a secondary consideration. Treating time and cost as the only objectives that matter overlooks quality entirely. Equally, missing one of the three objectives does not necessarily mean total failure; it usually means a partial shortfall against the full set of objectives, which still needs to be acknowledged and addressed.

Answer: B. A typical project life cycle progresses through initiation (defining the project and its objectives), planning (detailing how it will be delivered), execution (carrying out the planned work) and closure (formally completing and reviewing the project), each stage serving a distinct purpose. Projects are not delivered as a single simultaneous activity with no sequence - the staged structure is precisely the point. Closure is only the final stage, not the entirety of the life cycle, and the initiation-planning-execution-closure structure applies broadly across project types, not solely to manufacturing.

Answer: C. A work breakdown structure exists to break a project down into smaller, more manageable tasks and workstreams, which can then be planned, assigned to individuals or teams, and tracked individually as the project progresses. It is a planning and organisational tool, not a costing exercise in itself, even though it can support cost estimation. Creating a WBS does not remove the need for a project manager, who remains responsible for coordinating the tasks it identifies, and it is not designed to assign blame for failure - that is a different concern entirely from breaking down project work.

Answer: D. A Gantt chart visually displays project tasks against a timeline, making overall scheduling easy to see at a glance, while network analysis (including critical path analysis) focuses specifically on the logical sequence and dependencies between tasks, identifying which sequence of tasks determines the shortest possible project duration. The two techniques serve complementary but distinct purposes, not identical ones. Network analysis is particularly useful precisely when there are multiple interdependent tasks, not single-task projects, and Gantt charts are commonly used alongside other techniques, including network analysis, rather than in isolation.

Answer: A. A PERT chart can incorporate estimated task durations under different scenarios (such as optimistic, most likely and pessimistic estimates), helping project managers account for genuine uncertainty in how long tasks might take, which is a more probabilistic approach than a typical Gantt chart's fixed timeline view. PERT charts are used for projects of varying lengths, not limited to under a week, and they explicitly focus on task dependencies and sequencing, rather than removing the need to consider them. The two tools genuinely differ in emphasis and capability, despite both being used in project scheduling.

Answer: B. A key supplier failing to deliver materials on time, causing delays to dependent tasks, is a clear and common example of a genuine project risk that needs to be identified and managed. Describing tasks as always completed exactly on schedule, or budgets as guaranteed never to be exceeded, describes an unrealistic absence of risk that projects do not actually enjoy - risk identification exists precisely because such certainties do not hold in practice. Agreeing a plan does not eliminate uncertainty; it is simply the starting point against which risks must still be actively managed.

Answer: C. Scenario planning helps a project team explore how different plausible future events - such as a key risk materialising or not - might affect the project, allowing the team to think through and prepare responses in advance, rather than reacting only once a risk has already occurred. It does not predict which scenario will definitely happen; it explores possibilities to improve preparedness. Selecting a scenario to plan around does not remove the need for ongoing monitoring, and scenario planning is most valuable precisely for projects that do carry meaningful risk, not for risk-free ones.

Answer: D. Project management software typically supports scheduling, resource allocation and progress tracking, helping the team coordinate activity more effectively and identify emerging issues earlier than might otherwise be possible - it is a supporting tool, not a decision-maker in its own right. Using such software does not guarantee project success, since many other factors (such as team capability, scope clarity and stakeholder management) also matter. The software is also useful across projects of varying sizes, not only those above some arbitrary budget threshold.

Answer: B. A common challenge in matrix structures is the potential for conflicting priorities and unclear authority when functional and project demands compete for the same person's time and attention, since the team member effectively answers to two different lines of management. This is the opposite of having no line of authority at all - the issue is having two potentially competing ones, not none. Matrix structures are specifically associated with managing this kind of competing demand, not with avoiding it altogether, and they are used for project teams of varying sizes, not only single-person projects.

Answer: C. An effective project manager needs to plan the work, coordinate resources, manage risk, and communicate effectively with stakeholders throughout the project's life cycle - a broad set of coordinating and communication skills, not a narrow technical one. Personally performing every task would defeat the purpose of having a team and would be unrealistic for most projects of any scale. Focusing solely on cost ignores the equally important time and quality objectives, and withholding stakeholder communication until completion would undermine the ongoing engagement that effective project management depends on.

Answer: D. Recognising that project teams typically progress through a life cycle - forming relationships and ways of working early on, performing through delivery, and eventually disbanding once the project closes - helps a project manager anticipate and manage the different challenges that arise at each stage. Project teams do change and develop over time, contrary to a claim that they remain static. The team's life cycle, while related to the project's life cycle, is not identical to it in every respect, and disbandment matters to a project manager because how a team is wound down can affect morale, learning capture and future availability of its members.

Answer: A. Stakeholders beyond the sponsor - such as end users, suppliers, regulators or affected departments - often have differing interests and varying degrees of influence that can affect whether the project ultimately succeeds, which is why identifying them early helps the project manager plan how to engage and manage each group appropriately. Focusing solely on the sponsor risks missing influence or concerns that could derail the project later. Stakeholder identification needs to happen early, not after completion, when it is too late to act on it, and having multiple stakeholders does not doom a project to failure - effective stakeholder management is precisely what helps avoid that outcome.

Answer: B. A motivated team is more likely to sustain effort, maintain quality, and stay committed through the pressures, setbacks and changes that most projects encounter along the way, which is why motivation sits alongside technical planning as a genuine driver of project success, not a peripheral concern. Even a well-planned project can falter if the team delivering it becomes disengaged, so technical planning alone is not sufficient on its own. Setbacks are a normal part of most projects, regardless of how carefully they were planned, which is exactly why sustained motivation matters.

Answer: C. Time, cost and quality are typically interrelated, so compressing the timeline without additional budget to add resources often leaves less capacity to maintain the original quality standard, putting quality at risk as a likely consequence of this particular trade-off. Overtime does not fully substitute for elapsed time - sustained overtime introduces fatigue and error, and some activities simply cannot be compressed by working longer hours. Cost does not fall in proportion to time saved; rushing work often increases cost through inefficiency, overtime premiums or rework. And scope does not automatically expand to absorb saved time - scope is an objective to be controlled, and uncontrolled scope growth would worsen, not balance, the pressure on the other objectives.

Answer: D. Clear, agreed objectives for time, cost and quality give the project team and sponsor a shared, common basis for judging progress and resolving disagreements about scope or trade-offs that often arise as a project unfolds. Vague objectives tend to create confusion and disputes rather than offering useful freedom, since 'complete freedom with no accountability' undermines the basic purpose of having objectives at all. Objectives need to be defined before or early in the project, not after it is complete, and most well-run projects do allow agreed objectives to be revisited through a formal change-control process if circumstances genuinely change.

Answer: A. The planning stage typically involves developing a detailed schedule, allocating resources, and identifying risks, laying the groundwork before the actual work of the project begins. Closing out contracts and conducting a post-project review are activities associated with the closure stage, not planning. Carrying out the day-to-day tasks that produce deliverables is the execution stage's work, and approving the original business case is typically part of the earlier initiation stage, before detailed planning takes place.

Answer: B. The initiation stage typically involves defining the project's purpose, high-level objectives and overall feasibility, establishing whether and why the project should proceed before any detailed planning takes place. Detailed execution tasks belong to the later execution stage, and a lessons-learned review is a closure-stage activity, occurring after delivery rather than at the start. Detailed, task-level resource allocation is also a planning-stage activity that follows initiation, rather than being part of it.

Answer: C. Network analysis, including critical path analysis, is specifically designed to identify the sequence of interdependent tasks that determines the shortest possible overall project duration - exactly the need described, where delays in some tasks could significantly affect the end date. A simple task list with no dependency information would not reveal which tasks are critical to the timeline. A budget spreadsheet addresses cost, not scheduling dependencies, and a holiday calendar, while a useful planning input, does not itself identify the critical sequence of project tasks.

Answer: D. Data visualisations can present complex scheduling and progress information in an accessible, easy-to-interpret format, helping the project manager and stakeholders quickly identify delays, bottlenecks or other issues that might be harder to spot in raw data alone. They are not purely decorative; they serve a genuine analytical and communication purpose. Visualisations still depend on underlying progress data being collected in the first place - they do not remove that need - and they are most valuable when produced throughout a project, not only after it has finished.

Answer: A. Recording potential opportunities (upside risk) alongside threats (downside risk) allows the project team to actively plan how to pursue or capture favourable events, rather than treating risk management as solely defensive. Limiting the register to threats only would miss this proactive opportunity-management dimension. Recording opportunities is additional to, not a replacement for, identifying and managing threats, and there is no general rule that upside risks always carry greater financial impact than downside risks - the relative scale varies by project and by specific risk.

Answer: B. Without a specific, measurable specification - such as defined performance criteria, tolerances or acceptance standards - it becomes genuinely difficult to objectively judge whether a quality objective has been met, leaving room for disputes about whether 'good' was actually achieved. Flexibility has a real downside here: it removes the basis for objective assessment. Quality is one of the three core project objectives, not a secondary one, and a vague objective does not guarantee stakeholder satisfaction - it more often creates the conditions for disagreement about whether expectations were met.

Answer: C. When unexpected delays occur during execution, the typical and appropriate response is to reassess the schedule and resources, communicate the impact transparently to stakeholders, and adjust the plan as needed - active management of issues as they arise is a core part of the execution stage. Ignoring delays or refusing to revisit the plan would let a manageable issue snowball into a larger one. A single delay does not mean the project has failed outright, and waiting until closure to address an execution-stage issue would be far too late to actually manage its impact.

Answer: D. The closure stage typically involves conducting a post-project review to capture lessons learned, along with formally closing out remaining contracts, resources and administrative matters, bringing the project to a clean and complete end. Defining objectives and securing initial approval belongs to the earlier initiation stage, not closure. Detailed task-level scheduling is a planning-stage activity, and carrying out day-to-day work to produce deliverables is the substance of the execution stage, both of which occur well before closure.

Answer: A. Having one team member overloaded across multiple overlapping tasks while another has no work allocated illustrates a resource allocation imbalance, which scheduling tools such as Gantt charts can help identify visually, allowing the project manager to rebalance workload across the team - a process often called resource levelling. Deliberately keeping the strongest member fully loaded while others idle is not a recognised scheduling technique - it creates a single point of failure and wastes available capacity. The situation is a resourcing issue rather than a critical path problem, so extending the project deadline is not the necessary remedy - rebalancing work may resolve it within the existing timeline. And it is a workload problem, not a budgeting error - moving salary costs between people would change the numbers without changing who is overloaded.

Answer: B. Qualifying an alternative supplier in advance is a risk reduction response - it reduces the likely impact on the project if the primary supplier fails to deliver, without eliminating the underlying risk entirely. This is not risk acceptance, since the team has taken active steps rather than doing nothing. It is not risk avoidance either, since the project still depends on a supplier - just with a backup in place rather than removing the need for one. There is no indication the alternative supplier has taken on legal liability for the project's success, so this is not risk transfer.

Answer: C. Communicating identified risks to relevant stakeholders allows them to plan for potential impacts on their own areas of responsibility, and their perspective can also surface additional mitigation options that the project team alone might not have considered. Assuming stakeholders never have useful input overlooks the genuine value of their broader perspective and interests. Communicating a risk does not increase its likelihood of occurring - the risk exists independently of who is aware of it - and proactive communication, before a risk materialises, is exactly the point of risk management, not something to delay until after the fact.

Answer: D. In a purely functional structure, coordinating work that spans multiple departments can be genuinely harder, since there is no single role - such as a project manager - with clear cross-departmental authority over the project as a whole, leaving coordination to depend on ad hoc cooperation between department heads. This is a real limitation, not a strength, when compared with structures (such as a matrix or project-based structure) explicitly designed to coordinate cross-functional work. A purely functional structure still requires coordination between departments; it simply lacks a structural mechanism well suited to managing it for project work specifically, and it differs meaningfully from a dedicated project-based structure.

Answer: A. A project sponsor is typically a key role within a project team, providing senior-level support, securing resources, and giving strategic direction, helping the project manager navigate organisational priorities and obstacles. An external auditor's role concerns auditing financial statements, which is unrelated to project delivery roles in this sense, and a customer service representative or payroll administrator's day-to-day responsibilities are also not typically considered core project team roles, unless their specific expertise happens to be required for that particular project's work.

Answer: B. Common stakeholder mapping approaches suggest that a high-influence, low-interest stakeholder should generally be kept satisfied through periodic, high-level updates - enough to maintain their support without overwhelming them with day-to-day detail they have little appetite for. Providing them with the most frequent, detailed updates would likely be a poor use of effort given their actual interest level, and ignoring a high-influence stakeholder entirely would be a significant risk given the influence they hold over project success. Treating every stakeholder identically ignores the genuinely different engagement approaches that interest and influence levels call for.

Answer: C. Referring back to the documented, agreed scope provides an objective basis for resolving the disagreement, and facilitating a discussion between the stakeholders helps realign expectations and rebuild a shared understanding going forward - this combines factual grounding with genuine stakeholder management. Simply deferring to seniority, regardless of the actual documented scope, risks setting a precedent that decisions are made by hierarchy rather than evidence. Avoiding the disagreement risks it growing and affecting project delivery, and unilaterally deciding scope without reference to either party or the documentation would bypass the stakeholders' legitimate interest in how the project proceeds.

Answer: D. In practice, the three objectives frequently involve genuine trade-offs - for example, compressing the timeline can increase cost (through overtime or extra resources) or risk quality, so treating all three as simultaneously the single highest priority, with no acknowledgement of trade-offs, is often unrealistic. Claiming the objectives never interact ignores this well-recognised interdependency, and assuming all three can always be maximised together with no trade-off is rarely true in real project conditions. Far from removing the need for decisions, this tension is exactly why the project manager needs to make deliberate trade-off decisions throughout the project.

Answer: A. The typical project life cycle proceeds in the order initiation (establishing purpose and feasibility), planning (detailing how the work will be delivered), execution (carrying out the planned work) and closure (formally completing and reviewing the project) - each stage builds logically on the one before it. The other sequences presented reverse or scramble this logical order, which would not reflect how a project actually progresses from idea through to completion in practice.

Answer: B. Defining workstreams organises related groups of activities into manageable strands, each of which can be planned, resourced and tracked with a degree of independence, which is particularly useful in large or complex projects with many moving parts. It does not mean a single individual completes every task across every workstream - workstreams are typically resourced by different people or teams. Workstreams still need to feed into an overall project schedule, not replace the need for one, and most workstreams in a single project do need to coordinate with each other at key dependency points, rather than operating in complete isolation.

Answer: C. New risks can emerge as a project unfolds, and the likelihood or potential impact of existing risks can change with circumstances, so ongoing monitoring throughout the life cycle keeps the project's risk picture current and allows timely responses, rather than relying on a single, increasingly outdated assessment from the outset. Risks are not fixed in likelihood or impact once identified - they evolve. They are also not automatically resolved simply because time has passed, and assessing risk only at completion would be far too late to actually manage anything proactively, offering none of the benefit of ongoing monitoring.

Answer: D. A key advantage of a fully project-based structure is clearer lines of authority and focus - since team members report solely to the project rather than splitting attention between project and functional demands, it avoids the competing-priorities problem that can arise under a matrix structure's dual reporting lines. Team members still typically bring functional expertise into the project; the structure does not remove the need for that expertise, just the divided reporting line. There is no guarantee this structure always delivers faster - many other factors affect project speed - and a project manager remains a key role even when the team is fully dedicated, providing the leadership and coordination the structure depends on.

Answer: A. As a project nears completion and team members start anticipating their next assignment, engagement can naturally dip, so an aware project manager may need to actively manage morale, recognise contributions and plan a smooth transition, rather than assuming engagement will simply look after itself. Claiming morale is always unaffected, or that no further management attention is needed, overlooks this practical, well-recognised challenge near a project's conclusion. Sustained full engagement until the very last day is not something that can be assumed automatically without active management effort.

Answer: B. Different stakeholders typically have different needs, interests, and preferred channels of communication, so a tailored engagement plan is more likely to keep each group appropriately informed, engaged and supportive than a one-size-fits-all approach would achieve. Assuming every stakeholder wants identical information through an identical channel ignores genuine, well-recognised variation in stakeholder needs. Writing an engagement plan does not remove the need to actually communicate - the plan is the basis for ongoing communication, not a substitute for it - and engagement planning is valuable for projects with multiple stakeholders, which is the more typical and complex case it is designed to address.

Answer: C. When team members are seconded from other departments and retain a primary reporting line elsewhere, building genuine commitment and motivation to the project can be more difficult, since the project manager typically lacks the full formal authority a direct line manager would have, requiring greater reliance on influence, relationship-building and demonstrating the project's value to secure real engagement. The challenge is fundamentally about commitment and authority, not administration - timesheet mechanics are trivial by comparison. The project manager's authority is limited to the project itself and does not extend into each member's home role, which remains with their line manager. And secondees cannot be assumed to be more committed than permanent staff - even where secondment is a development opportunity, their loyalty, appraisal and career progression usually still sit with the home department.

Answer: D. The appropriate response is to assess how the requested scope increase would affect time, cost and quality, then formally agree any resulting changes to the objectives with the sponsor through a change control process - this keeps the project's objectives realistic and properly authorised as scope evolves. Implementing the change immediately without assessing impact risks unintended consequences for the other objectives. Objectives can be revised through proper governance; they are not permanently fixed from the outset. The sponsor, as the project's senior authority, is generally entitled to request and approve such changes, rather than this being solely the original project team's decision to ignore or accept unilaterally.

Answer: A. For a small, simple project with straightforward, sequential tasks and no significant dependencies to model, a simple Gantt chart or task list is often a proportionate level of planning detail, without necessarily needing the added complexity of full network analysis, which adds most value when dependencies are numerous and significant. Insisting that full critical path analysis is always required, regardless of project complexity, would be a disproportionate use of effort for a genuinely simple project. Using no planning tool at all would still leave the project lacking basic structure, and planning tools are useful across projects of varying sizes and complexity levels, not reserved exclusively for the largest ones.

Answer: B. The key consideration is whether the cost of mitigation is proportionate to the risk's actual likelihood and potential impact - over-investing significant resources in a low-probability, low-impact risk can divert attention and budget away from more significant risks that genuinely warrant that investment. Appearing on the risk register does not mandate full mitigation - the register is a monitoring tool, and acceptance is a legitimate response for minor risks. Spending mitigation budget simply because it is unspent inverts the logic of risk management - budget should follow risk priority, not the calendar. And a risk's priority should be driven by its likelihood and impact, not by the seniority of whoever raised it - senior sponsorship may affect visibility but is not a sound basis for allocating mitigation resources.

Answer: C. For a short, highly time-critical project needing fast decisions and minimal competing demands, a more dedicated, project-based arrangement - where team members are not also juggling functional responsibilities - may better support the speed and focus required, compared with a matrix structure where competing functional demands can slow decisions down. Claiming structural choice has no bearing on decision speed overlooks a genuine, practical effect of how a project is organised. A purely functional structure, lacking dedicated project roles altogether, would not generally suit a fast-moving, dedicated effort either, and always defaulting to a matrix structure regardless of the specific time pressures involved ignores the very structural trade-offs this scenario is designed to highlight.

Answer: D. In a project spanning multiple functions with differing priorities, the project manager typically plays a coordinating role - aligning each function's input towards the shared project goal, despite their differing priorities and working styles, rather than letting those differences pull the project in inconsistent directions. Personally taking over each function's specialist work would be impractical and would waste the very expertise the project depends on. Leaving the functions to coordinate entirely on their own would remove the coordinating role the project manager is specifically there to provide, and exclusively following one function's priorities while disregarding the others would undermine the cross-functional nature of the project's needs.

Answer: A. Engaging directly with affected employees to understand their specific concerns, and communicating honestly about what the changes will actually mean for their roles, is generally the most effective way to address resistance rooted in genuine fear or uncertainty - avoidance tends to let concerns fester and harden into stronger resistance. Dismissing concerns as irrelevant ignores the legitimate human impact of the change, which can itself fuel further resistance. Proceeding with no consideration of employee feedback at all risks both a poorly informed implementation and a workforce that feels unheard, neither of which supports a smooth or sustainable change.

Answer: B. Capturing lessons learned at closure can inform how future projects - even quite different ones - are planned and managed, helping the wider organisation build its project delivery capability over time, rather than each project repeating the same avoidable mistakes in isolation. Limiting relevance to an identical future project with the same team is far narrower than the genuine, broader organisational value lessons learned can provide. The value of capturing lessons does not disappear once a project is closed - quite the opposite, since closure is precisely when this reflection is captured for future use. Sharing lessons learned more widely, beyond the immediate project team, is generally what allows the organisation as a whole to benefit from them.