8. Resources, Organization and Project Leadership

Introduction and Context

Projects convert strategy into temporary, coordinated action. Whether the project involves installing a production line, developing a new product, implementing an enterprise resource planning system, or improving a supply network, its success depends not only on scope, schedule, cost, and quality plans but also on the way resources are organized and led. A technically sound plan can fail when skilled people are unavailable, equipment is overloaded, responsibilities are unclear, or conflicts remain unresolved.

Resource management in projects includes the planning, acquisition, allocation, development, and control of physical and human resources. Physical resources may include materials, machinery, tools, facilities, information systems, energy, and working space. Human resources include the project manager, specialists, operators, suppliers, contractors, sponsors, users, and other stakeholders. These resources are interdependent. A shortage of skilled technicians may delay equipment commissioning; inadequate workspace may reduce team productivity; poor coordination between engineering and procurement may create material shortages.

Project organization provides the structural arrangement through which authority, responsibility, communication, and accountability are established. Project leadership gives this structure direction and meaning. Leadership is not limited to issuing instructions. It involves influencing people, creating commitment, resolving ambiguity, maintaining ethical standards, and enabling the team to perform under uncertainty.

For postgraduate managers, the central issue is not simply how to obtain resources. It is how to create a system in which resources are used productively, competing demands are balanced, knowledge is shared, and people can collaborate across functions, cultures, locations, and organizational boundaries.

Learning Objectives

After studying this chapter, students should be able to:

1. Explain the strategic role of physical and human resource management in projects.

2. Develop resource requirements, responsibility structures, and resource calendars.

3. Analyse capacity, workload, resource constraints, and trade-offs among competing projects.

4. Compare functional, matrix, projectized, and hybrid project organizations.

5. Apply theories of motivation, leadership, team development, conflict, and negotiation.

6. Design practices that support psychological safety, inclusion, and ethical conduct.

7. Lead cross-functional, multicultural, and virtual project teams.

8. Evaluate the use of digital tools, analytics, and artificial intelligence in resource and team management.

9. Diagnose resource and leadership risks through applied project scenarios.

Resources as a Strategic Project Variable

A resource plan translates project requirements into practical questions: what is needed, in what quantity, at what time, at what location, and under whose control? Resource planning should begin with the work breakdown structure and schedule, but it should not be treated as a mechanical exercise. Estimates are uncertain, resource productivity varies, and availability is influenced by organizational priorities.

A useful resource statement identifies:

• the type and quantity of resource required;
• the timing and duration of its use;
• the competence or specification required;
• the source of the resource;
• the cost and contractual conditions;
• constraints such as shared use, lead time, safety, or location;
• risks associated with non-availability or poor performance.

Physical resources are often visible and therefore easier to plan, but they can still produce substantial uncertainty. Long-lead equipment, imported components, specialized testing facilities, and constrained production capacity may determine the critical path. A machine may be available in quantity but not in the required condition, accuracy, or operating window. Similarly, the apparent availability of a facility may conceal maintenance shutdowns, regulatory restrictions, or competing production commitments.

Human resources are more complex because competence, motivation, relationships, and learning affect performance. Two employees with the same job title may have different levels of project experience. A specialist may be technically excellent but unavailable during commissioning. A contractor may possess the required skill but lack familiarity with the organization’s safety or quality systems. Consequently, resource planning must consider both capacity and capability.

The distinction between capacity and capability is important. Capacity refers to the amount of work that can be undertaken during a period. Capability refers to the knowledge, skill, experience, authority, and behavioural capacity to perform that work effectively. A project team can have sufficient numerical capacity but inadequate capability, or highly capable people whose workloads exceed realistic capacity.

From Work Packages to Resource Commitments

Resource planning normally proceeds through several connected activities. First, the project team decomposes scope into work packages and activities. Second, it estimates the labour, equipment, materials, facilities, and information needed for each activity. Third, these requirements are time-phased against the schedule. Fourth, the project compares requirements with actual availability. Finally, management resolves gaps through recruitment, procurement, outsourcing, rescheduling, scope adjustment, or priority decisions.

The resulting information may be represented in a resource breakdown structure, which classifies resources by category, department, skill, location, or supplier. A resource calendar records when people, equipment, or facilities are available. A responsibility assignment matrix links work packages to accountable and supporting roles. The RACI format is frequently used: Responsible identifies the person performing the work, Accountable identifies the person answerable for the result, Consulted identifies contributors whose expertise is required, and Informed identifies parties who must receive information. RACI is useful, but it should not create multiple accountabilities for one deliverable or substitute for meaningful discussion about authority.

Resource histograms display demand over time. When demand exceeds available capacity, the project manager must decide whether to level resources, smooth resources, add capacity, or change the plan. Resource leveling changes activity timing to remove over-allocation and may extend the schedule. Resource smoothing adjusts activities within available float so that resource use is more even without changing the critical completion date, where possible. Both techniques involve trade-offs. A levelled plan may be more realistic but longer; a smoothed plan may preserve the deadline but leave little flexibility.

A simple capacity calculation can clarify the issue. If six analysts are available for four weeks at 30 productive hours per week, nominal capacity is 720 hours. If meetings, training, leave, coordination, and operational duties consume 20 percent, practical capacity falls to 576 hours. If the project requires 640 hours, management cannot assume that the gap will be solved through effort alone. Options include adding an analyst, reducing scope, extending the schedule, improving methods, or assigning work to another unit.

Such calculations should be treated as decision aids rather than precise predictions. Knowledge work is not perfectly divisible, and adding people to a late project may increase communication overhead. Brooks’s Law captures this risk in software development: adding people to a late project can make it later when coordination and onboarding costs exceed the benefit of additional labour. The broader lesson applies beyond software: capacity must be evaluated in relation to workflow, interdependence, and learning time.

Organizing the Project: Authority and Integration

The project organization determines how project work is connected to the permanent organization. In a functional structure, authority rests primarily with departmental managers. The project manager may coordinate activities but often has limited control over staff and budgets. This arrangement supports technical specialization and efficient use of departmental resources, but projects may suffer from slow decisions and weak cross-functional integration.

In a projectized structure, personnel are organized largely around projects and the project manager has substantial authority over budget, resources, and decisions. This can strengthen commitment and responsiveness, although it may duplicate expertise and create uncertainty about staff roles after project completion.

A matrix structure shares authority between functional and project managers. In a weak matrix, the functional manager retains most authority. In a strong matrix, the project manager has greater control. A balanced matrix attempts to share authority. Matrix structures can support efficient specialist utilization and project integration, but they also create potential conflict over priorities, performance appraisal, and resource allocation.

Many organizations use hybrid arrangements. For example, production engineers may remain in functional departments, while a dedicated project office coordinates major capital projects. The appropriate arrangement depends on project complexity, strategic importance, resource scarcity, organizational maturity, and the need for specialist continuity. No structure eliminates conflict; it merely determines where conflict is likely to occur and how it must be governed.

Governance mechanisms are therefore essential. A project charter should clarify authority, sponsorship, decision rights, escalation routes, and success criteria. A steering committee can resolve issues that exceed the project manager’s authority. Stage reviews provide opportunities to reassess resource commitments as evidence improves. Decision logs and change-control records preserve accountability and reduce later disputes about what was agreed.

Building and Developing Cross-Functional Teams

A project team is more than a collection of assigned individuals. It is a temporary social and technical system whose members depend on one another to achieve a shared outcome. Cross-functional teams combine different perspectives from operations, engineering, quality, finance, procurement, information technology, marketing, and external partners. Their diversity can improve problem solving, but it can also create disagreement over language, priorities, methods, and measures of success.

Team development is often described through Tuckman’s stages: forming, storming, norming, performing, and adjourning. The stages are not necessarily linear, and teams may regress when membership changes or a crisis occurs. During forming, members seek clarity about purpose and relationships. Storming involves conflict over roles, methods, influence, and priorities. Norming develops shared rules and trust. Performing is characterized by effective coordination and problem solving. Adjourning concerns closure, learning, and transition.

The project manager can accelerate team maturity by establishing a clear purpose, defining interfaces, agreeing working norms, making decision processes explicit, and ensuring early opportunities for meaningful collaboration. A team charter may address meeting practices, response times, escalation, documentation, behavioural expectations, inclusion, and how disagreement will be handled.

Effective teams require both task management and relationship management. Task mechanisms include integrated schedules, interface registers, design reviews, issue logs, and performance dashboards. Relationship mechanisms include one-to-one conversations, recognition, listening, coaching, and fair treatment. Excessive attention to either dimension is harmful: a team can be friendly but ineffective, or productive in the short term but psychologically unsafe and unsustainable.

Motivation and Engagement in Project Work

Motivation explains why individuals direct effort, sustain it, and choose particular behaviours. Project managers should avoid assuming that money is the only or dominant motivator. Herzberg’s two-factor theory distinguishes hygiene factors, such as pay, policy, working conditions, and supervision, from motivators, such as achievement, recognition, responsibility, and growth. Improving hygiene factors may prevent dissatisfaction, but meaningful engagement often requires opportunities for achievement and ownership.

McClelland’s acquired-needs theory highlights needs for achievement, affiliation, and power. A high-achievement specialist may value challenging and measurable assignments; a person with a strong affiliation need may respond positively to collaboration; an individual motivated by power may be effective when given legitimate influence and responsibility. These tendencies should guide managerial conversations rather than become rigid labels.

Expectancy theory proposes that motivation depends on three relationships: effort must be expected to produce performance, performance must be expected to produce outcomes, and those outcomes must be valued. If a project asks an employee to work harder but provides inadequate tools, expectancy is weakened. If performance is not recognized, instrumentality is weakened. If the reward has little value to the employee, valence is weakened.

Self-determination theory emphasizes autonomy, competence, and relatedness. Project leaders can support these needs by allowing appropriate discretion, providing development and feedback, and creating a sense of belonging. In knowledge-intensive projects, autonomy is especially important, but it must be balanced with coordination and safety requirements.

Motivation practices should be equitable and context-sensitive. Public praise may energize one person and embarrass another. Individual bonuses may undermine cooperation where success depends on joint work. A balanced approach recognizes contributions, supports learning, protects reasonable workloads, and connects daily work to the project’s purpose.

Leadership for Uncertainty and Delivery

Management coordinates plans, resources, and controls; leadership mobilizes people when plans are incomplete or conditions change. Project leadership is situational. Directive behaviour may be appropriate during a safety emergency or when a novice team faces a highly standardized task. Coaching is more suitable when capability is developing. Supporting behaviour is valuable when team members are competent but uncertain or discouraged. Delegation is appropriate when individuals or sub-teams possess the competence and commitment to act independently.

Transformational leadership emphasizes purpose, inspiration, intellectual stimulation, and individualized consideration. It can help teams embrace difficult change, but inspiration cannot replace sound planning or technical competence. Transactional leadership, based on clear expectations, monitoring, and contingent rewards, is useful for routine control and contractual commitments. Effective project managers combine both approaches.

Servant leadership emphasizes the leader’s responsibility to remove obstacles, develop people, and enable team performance. Ethical leadership adds honesty, fairness, accountability, and concern for affected stakeholders. In projects involving safety, environmental impact, public infrastructure, or sensitive data, ethical leadership is not optional. A leader must be willing to challenge unrealistic targets and stop unsafe work.

Leadership credibility is built through consistency. A project manager who demands transparency but hides bad news, or who promotes teamwork while rewarding individual blame, sends contradictory signals. Credibility also requires technical curiosity: the leader need not be the best specialist, but must ask informed questions and respect professional expertise.

Psychological Safety, Inclusion and Ethical Conduct

Psychological safety is the shared belief that people can raise questions, report mistakes, express disagreement, and offer ideas without fear of humiliation or retaliation. It does not mean that performance standards are absent. Rather, it enables learning and early risk detection while preserving accountability.

Project leaders support psychological safety by inviting dissent, responding constructively to bad news, separating people from problems, conducting learning-focused reviews, and ensuring that senior voices do not dominate every discussion. A practical meeting technique is to ask each function to identify one assumption, risk, or unresolved concern before decisions are finalized.

Inclusion requires more than demographic representation. It involves equitable access to information, participation, development, and influence. Time-zone patterns can exclude remote members; technical jargon can silence non-specialists; cultural norms may affect willingness to challenge authority. Leaders should rotate meeting times, circulate materials in advance, use clear language, and make decision processes visible.

Ethical resource management includes fair allocation, avoidance of discrimination, truthful reporting of capacity, respect for working-time limits, responsible use of contractors, and protection of health and safety. Managers should not manipulate resource estimates to secure approval or conceal overload. Professional codes and organizational policies may impose additional duties concerning confidentiality, conflicts of interest, procurement integrity, and environmental responsibility.

Conflict and Negotiation in Projects

Conflict is natural in projects because resources are scarce, objectives differ, and technical uncertainty produces competing interpretations. Conflict may concern goals, processes, roles, schedules, personalities, or values. Task conflict can improve decisions when managed respectfully; relationship conflict usually damages trust and performance.

A useful diagnostic sequence is to identify the parties, distinguish positions from interests, examine evidence and constraints, and determine whether the disagreement is substantive or relational. The position may be “we need the equipment by Monday,” while the underlying interest may be “we must protect the commissioning window and avoid idle labour.” Understanding interests creates more options.

The Thomas–Kilmann framework identifies competing, collaborating, compromising, avoiding, and accommodating styles. No style is universally best. Competing may be justified for urgent safety decisions; avoiding may be appropriate when emotions need to cool; accommodating may preserve a relationship on a low-value issue; compromising can provide a timely, partial solution; collaborating seeks an outcome that addresses the underlying interests of all parties.

Principled negotiation recommends separating people from problems, focusing on interests rather than positions, generating options for mutual gain, and using objective criteria. In project settings, objective criteria may include safety standards, verified capacity, contractual obligations, lifecycle cost, technical tolerances, or the approved schedule baseline.

Negotiation should occur at the lowest competent level, but escalation is necessary when authority is exceeded, safety is threatened, or unresolved conflict affects critical milestones. The project manager should document agreements, owners, dates, assumptions, and consequences. An informal agreement that is not recorded can become a future source of conflict.

Multicultural and Virtual Project Teams

Multicultural teams can generate creativity and broader market understanding, yet differences in communication style, hierarchy, time orientation, risk perception, and attitudes toward disagreement may cause misunderstanding. Cultural frameworks can provide useful hypotheses, but they should never be used to stereotype individuals. The leader must learn how each member prefers to communicate and make decisions.

Virtual teams face additional challenges: reduced informal interaction, delayed feedback, ambiguous availability, technology failures, and difficulty interpreting silence. Effective virtual leadership requires explicit operating agreements. These may specify core collaboration hours, response expectations, channels for urgent matters, documentation standards, meeting etiquette, and escalation procedures.

A virtual team should use asynchronous communication for information that does not require immediate discussion and synchronous meetings for decisions, complex problem solving, relationship building, and sensitive issues. A decision record should state the decision, rationale, participants, assumptions, owner, and review date. This reduces dependence on memory and informal hallway conversations.

Digital collaboration platforms, resource management systems, integrated schedules, skills databases, and dashboards can improve visibility. However, digital visibility is not the same as managerial understanding. Automated workload indicators may count hours without capturing cognitive complexity, interruptions, or hidden operational duties. Data should support dialogue, not replace it.

Artificial intelligence can assist with resource forecasting, schedule scenario analysis, skills matching, meeting summarization, and early identification of workload anomalies. Its use requires attention to data quality, privacy, bias, explainability, intellectual property, and human accountability. An AI recommendation to assign a person to a project should be reviewed for context and fairness rather than accepted automatically.

Applied Case: The Orion Packaging Line Project

Background

The Orion Packaging Line Project is an illustrative case concerning a food manufacturer introducing a high-speed automated packaging line. The project involves operations, engineering, quality assurance, procurement, information technology, finance, a machine supplier, and an external safety consultant. The approved completion date is tied to a seasonal demand increase.

Situation and Problem

Three months before commissioning, the project manager discovers that the controls engineer is committed to another plant, the installation contractor has proposed weekend work, and the quality team has not completed validation protocols. The production manager insists that the line must be available on the original date. Engineering argues that the date is technically unrealistic. Procurement reports that a critical sensor shipment may be delayed. Team meetings have become defensive, and operators are reluctant to report concerns because earlier warnings were dismissed.

Analysis

The problem is not one shortage but a system of interdependent constraints. The controls engineer represents a capability gap; weekend work increases fatigue and safety risk; incomplete validation threatens regulatory and quality approval; the sensor delay affects the commissioning sequence; and low psychological safety prevents accurate information from reaching decision makers.

The project manager maps activities against resource requirements and identifies the true critical interfaces. A resource histogram shows that engineering is overloaded during installation, while the quality team is underutilized until late in the schedule. A RACI review reveals that both the project manager and production manager believe they are accountable for the commissioning decision. The team charter is revised to establish decision rights and escalation rules.

Approach and Strategy

First, the steering committee approves temporary allocation of the controls engineer and authorizes a qualified external specialist as backup. Second, the team resequences work so that software simulation and documentation proceed before physical installation. Third, procurement develops an approved alternative sensor and obtains technical validation from engineering and quality. Fourth, the project manager rejects unlimited weekend work and introduces a fatigue and safety review for any extended shift.

The project manager holds a facilitated conflict meeting. Participants state interests rather than positions: operations needs reliable production availability, engineering needs adequate testing time, quality needs documented evidence, and finance needs control of the contingency budget. The group agrees on objective acceptance criteria and establishes a daily commissioning huddle.

To restore psychological safety, the project manager begins each huddle by asking for one new risk or assumption. Reports are thanked and investigated rather than punished. The team also adopts a decision log and a shared dashboard showing unresolved issues, owners, and due dates.

Outcome

The original date is retained, but the scope of the first production release is narrowed. Non-essential reporting features are deferred, while safety validation, quality approval, and core production functions remain mandatory. The alternative sensor is accepted after testing. Commissioning proceeds in controlled stages, and operators participate in trials before handover. The project experiences additional short-term coordination effort but avoids unsafe acceleration and gains stronger operational acceptance.

Learning Points

The case demonstrates that resource management is inseparable from leadership. Capacity analysis exposed the overload, but negotiation and governance created the solution. Clear accountability reduced organizational conflict. Psychological safety improved the quality of risk information. Finally, protecting mandatory quality and safety outcomes while deferring lower-value scope was more effective than simply demanding additional effort.

Challenges, Risks and Common Mistakes

Resource plans become unreliable when estimates are copied from previous projects without examining context, when productive hours are confused with paid hours, or when functional managers promise the same person to several projects. Other common mistakes include assigning people only by availability rather than competence, ignoring onboarding time, failing to plan knowledge transfer, and treating contractors as outside the team.

Managers may also overemphasize utilization. Very high utilization leaves no capacity for emergencies, learning, improvement, or coordination. A person shown as fully utilized may be unable to complete critical work because tasks are fragmented across many projects. Work-in-progress limits and explicit priorities are often more useful than maximizing individual occupancy.

Leadership risks include micromanagement, inconsistent decisions, favouritism, public blame, avoidance of difficult conversations, and excessive optimism in reporting. A project manager who suppresses bad news may appear successful until the project reaches a point where recovery is impossible. Conversely, a leader who escalates every minor issue weakens team autonomy and governance efficiency.

Resource decisions can also create ethical risks. Selective allocation of desirable assignments may disadvantage certain groups. Excessive overtime may transfer project risk to employees and their families. Personal data in skills or performance systems may be misused. Automated tools can reproduce historical bias if their training data reflects unequal opportunities. These risks require transparency, review, and human judgement.

Current Developments and Best Practices

Contemporary project organizations increasingly manage portfolios rather than isolated projects. Resource decisions therefore require portfolio-level prioritization, scenario planning, and visibility of cumulative demand. Skills-based planning is replacing purely departmental headcount planning, particularly where specialized digital, analytical, cybersecurity, sustainability, or automation skills are scarce.

Hybrid work is making asynchronous coordination, digital documentation, and outcome-based performance more important. At the same time, organizations are rediscovering the value of deliberate in-person interaction for trust building, complex design, and conflict resolution. The appropriate balance depends on task interdependence and team maturity rather than ideology.

Sustainable resource management considers energy, materials, travel, waste, worker welfare, and lifecycle consequences. Project leaders should include sustainability criteria in procurement and design decisions rather than treating them as an afterthought.

Effective practice can be summarized as follows:

1. Plan resources from work packages and interfaces, not from broad headcount assumptions.

2. Distinguish capacity, capability, availability, and productivity.

3. Make accountability and decision rights explicit.

4. Review resource demand at portfolio and project levels.

5. Protect realistic workloads and safety margins.

6. Build cross-functional norms before major conflict emerges.

7. Use motivation, coaching, and recognition appropriate to individual and team needs.

8. Encourage early reporting of risk and treat learning as a performance responsibility.

9. Negotiate through interests and objective criteria.

10. Use digital and AI tools transparently, with human oversight and data protection.

11. Close projects by capturing lessons, recognizing contributions, and planning people’s transition.

Chapter Summary

Project performance depends on the coordinated use of physical resources, human capability, organizational authority, and leadership behaviour. Effective resource planning identifies requirements, time-phases demand, compares it with realistic capacity, and resolves gaps through prioritization, rescheduling, procurement, outsourcing, or scope decisions. Resource histograms, calendars, responsibility assignment matrices, and capacity calculations support these decisions.

Functional, projectized, matrix, and hybrid structures distribute authority differently, making governance and decision rights essential. Cross-functional teams develop through changing stages and require both task systems and relationship management. Motivation is strengthened when people experience achievement, recognition, autonomy, competence, fairness, and connection to purpose.

Project leadership combines direction, coaching, support, ethical judgement, and the ability to act under uncertainty. Psychological safety improves learning and risk visibility, while inclusive practices help multicultural and virtual teams collaborate effectively. Conflict should be diagnosed and negotiated through interests, objective criteria, and documented agreements. Digital platforms, analytics, and AI can improve resource visibility and forecasting, but they cannot replace managerial judgement, ethical accountability, or human conversation.

Key Terms

Resource management: Planning, acquiring, allocating, developing, and controlling project resources.

Capacity: The amount of work that can realistically be undertaken during a specified period.

Capability: The knowledge, skill, experience, authority, and behavioural ability required to perform work.

Resource calendar: A record of the periods when people, equipment, facilities, or materials are available.

Resource breakdown structure: A hierarchical classification of project resources by type, skill, department, location, or source.

Resource histogram: A time-based display of resource demand and allocation.

Resource leveling: Adjusting activity timing to resolve resource over-allocation, often with schedule impact.

Resource smoothing: Adjusting activities within available float to improve resource use without changing the completion date where possible.

RACI matrix: A responsibility tool identifying who is Responsible, Accountable, Consulted, and Informed.

Functional organization: An organizational structure in which authority is primarily held by departments.

Projectized organization: A structure in which personnel and authority are organized substantially around projects.

Matrix organization: A structure in which project and functional managers share authority.

Psychological safety: A shared belief that people can speak up, question, report errors, and disagree without fear of humiliation or retaliation.

Cross-functional team: A team whose members represent multiple professional or organizational disciplines.

Expectancy theory: A motivation theory linking effort, performance, outcomes, and the value attached to those outcomes.

Transformational leadership: Leadership that builds commitment through purpose, inspiration, intellectual stimulation, and individualized consideration.

Conflict of interests: A situation in which parties’ objectives, priorities, interpretations, or needs are incompatible or appear incompatible.

Principled negotiation: Negotiation focused on interests, objective criteria, options for mutual gain, and separation of people from problems.

Virtual team: A team whose members collaborate across geographical locations primarily through digital communication.

Portfolio resource management: Coordinating resource priorities and capacity across multiple projects and operational commitments.

Review Questions

Short Answer Questions

1. Distinguish between resource capacity and resource capability.

2. What is the purpose of a resource calendar?

3. Explain one difference between resource leveling and resource smoothing.

4. What does psychological safety mean in a project team?

5. Identify the four roles represented in a RACI matrix.

Long Answer Questions

1. Explain how a project manager can translate a work breakdown structure into an integrated resource plan.

2. Compare functional, projectized, and matrix organizations, including the principal advantages and tensions of each.

3. Discuss the relevance of Herzberg’s, expectancy, and self-determination theories to project team motivation.

4. Explain how project leaders can build and maintain effective cross-functional teams.

5. Describe a structured approach to conflict diagnosis and principled negotiation in projects.

Analytical / Application Questions

1. A project requires 900 hours of specialist work over six weeks, but practical available capacity is 720 hours. Analyse at least four possible responses and explain the trade-offs among them.

2. In a virtual multinational project, members remain silent during meetings but later challenge decisions through private messages. Diagnose the likely leadership, cultural, and communication issues and propose corrective actions.

3. A project sponsor demands the original deadline despite a shortage of qualified commissioning staff. Using resource, leadership, ethical, and governance concepts from this chapter, recommend a defensible course of action.

22. Multiple Choice Questions with Answers

Question 1

A project team has six analysts available for four weeks at 30 hours per week, but 20% of time is unavailable for meetings, leave, and coordination. What is the practical capacity?

A. 576 hours

B. 600 hours

C. 720 hours

D. 864 hours

Correct Answer: A. 576 hours

Question 2

Which action most directly represents resource smoothing?

A. Adding permanent staff to the project

B. Changing activities within available float to reduce peaks in resource demand

C. Increasing the project budget without changing the schedule

D. Replacing all specialists with generalists

Correct Answer: B. Changing activities within available float to reduce peaks in resource demand

Question 3

In a RACI matrix, the person who is answerable for the result is identified as:

A. Responsible

B. Accountable

C. Consulted

D. Informed

Correct Answer: B. Accountable

Question 4

Which organizational structure most commonly involves shared authority between project and functional managers?

A. Functional

B. Projectized

C. Matrix

D. Single-purpose

Correct Answer: C. Matrix

Question 5

A team member says that working harder will not improve performance because the required software is unavailable. Which element of expectancy theory is weakened?

A. Valence

B. Instrumentality

C. Expectancy

D. Equity

Correct Answer: C. Expectancy

Question 6

Which behaviour best supports psychological safety?

A. Punishing the first person who reports a problem

B. Avoiding disagreement to preserve harmony

C. Thanking people for raising risks and investigating them constructively

D. Allowing only senior managers to speak during reviews

Correct Answer: C. Thanking people for raising risks and investigating them constructively

Question 7

A project manager asks two departments to explain their underlying needs before discussing solutions. This approach is most consistent with:

A. Principled negotiation

B. Avoidance

C. Competing behaviour

D. Unilateral decision making

Correct Answer: A. Principled negotiation

Question 8

Which practice is most appropriate for a multicultural virtual team?

A. Relying entirely on informal communication

B. Allowing each member to use undocumented processes

C. Establishing explicit communication, response-time, and decision-recording norms

D. Scheduling all meetings at the project manager’s preferred time

Correct Answer: C. Establishing explicit communication, response-time, and decision-recording norms

Question 9

Why can adding people to a late project fail to improve performance?

A. Additional people always reduce quality

B. Coordination and onboarding costs may exceed the benefit of added labour

C. Late projects cannot use specialists

D. Project schedules are never affected by resources

Correct Answer: B. Coordination and onboarding costs may exceed the benefit of added labour

Question 10

An AI tool recommends assigning an employee to a project based on historical performance data. What is the most appropriate managerial response?

A. Accept the recommendation automatically

B. Ignore all AI recommendations

C. Review the recommendation for context, fairness, privacy, and human factors

D. Use the recommendation only if it reduces salary costs

Correct Answer: C. Review the recommendation for context, fairness, privacy, and human factors