Project Management Qualification (PMQ) Quiz 78

Correct: Benefits realization management is a continuous process that often extends beyond the project life cycle. While the project manager is responsible for delivering the outputs and capabilities, the project sponsor is ultimately accountable for the realization of benefits. During closure, the project manager must ensure that the benefits management plan, which outlines how and when benefits will be measured, is transitioned to the permanent organization, specifically the sponsor and business change managers who will monitor the outcomes in a business-as-usual environment. Incorrect: Keeping the project open for twelve months is inappropriate because projects are temporary endeavors; the realization phase is typically managed as part of operations or a program. Archiving the plan without a handover is incorrect because it neglects the tracking of the investment’s value, leading to a failure in benefits management. Redefining success criteria to ignore benefits is a poor practice that decouples the project from its original business case and justification. Key Takeaway: Benefits are often realized after the project has closed, necessitating a formal handover of tracking responsibilities from the project team to the business operations and the sponsor.

Correct: A hybrid life cycle is the most appropriate choice because the project contains two different work streams with different levels of uncertainty and stability. The hardware component has fixed, stable requirements (safety standards) which suit a linear approach, while the mobile application requires feedback and refinement, which suits an iterative or incremental approach. Combining these allows the project to manage risk effectively by providing structure where needed and flexibility where requirements are evolving. Incorrect: A linear life cycle is unsuitable because it assumes all requirements are known upfront. Applying it to the mobile application would likely result in a product that does not meet user needs because feedback is only gathered at the end of the project. Incorrect: An evolutionary life cycle is not ideal here because the hardware component requires a high degree of upfront planning and adherence to fixed standards, which can be difficult to manage in a purely evolutionary model that lacks a defined end-state. Incorrect: An agile life cycle might be too risky for the hardware component. Regulatory and safety standards often require detailed documentation and specific sequential milestones that are better managed through the predictive elements of a hybrid or linear model. Key Takeaway: The selection of a project life cycle should be based on the clarity of requirements, the level of technical uncertainty, and the need for stakeholder feedback. Hybrid models are often used when different work packages within the same project have conflicting needs for stability versus flexibility.

Correct: A pilot study is a small-scale implementation of the final product or service in a live operational environment. Its primary goal is to test the solution under real conditions to identify any issues before a full-scale rollout, thereby reducing risk. In contrast, prototyping is typically used during the design and development phases to test specific features, explore concepts, or refine requirements before the final solution is built. Incorrect: Creating a non-functional mock-up for stakeholder approval describes a form of prototyping, not a pilot study, and prototyping is not the final stage of deployment. Incorrect: Determining financial viability is part of the business case development in the concept phase, not a pilot study, and prototyping is not a method for organization-wide training. Incorrect: Developing code through iterative cycles refers to agile development methodologies rather than the specific purpose of a pilot study, and prototyping is used for design exploration rather than just documenting technical specifications for maintenance. Key Takeaway: Pilot studies validate the final solution in a live environment to ensure readiness for full deployment, whereas prototyping is an iterative tool used earlier to refine design and requirements.

Correct: An iterative delivery model is specifically designed to manage high levels of uncertainty and risk regarding the final product. By repeating cycles of development and seeking feedback on prototypes or drafts, the team can refine the requirements and design, ensuring the final solution aligns with user needs. Incorrect: An incremental delivery model focuses on breaking the project into smaller, functional pieces to deliver value early. While this reduces financial risk and speeds up delivery, it does not inherently focus on the refinement of a single complex feature through repeated cycles like the iterative model does. Incorrect: A linear delivery model, often called waterfall, is least effective in high-uncertainty environments because it assumes requirements are fixed at the start; any misalignment is usually only discovered at the very end of the project. Incorrect: A big-bang delivery model increases risk significantly because it delays the integration and release of all components until the end of the project, providing no opportunity for course correction based on user feedback. Key Takeaway: Iterative models are used to ‘get the product right’ through refinement, while incremental models are used to ‘get the product out’ in stages to realize value sooner. When the primary risk is product misalignment or vague requirements, iterative cycles are the preferred mitigation strategy.

Correct: Project governance defines the framework for decision-making and accountability. When a conflict exceeds the Project Manager’s delegated authority or threatens the validity of the business case, it must be escalated to the Project Sponsor or the Project Board. The Sponsor is ultimately accountable for the project’s success and the realization of benefits, making them the appropriate authority to resolve strategic conflicts. Incorrect: Prioritizing requirements based solely on seniority ignores the formal governance process and may lead to a solution that does not align with the project’s objectives or the business case. Incorrect: Management reserves are intended for unforeseen risks and issues, not for expanding the project scope to satisfy unauthorized requirements; using them in this way bypasses financial oversight and governance. Incorrect: While negotiation is a key skill, continuing to negotiate indefinitely when a project’s benefits are at risk is a failure of oversight. Governance structures are specifically designed to provide timely escalation paths to prevent such paralysis. Key Takeaway: Governance provides the structure through which project objectives are set and the means of attaining those objectives are determined, ensuring that escalation occurs when the project’s strategic alignment is at risk.

Correct: Effective project governance relies on a clear framework where roles, responsibilities, and accountabilities are explicitly defined. In this scenario, the delay is caused by a lack of clarity regarding who holds the authority to approve budget changes, which is a fundamental governance failure. A robust governance structure ensures that every participant knows their specific decision-making powers and the escalation paths for issues. Incorrect: Establishing a comprehensive reporting cycle focuses on the flow of information rather than the authority to act on that information; reporting alone does not solve accountability gaps. Incorrect: Giving the Project Manager ultimate authority to reallocate funds without oversight contradicts the principle of governance, which requires a system of checks and balances to protect the business case. Incorrect: While strategic alignment is a key principle of governance, the immediate issue in the scenario is a breakdown in the internal decision-making hierarchy and accountability, not a misalignment with corporate strategy. Key Takeaway: Governance provides the framework for decision-making; without clearly mapped accountabilities, projects suffer from paralysis and lack of oversight regardless of how well the technical work is performed or reported. No asterisks were used in this explanation and no letter references were made to the options provided.

Correct: The Project Sponsor is the owner of the business case and is responsible for ensuring the project remains aligned with the organization’s strategic objectives. When the corporate strategy changes, the Sponsor must assess if the project still provides value and remains viable. They provide the high-level direction necessary to ensure the project delivers the intended benefits or is adjusted to meet new strategic needs. Incorrect: Updating the project schedule and resource allocation is a tactical responsibility of the Project Manager, not a strategic responsibility of the Sponsor. Focusing solely on speed to finish the original scope ignores the strategic misalignment. Managing detailed technical requirements is also a functional or project management task; the Sponsor should remain at a strategic level rather than getting involved in low-level technical workflows. Authorizing the Project Manager to make all strategic decisions independently is incorrect because the Sponsor is ultimately accountable for the project’s success and its alignment with the business. Strategic decisions that affect the business case must be led or approved by the Sponsor. Key Takeaway: The Project Sponsor acts as the bridge between the project and the organization’s senior leadership, ensuring that the project’s investment continues to support the strategic goals of the business.

Correct: The project manager is responsible for the day-to-day management of the project. This includes monitoring progress, managing the team, and taking corrective action when the project deviates from the plan to ensure deliverables are met. Incorrect: Providing funding and high-level strategic direction is the responsibility of the Project Sponsor, not the project manager. Incorrect: Accountability for the business case and the realization of benefits lies with the Project Sponsor or the Senior Responsible Owner, while the project manager focuses on delivery. Incorrect: While the project manager ensures that a quality management system is in place, they do not typically perform the detailed technical testing themselves; this is the responsibility of technical specialists or team leads. Key Takeaway: The project manager’s role is centered on the day-to-day delivery and control of the project within the boundaries set by the Project Board.

Correct: The Project Steering Group (or Project Board) is responsible for the overall governance and strategic direction of the project. Their primary role includes monitoring the project against the Business Case and making the ‘go/no-go’ decisions at the end of each stage. When a significant change occurs that affects viability, they must review the Business Case to ensure the project still offers value for money before authorizing the next stage. Incorrect: Taking over day-to-day management is the responsibility of the Project Manager, not the Steering Group, which should remain at a strategic level. Incorrect: Redrafting the Project Management Plan and assigning tasks are operational management activities performed by the Project Manager. The Steering Group approves the plan but does not write it. Incorrect: Conducting detailed quality audits is typically the role of a Quality Assurance function or the Project Manager; the Steering Group receives reports on quality but does not perform the audits themselves. Key Takeaway: The Project Steering Group provides senior-level oversight and is ultimately accountable for the project’s success, focusing on strategic alignment and continued business justification rather than operational execution.

Correct: A Directive PMO takes over the management of projects by providing the project management expertise and resources. In this model, project managers are assigned by and report directly to the PMO. This results in a high level of control and means the PMO is directly responsible for the project outcomes. Incorrect: A Supportive PMO acts primarily as a resource center, providing templates, best practices, and training, but it has a low level of control and does not manage projects directly. Incorrect: A Controlling PMO provides support and requires compliance with specific frameworks, methodologies, or tools. While it has a moderate level of control, it typically does not assign project managers or take full responsibility for project execution. Incorrect: An Administrative PMO focuses on clerical tasks, data collection, and reporting rather than the strategic management or direct leadership of project teams. Key Takeaway: The level of authority and the reporting line of the project manager are the primary indicators used to distinguish between Supportive, Controlling, and Directive PMO models.

Correct: In project management governance, delegated authority is defined through tolerances. When a project manager forecasts that a tolerance (such as cost, time, or scope) will be exceeded, they no longer have the authority to manage the issue independently. The correct procedure is to escalate the situation immediately to the project sponsor or board using an exception report. This allows the higher-level authority to decide whether to increase the budget, reduce scope, or terminate the project. Incorrect: Reallocating funds from quality assurance to materials is incorrect because it compromises the quality tolerance and likely exceeds the project manager’s authority regarding quality standards. Negotiating a reduction in project scope is incorrect because scope changes typically require formal approval from the project board or a change control board; the project manager cannot unilaterally change the project’s objectives to stay within budget. Recording the variance in a highlight report and waiting for the next meeting is incorrect because a forecast breach of tolerance requires immediate escalation via an exception report rather than waiting for a routine progress update. Key Takeaway: Delegated authority is managed through tolerances, and any forecast breach of these limits must be escalated to the next management level via an exception report to maintain proper governance.

Correct: Corporate governance is the overarching system by which an entire organization is directed and controlled, encompassing ethics, risk management, and strategic direction. Project governance is a specific framework nested within corporate governance that provides the structure, processes, and decision-making models for managing a project. It ensures that the project remains accountable to the organization’s higher-level objectives. Incorrect: The suggestion that project governance is an independent framework designed to override corporate policies is incorrect because project governance must always operate within the boundaries and constraints set by the corporate level to ensure organizational integrity. The claim that corporate governance is exclusively focused on external compliance while project governance handles all strategic alignment is false; corporate governance is heavily involved in setting the strategic direction that projects must follow. The idea that project governance replaces corporate governance to give a Sponsor absolute authority is incorrect, as governance is about checks, balances, and accountability, not granting absolute power. Key Takeaway: Project governance provides the specific link between the project and the parent organization, ensuring that the project is governed in a way that is consistent with corporate values and strategic intent.

Correct: An external audit conducted by an independent consultancy provides the highest level of objectivity and independence. Because the auditors are outside the organization’s hierarchy and have no stake in the project’s outcome, they are less likely to be influenced by internal politics or ‘optimism bias,’ making their findings highly reliable for a Project Sponsor. Why incorrect: A peer review conducted by senior project managers from a different department is a form of internal assurance. While valuable for sharing best practices, it lacks the formal independence of an external audit and may still be influenced by the organization’s culture. An internal audit performed by the organization’s quality assurance department is more formal than a peer review but is still considered internal assurance. While it follows organizational standards, it may not provide the same level of external perspective or specialized expertise as a third-party consultancy. A detailed project status presentation delivered by the Project Manager is a reporting activity, not an assurance activity. It is inherently subjective as it is produced by the team responsible for delivery. Key Takeaway: Effective project assurance relies on the principle of independence; the more removed the assurance provider is from the project delivery, the higher the level of objective confidence they provide to stakeholders.

Correct: The primary objective of a project audit is to provide an independent and objective assessment of whether the project is adhering to organizational standards, policies, and the defined project management plan. This provides assurance to senior management and stakeholders that governance is being maintained. Incorrect: Conducting a technical review of software code refers to quality control or technical peer reviews, which focus on the product’s attributes rather than process compliance. Facilitating team-building exercises is a leadership and resource management activity aimed at team development, not a compliance audit function. Renegotiating the project baseline is a change management or project control activity that occurs through formal change requests, whereas an audit is meant to verify adherence to existing standards rather than change the project’s fundamental constraints. Key Takeaway: Project audits are a key part of quality assurance, focusing on process compliance and providing confidence to stakeholders that the project is being managed correctly.

Correct: Effective project governance requires that the project board has clear accountabilities for ensuring the project operates within the legal and regulatory environment. By defining these accountabilities, the board ensures that compliance with laws such as the General Data Protection Regulation (GDPR) or the Health and Safety at Work Act is monitored and managed at the highest level of the project. Incorrect: Transferring risks to external vendors through contracts does not eliminate the project’s legal liability, as the sponsoring organization often remains the data controller or the primary duty holder under safety laws. Incorrect: Assigning compliance solely to the project manager is a failure of governance; the project board must provide oversight and support for legal obligations as they are ultimately accountable for the project’s success and legality. Incorrect: Conducting a single audit at the end of the project is insufficient because regulatory compliance must be an ongoing process throughout the project lifecycle to prevent costly breaches or safety incidents. Key Takeaway: Project governance must integrate regulatory frameworks by establishing clear roles, responsibilities, and reporting lines for legal compliance at the board level to ensure continuous oversight and risk mitigation.

Correct: The user representative is a key role in project governance responsible for representing the interests of those who will use the project’s products. Their primary duty is to define the requirements clearly and ensure that the solution is fit for purpose so that the business can actually use the outputs to realize the expected benefits. Incorrect: Securing investment and maintaining the business case is the responsibility of the Project Sponsor, who owns the project from a financial and strategic perspective. Incorrect: Directing the technical team on coding standards and architecture is the responsibility of the Senior Supplier or a technical lead, representing the interests of those who design and build the solution. Incorrect: Authorizing changes when tolerances are exceeded is a function of the Project Board or the Project Sponsor, depending on the severity of the change and the governance framework in place. Key Takeaway: The user representative acts as the bridge between the project team and the end-users, ensuring the project delivers what the business actually needs to operate effectively.

Correct: The Terms of Reference (ToR) for a governance board are essential for establishing the framework within which the board operates. It clarifies who is on the board, what their specific responsibilities are, and how they will make decisions. This ensures that the project has clear leadership and that the board can provide the necessary strategic alignment and support to the project manager. Incorrect: Detailing day-to-day task assignments is an operational management activity performed by the project manager or team leads, not a function of a governance board’s ToR. Incorrect: Outlining technical design specifications is part of the project’s technical documentation or quality management plan, rather than a governance document. Incorrect: Establishing legal procurement terms is the function of a contract or a procurement management plan, not the governance board’s ToR. Key Takeaway: Effective project governance requires a clear Terms of Reference to define accountability, authority, and the boundaries of the board’s oversight role.

Correct: The projectized structure is characterized by the project manager having nearly total authority over the project. In this environment, the team is dedicated to the project, and the project manager controls the budget and resource assignments. This structure eliminates the need for constant negotiation with functional managers because the functional silos are replaced by project-based units. Incorrect: The strong matrix structure provides significant authority to the project manager, but team members still maintain a relationship with their functional departments, which contradicts the scenario where they have no functional home. The balanced matrix structure involves shared power between functional managers and project managers, which does not meet the requirement for total project manager authority. The functional structure is the opposite of what is described, as it places all power with the department heads and gives the project manager little to no formal authority. Key Takeaway: A projectized structure is the most project-centric organizational form, offering the highest level of autonomy for the project manager but often creating inefficiency due to the lack of a stable functional home for staff once a project concludes.

Correct: In a functional organizational structure, the project manager typically has very limited authority, often acting as a project coordinator or expeditor. The power resides with the functional managers who control the resources and the budget. Therefore, the project manager must use negotiation and interpersonal skills to gain the cooperation of functional heads who often prioritize their own departmental objectives over project goals. Incorrect: The option suggesting the project manager has high authority over the budget and can hire external consultants is incorrect because in a functional structure, the functional manager usually controls the budget, not the project manager. The option stating the project manager can issue direct orders because project work takes precedence is incorrect because in this structure, departmental work is generally the priority, and the project manager lacks the formal authority to override functional managers. The option regarding permanently assigned resources is incorrect because that describes a project-oriented or projectized structure, not a functional one. Key Takeaway: In functional organizations, project managers must navigate a landscape where they have low authority and must compete with operational priorities for resource time through negotiation and influence.

Correct: In a weak matrix structure, the project manager acts primarily as a coordinator or expeditor. They have limited authority, and the functional managers retain control over the budget and the project resources. This aligns with the scenario where the project manager lacks budget control and team members report to functional heads for appraisals. Incorrect: A strong matrix is incorrect because in that structure, the project manager has a high level of authority, often manages the project budget, and usually works in a dedicated project management department. Incorrect: A balanced matrix is incorrect because it involves a more equal distribution of power between the project manager and functional managers, where the project manager typically has more influence over the budget and resource allocation than described here. Incorrect: A project-oriented structure is incorrect because in such an organization, the project manager has total or near-total authority, and team members are often co-located and report directly to the project manager rather than a functional department. Key Takeaway: The distinguishing factor of a weak matrix is that the functional manager maintains the majority of the power, leaving the project manager in a role focused on coordination and communication.

Correct: In a projectized or project-based structure, the organization is organized by projects rather than functions. While this provides the Project Manager with high levels of authority and ensures the team is fully dedicated to project goals, it often leads to inefficiencies at the corporate level because resources are not shared between projects. Furthermore, because there are no functional departments to return to, staff may face job insecurity or ‘bench time’ when the project ends, which is a significant organizational risk. Incorrect: The suggestion that functional managers retain authority describes a functional or weak matrix structure, whereas in a projectized structure, the Project Manager holds the majority of the power. Incorrect: The idea that team members are distracted by departmental responsibilities is a characteristic of functional or matrix organizations; dedicated teams in a projectized environment are specifically shielded from such distractions. Incorrect: Project Managers in a projectized structure typically have high to total control over the budget and resource selection, making the claim of limited control inaccurate for this organizational type. Key Takeaway: While projectized structures maximize project focus and PM authority, they sacrifice the resource-sharing efficiencies and career stability found in functional or matrix structures. This often results in the ‘duplication of effort’ across different project silos within the same company.

Correct: A Strong Matrix structure is the most appropriate choice because it shifts the balance of power toward the project manager while still maintaining the functional departments. In this structure, project managers have high authority and often manage the project budget, while functional managers provide technical expertise and manage the staff’s long-term career development. Incorrect: The Functional structure is what the firm is currently struggling with, where power resides entirely with department heads, leading to project delays. The Weak Matrix structure would not solve the problem because the project manager would remain in a coordinator role with limited authority, leaving the functional managers in control of resource priorities. The Project-based (Dedicated) structure would give the project manager total authority, but it would require dismantling the functional departments, which the executive board specifically wants to avoid to maintain professional standards and career paths. Key Takeaway: Choosing an organizational structure requires balancing the level of authority needed by the project manager against the organization’s need for functional expertise and resource efficiency. Strong Matrix structures are often the middle ground for organizations that are project-heavy but require deep technical specialization across departments.

Correct: In a functional structure, the organization is grouped by specialty, and the project manager typically has little to no formal authority, often acting as a coordinator or expeditor. Communication must follow the chain of command, meaning cross-functional issues must be escalated up to a level where the functional silos meet. This vertical communication flow and the prioritization of functional goals over project goals lead to slow decision-making and project delays. Incorrect: A strong matrix structure would grant the project manager more authority than the functional managers, which contradicts the scenario where the PM has no formal authority. Incorrect: In a project-oriented structure, the project manager has total authority over the team, and communication is typically very fast and direct, which is the opposite of the delays described. Incorrect: A balanced matrix involves shared power, but the scenario specifically describes a situation where functional heads dominate the decision-making process and the PM is sidelined, which is characteristic of a functional or weak matrix. Key Takeaway: The organizational structure defines the power balance between project and functional managers; in functional organizations, the project manager’s lack of authority and the reliance on vertical communication channels significantly hinder the speed of project decision-making.

Correct: In a Balanced Matrix organization, power and authority are shared between the project manager and the functional manager. Because neither party has total control over the resource, negotiation is the primary tool for resolving conflicts. The project manager should first attempt to find a mutually beneficial solution or a compromise that balances project needs with operational requirements. Incorrect: Exercising authority to command the resource is incorrect because in a balanced matrix, the project manager does not have full line management authority over staff; that authority remains partially with the functional manager. Escalating to the Project Sponsor is premature; escalation should only occur after direct negotiation between the project manager and functional manager has failed. Updating the schedule and blaming the functional department is a passive approach that fails to manage the resource issue proactively and damages the collaborative environment necessary in matrix structures. Key Takeaway: In matrix environments, successful resource management relies heavily on negotiation, communication, and the ability of the project manager to influence stakeholders without having formal line authority.

Correct: Facilitating a cross-functional workshop is the most effective approach because it addresses the root cause of the conflict by aligning the project’s success with the functional managers’ own goals. Establishing a shared resource management agreement ensures transparency and commitment from all parties, which is essential for managing boundaries in a matrix environment. Incorrect: Submitting a formal change request to extend the timeline may provide temporary relief but does not solve the underlying conflict between departmental KPIs and project requirements. Incorrect: Requesting the Project Sponsor to mandate prioritization is an escalation that should be a last resort; it can damage long-term relationships and does not foster the collaborative environment needed for cross-functional success. Incorrect: Redesigning the project into isolated workstreams is counterproductive for an organizational change project, as it creates silos that prevent the integration necessary for the project to deliver its intended benefits. Key Takeaway: Managing departmental boundaries requires the project manager to act as a bridge, ensuring that functional managers see the project as a benefit to their own departments rather than a threat to their resources or performance metrics. Integrated governance and collaborative negotiation are the primary tools for maintaining cross-functional team dynamics. No asterisks or letter references were used in this explanation as per the requirements provided.

Correct: Implementing a centralized cloud-based platform ensures a single source of truth and prevents versioning conflicts, which are common in distributed teams. A team charter complements this technology by setting clear behavioral expectations, such as when to use instant messaging for urgent issues versus email for non-urgent updates, helping to manage the challenges of asynchronous communication across time zones. Incorrect: Requiring significant shift changes to create a four-hour overlap is often impractical and can lead to burnout or high staff turnover, especially when time zones are significantly far apart like Seattle and Dubai. Incorrect: Decentralized file storage creates silos and increases the risk of team members working from outdated information, which contradicts the need for integration in project management. Incorrect: Restricting communication to weekly conferences creates a bottleneck, as team members may wait days for answers to critical questions, significantly slowing project velocity and failing to utilize the benefits of asynchronous technological tools. Key Takeaway: Successful distributed teams require a combination of integrated technology for transparency and a clear communication framework to manage asynchronous workflows effectively.

Correct: The Organizational Breakdown Structure (OBS) is a hierarchical representation of the project organization. When the OBS is mapped against the Work Breakdown Structure (WBS), it creates the Responsibility Assignment Matrix (RAM). This matrix is the primary tool for ensuring that every work package has a clearly defined owner and that roles such as Responsible, Accountable, Consulted, and Informed are assigned. Incorrect: Defining the critical path and logical dependencies is a function of project scheduling and network analysis, not the OBS. While the OBS shows hierarchy, it does not show the sequence of work. Categorizing risks by functional area is a component of a Risk Breakdown Structure (RBS), which is distinct from the OBS. Allocating costs to work packages is part of the cost baseline and budgeting process, often represented in a Cost Breakdown Structure (CBS), rather than the organizational hierarchy. Key Takeaway: The integration of the WBS and the OBS is the fundamental step in establishing clear accountability and resource management through the Responsibility Assignment Matrix.

Correct: The integration of the Work Breakdown Structure (WBS) and the Organizational Breakdown Structure (OBS) is a fundamental step in project control. By mapping the ‘what’ (WBS) to the ‘who’ (OBS), the project manager creates a Responsibility Assignment Matrix (RAM). The intersection points between these two structures are known as Control Accounts. These accounts serve as the primary management control points where scope, budget, and schedule are integrated and compared to earned value for performance measurement. Incorrect: The creation of a Resource Histogram is a resource management activity that focuses on the quantity of resources over time, rather than the structural accountability provided by the WBS/OBS integration. Incorrect: The Project Scope Statement is an input to the creation of the WBS, not a result of integrating the WBS with the OBS. Incorrect: The development of a Critical Path Method (CPM) network diagram is a scheduling process that focuses on the logical sequencing of activities and time management, which is distinct from the organizational accountability established by the WBS/OBS matrix. Key Takeaway: The intersection of the WBS and OBS defines the Control Account, which is the essential unit for monitoring project performance and assigning clear responsibility for specific work packages.

Correct: In a project-oriented (projectised) structure, the project manager has a high level of authority and independence. They control the budget and the team members report directly to them, which is exactly what the new role describes. The previous role, where department heads controlled the budget and resources, is characteristic of a functional or weak matrix structure. Incorrect: Moving from a strong matrix to a functional structure would actually decrease authority and autonomy, as functional structures place the most power in the hands of departmental managers rather than project managers. Incorrect: The scenario describes a move toward full control, whereas a balanced matrix involves shared authority between the project manager and functional managers, which does not match the description of the new role. Incorrect: While a strong matrix increases project manager authority compared to a weak matrix, the description of having a dedicated team reporting directly to the project manager and full budget accountability is the defining characteristic of a project-oriented structure, not a matrix structure. Key Takeaway: The organizational structure is the primary factor determining a project manager’s level of authority, with project-oriented structures providing the highest level of autonomy and functional structures providing the lowest.

Correct: In a geography-based structure, the primary disadvantage is the duplication of resources. Because each region operates as a semi-autonomous unit, they often hire their own specialists and maintain their own support functions, which leads to higher costs and less efficiency compared to a centralized functional model where resources are shared across the whole organization. Incorrect: A lack of understanding regarding local cultural nuances is incorrect because geography-based structures are specifically designed to improve local knowledge and responsiveness by placing teams within the regions they serve. Incorrect: The inability to comply with local data protection regulations is incorrect because being based within a specific geography typically makes it easier for a team to understand and adhere to local legal and regulatory requirements. Incorrect: A decrease in the project manager’s authority is incorrect because while the reporting lines may change, geography-based structures often empower local project managers to make decisions that are relevant to their specific region, rather than centralizing all authority at a distant headquarters. Key Takeaway: While geography-based structures enhance local responsiveness and customer service, they often suffer from resource duplication and a lack of global economies of scale, which project managers must account for in their resource management plans.