Field Based Assignment 1

Question 1

Elaborate the project management scope of the following terms:

a) Authority
In project management, authority refers to the formal power vested in a project manager or leader
to make decisions, allocate resources, assign tasks, and enforce rules within the project
environment. It is a critical aspect of leadership and ensures that the project runs smoothly
without delays caused by indecision. Authority legitimizes the project manager’s position and
allows them to coordinate between stakeholders effectively.

Key aspects of authority include:

 Decision-making power: The authority to approve plans, budgets, and schedules.

 Resource allocation: The right to assign manpower, finances, and materials.

 Conflict resolution: Authority to settle disputes between team members or departments.

 Leadership: Ensures that team members respect instructions and follow project
direction.

 Reward Authority: The power to recommend or provide rewards (e.g., bonuses,

recognition, desirable assignments, promotions) for team members who meet or exceed
expectations.

 Penalty (Coercive) Authority: The power to enforce discipline or recommend penalties

for non-performance (e.g., negative feedback, removal from the project, withholding
bonuses). This should be used judiciously.

 Expert Authority: Power derived from the PM's own knowledge, skills, experience, and
certifications (e.g., PMP, technical expertise). Team members are more likely to follow
someone they respect for their competence.

 Referent Authority: Power that comes from the PM's personal attributes, charisma, and
the strength of their professional relationships. People follow because they like, respect,
and identify with the PM.

For example, in a road construction project, the project manager has authority to assign site
engineers to specific sections, approve procurement requests, and adjust the schedule in case of
delays. Without authority, project managers cannot implement their responsibilities effectively.

b) Responsibility
Responsibility is the obligation to perform assigned duties to the best of one’s ability and ensure
that the expected outcomes are achieved. In project management, responsibilities are distributed
among the project team to ensure accountability and efficiency.
Key elements include:

 Role clarity: Each team member is given specific tasks that align with their skills.

 Ownership: Individuals take personal commitment to deliver quality results.

 Delegation: Managers distribute responsibilities fairly to avoid overburdening.

 Alignment with objectives: Responsibilities ensure all efforts contribute toward project
goals.

 Formal Acceptance: The individual or group must formally understand and accept the
responsibility. This creates a psychological contract and commitment to the task.

 Adherence to Standards: The responsible party is obligated to perform the work

according to agreed-upon standards, methodologies, quality requirements, and codes of
conduct.

 Resource Management: Responsibility includes the duty to use assigned resources

(budget, time, materials) wisely and efficiently to complete the task.

For instance, in a building project, an architect may be responsible for drawings, a site engineer
for supervision, and procurement officers for sourcing materials. Responsibility ensures
accountability and prevents overlap or neglect of work.

c) Accountability
Accountability refers to being answerable for the results of assigned tasks. While responsibility
focuses on “who does what,” accountability focuses on “who is held answerable.” In project
management, accountability ensures transparency and performance tracking.

Aspects include:

 Performance evaluation: Results are compared against expectations.

 Transparency: All actions and decisions can be traced to responsible individuals.

 Discipline: Accountability reduces negligence and encourages seriousness.

 Trust: It builds confidence among stakeholders that project leaders will deliver as
promised.

 Results-Oriented: Accountability is not about performing tasks (that's responsibility) but

about ensuring those tasks lead to the desired, measurable results. It's about the "what"
(the deliverable met its specs) rather than just the "how" (the task was completed).

 Measurement Against Benchmarks: Accountability is measured against predefined

benchmarks and success criteria, such as the project baseline (scope, schedule, cost),
quality standards, and key performance indicators (KPIs).
  Answering to Stakeholders: Accountability means being answerable to stakeholders
(e.g., the sponsor, customer, senior management) for the project's performance, including
its successes, failures, and the use of resources.

For example, if a project manager assigns a civil engineer the responsibility of site supervision,
the engineer is accountable for ensuring construction adheres to safety standards and approved
designs. If something goes wrong, the engineer must explain the failure and suggest corrective
measures.

d) Chain of Command/Scalar Chain

The chain of command, or scalar chain, is the formal line of authority that flows from the top
management to the lowest level of staff. It establishes reporting relationships and ensures that
communication moves in a structured way.

Key features:

 Hierarchy clarity: Defines who reports to whom.

 Communication efficiency: Instructions are passed down clearly, while feedback moves
upward.

 Conflict reduction: Helps avoid confusion about roles and authority.

 Decision control: Maintains order and discipline in the project.

 Unity of Command: A core principle related to the chain of command is that each team
member should report to only one direct supervisor. This prevents confusion, avoids
conflicting priorities, and ensures clear accountability.

 Flow of Authority: The chain of command is the pathway through which authority is
delegated downward. A project sponsor grants authority to the project manager, who then
delegates specific authority to team leads, and so on.

 Structured Escalation Path: The scalar chain provides a predefined and agreed-upon
path for resolving issues. If a team member cannot resolve a problem, they escalate it to
their project manager. If the project manager cannot resolve it, they escalate it to the
sponsor, and so on.

For example, in a large engineering project, a site worker reports to a foreman, the foreman
reports to a site engineer, who reports to the project manager, who then reports to the sponsor.
This avoids confusion that may arise if instructions come from multiple uncontrolled directions.

e) Span of Control
The span of control refers to the number of subordinates directly supervised by one manager. In
project management, this influences efficiency, supervision quality, and communication flow.

 Wide span of control: A manager supervises many employees. It reduces hierarchy

levels but can make supervision weaker.
  Narrow span of control: A manager supervises fewer employees. It allows close
monitoring but may create bureaucracy.

 Balance: The ideal span depends on the project’s complexity, employee skill level, and
nature of work.

For instance, in a construction project, if a site engineer directly supervises too many workers,
mistakes may go unnoticed. A balanced span ensures that workers are adequately guided while
avoiding excessive managerial overhead.

Question 2

The project manager is the central figure responsible for integrating all aspects of a project to
ensure its successful delivery. They act as the visionary, strategist, and executor, translating
stakeholder needs into tangible deliverables. Their role is a complex blend of hard skills in
management and soft skills in leadership; all aimed at navigating the project from conception to
closure.

Duties and responsibilities include:

1. Initiation and Planning

o Defining Project Scope: Working with the client (e.g., property developer) and
architects to formally define the project's objectives, deliverables, and boundaries
to create a clear Project Charter.

o Developing Detailed Work Plans: Creating comprehensive project management

plans that cover scope, schedule, cost, quality, resources, communication, risks,
and procurement.

o Scheduling: Breaking down the project into manageable tasks using a Work
Breakdown Structure (WBS), forecasting realistic timelines, sequencing tasks
(e.g., foundation before framing), and developing a master schedule using Gantt
charts and critical path method (CPM) tools.

2. Team Leadership and Supervision

o Acquiring and Assigning Talent: Selecting and assigning roles to general

contractors, subcontractors, and internal team members based on their specific
expertise (e.g., electrical, plumbing, structural engineering).

o Motivating and Building Collaboration: Fostering a positive, safety-first site

culture, resolving conflicts between different trade teams, and ensuring all crews
are aligned and working towards the common goal.

o Providing Direction and Supervision: Conducting daily site meetings, providing

clear instructions, and ensuring every team member understands their tasks and
responsibilities.
3. Resource and Procurement Management

o Allocating Resources: Efficiently managing the deployment of manpower,

machinery (e.g., cranes, excavators), and materials (e.g., concrete, steel) to avoid
idle time or shortages.

o Procurement: Overseeing the bidding process, selecting and managing suppliers

and subcontractors, and ensuring all materials and services (e.g., concrete
delivery, glass façade installation) are procured on time and to specification to
prevent project delays.

o Controlling Costs: Vigilantly tracking resource usage to prevent wastage and

control project costs.

4. Risk Management

o Proactive Identification: Systematically identifying potential risks such as

weather delays, supply chain disruptions, design flaws, safety hazards, or
unforeseen site conditions (e.g., unstable soil).

o Developing Mitigation Strategies: Creating contingency plans, such as securing

alternate suppliers, scheduling weather-dependent tasks for optimal seasons, and
implementing rigorous safety protocols.

o Continuous Monitoring: Regularly reviewing the risk register throughout the

project's lifecycle and adapting plans as new risks emerge.

5. Communication and Reporting

o Acting as the Central Hub: Serving as the primary communication bridge

between the client, architects, engineers, contractors, regulatory inspectors, and
community representatives.

o Preparing Progress Reports: Providing regular, transparent updates on status,

budget, and schedule to stakeholders through structured reports and meetings.

o Ensuring Smooth Information Flow: Facilitating clear and timely communication

between all parties to prevent misunderstandings, errors, and rework.

6. Quality and Compliance Control

o Ensuring Standards are Met: Guaranteeing that all construction work meets the
specified architectural plans, building codes, quality standards, and safety
regulations.

o Conducting Inspections: Coordinating with quality inspectors and third-party

agencies to conduct evaluations at critical milestones (e.g., pre-pour concrete
inspection, post-frame inspection) before work proceeds to the next stage.
 7. Budget Control and Financial Management

o Monitoring Expenditure: Continuously tracking all project expenditures (labour,

materials, equipment) against the approved budget and forecasting final costs.

o Managing Cash Flow: Approving invoices, managing change orders, and

implementing cost-control measures to prevent and address cost overruns.

8. Stakeholder Engagement and Expectation Management

o Negotiating and Managing Relationships: Engaging in negotiations with clients,

contractors, and suppliers to align interests and resolve disputes.

o Managing Expectations: Proactively communicating with the client and future

tenants to keep them informed of progress and manage their expectations
regarding the final product.

9. Monitoring, Evaluation, and Control

o Tracking Performance: Using Key Performance Indicators (KPIs) like Earned

Value Management (EVM), schedule variance, and cost variance to objectively
measure progress.

o Taking Corrective Action: Implementing corrective measures immediately when

the project deviates from the plan, such as re-allocating resources to get back on
schedule or value-engineering to reduce costs.

10. Project Closure and Handover

o Finalizing all Activities: Overseeing the punch-list process to ensure all minor
defects are corrected, obtaining a certificate of occupancy from the local
authority, and preparing final project reports and as-built drawings.

o Conducting Handovers: Formally handing over the completed building keys and
all documentation to the client or facility management team.

o Conducting Lessons-Learned Sessions: Facilitating a meeting with the entire

project team to document what went well, what could be improved, and how to
apply these lessons to future projects.

Example: In the construction of a new commercial office building, the project manager is
responsible for ensuring the general contractor and all subcontractors deliver work on time,
within the allocated budget, and according to the architectural and engineering specifications.
They are also responsible for handling permit issues with the city council, managing community
concerns about noise and traffic disruptions, and ensuring the worksite adheres to strict health and
safety standards to protect all workers.

Question 3
As an experienced Project Manager, how would you motivate your human capital so as to
curb work-related stress?

Human capital is the backbone of any project, and their motivation determines overall
productivity. Stress is common in project environments due to tight deadlines, dynamic
workloads, and high-stakes pressure. An experienced project manager applies a combination of
empathetic leadership and practical strategies to sustain motivation and significantly reduce stress
levels:

• Clear Goal Setting: Precisely defining project expectations, key deliverables, and
individual responsibilities reduces ambiguity, prevents confusion, and minimizes anxiety.
Utilizing SMART goals (Specific, Measurable, Achievable, Relevant, Time-bound)
ensures everyone understands their role and how it contributes to the project’s success.

• Recognition and Rewards: Regularly celebrating both individual and team

achievements—whether through public acknowledgment, performance bonuses, or non-
monetary incentives—boosts morale, reinforces positive behaviour, and cultivates a
supportive and appreciative work culture.

• Training and Development: Providing access to relevant workshops, certifications,

and skill-upgrading opportunities empowers team members to execute their tasks more
efficiently and confidently. This reduces stress related to skill gaps and enhances overall
competence and job satisfaction.

• Open Communication: Encouraging transparent, honest, and frequent dialogue

through regular check-ins, feedback sessions, and an open-door policy allows employees
to voice concerns, share ideas, and address issues early before they escalate into major
stressors.

• Work-life Balance: Actively promoting flexible working hours, remote work options
(where feasible), and encouraging regular breaks and time off helps prevent burnout and
supports mental and physical well-being, leading to more sustained productivity.

• Delegation of Tasks: Fairly distributing the workload based on individual strengths and
capacities, while ensuring no one is overburdened, promotes equity and prevents
exhaustion. Effective delegation also involves trusting team members with autonomy,
which increases engagement and reduces micromanagement stress.

• Stress Management Programs: Introducing structured wellness initiatives such as on-

site meditation sessions, yoga classes, access to counselling services, or partnerships with
mental health professionals provides employees with tools to manage stress proactively.

• Team-building Activities: Organizing regular informal gatherings, team outings, or

collaborative workshops strengthens interpersonal relationships, builds trust, improves
cooperation, and diffuses workplace tension, creating a more cohesive and resilient team.
 • Supportive Leadership: Demonstrating empathy, approachability, and a solutions-
oriented mindset helps build a psychologically safe environment. By actively listening,
showing understanding, and advocating for the team’s needs, a project manager can
foster loyalty and reduce anxiety.

For example, in a construction project, a project manager can reduce stress by implementing
rotating shifts to avoid fatigue, providing advanced safety training to enhance confidence and
reduce accident-related anxiety, and rewarding outstanding workers with public recognition or
financial allowances to reinforce high performance and dedication.

Question 4

Outline the factors that are responsible for a project failure.

Despite careful planning, many projects fail due to a combination of internal missteps and
external pressures. These factors often interlink, creating a domino effect that derails project
objectives. Common causes include:

1. Poor Planning

o Insufficient detail: Lack of a comprehensive, detailed project plan that outlines

all activities, dependencies, and milestones leads to chaos, inefficiency, and
missed deadlines.

o Unrealistic scheduling: Creating timelines without input from the team doing
the work or without considering potential setbacks sets the project up for failure
from the start.

o Inadequate baseline: Failing to establish a clear baseline for scope, time, and
cost makes it impossible to measure progress or identify variances.

2. Unclear Objectives

o Vague or shifting goals: Goals that are not Specific, Measurable, Achievable,
Relevant, and Time-bound (SMART) confuse the team and create misalignment.

o Lack of alignment: Project objectives that are not aligned with the
organization's strategic goals result in a lack of executive support and eventual
cancellation.

o Ambiguous success criteria: Without a clear definition of what constitutes

"success," the project can be completed but still be considered a failure by
stakeholders.

3. Inadequate Resources

o Shortage of skilled manpower: Insufficient, untrained, or over-allocated team

members hinder progress and compromise quality.
 o Financial constraints: Under-budgeting or inconsistent funding streams halt
project activities and demotivate the team.

o Technology gaps: Lack of access to appropriate tools, software, or equipment

cripples the team's ability to execute tasks effectively.

4. Weak Leadership

o Ineffective project managers: Managers who fail to coordinate tasks, resolve

conflicts, motivate the team, or advocate for necessary resources create a
directionless and disengaged environment.

o Lack of decision-making: Indecisive leadership leads to paralysis, delays, and

missed opportunities to correct the project's course.

o Absence of sponsorship: A disengaged or weak project sponsor fails to provide

top-level support, remove organizational obstacles, and secure ongoing funding.

5. Poor Communication

o Misunderstandings and assumptions: Inconsistent or absent communication

between the team, stakeholders, and leadership causes errors, rework, and delays.

o No communication plan: Failure to define who needs what information, when,

and how leads to information silos and misinformed decision-making.

o Ignoring feedback: Not creating channels for or listening to feedback from the
team and end-users results in a product that does not meet needs.

6. Scope Creep

o Uncontrolled changes: Allowing frequent, unvetted changes in project

requirements without adjusting the budget, timeline, or resources increases cost,
extends schedules, and leads to team burnout.

o Poor change management: Lack of a formal Change Control Board (CCB) and
process for evaluating and approving change requests means the project's original
objectives become blurred and unachievable.

7. Lack of Stakeholder Engagement

o Ignoring key stakeholders: Failing to identify, analyse, and engage important

stakeholders throughout the project lifecycle leads to unmet expectations,
reduced buy-in, and ultimately, project rejection upon delivery.

o Managing expectations: Not proactively managing stakeholder expectations

results in surprises and dissatisfaction, even if the project is delivered on time and
budget.
 8. Ineffective Risk Management

o Failure to anticipate: Not proactively identifying, analysing, and planning for

potential risks leaves the project vulnerable to costly and disruptive events.

o No contingency plans: Absence of fallback plans or risk response strategies

means the team is reactive rather than proactive when issues inevitably arise.

9. Technology Failures

o Use of unproven technology: Implementing bleeding-edge technology that is

unreliable or not yet fully developed introduces significant technical risk and can
lead to system failures.

o Outdated systems: Relying on legacy systems that are incompatible with new
project requirements or are prone to failure disrupts execution and integration
efforts.

10. Cultural and Environmental Barriers

o Resistance to change: Organizational culture that is resistant to new processes

or the project's output can actively sabotage adoption and success.

o External factors: Unfavourable government policies, regulatory changes,

economic shifts, or community opposition can halt a project regardless of internal
performance.

o Geographical distribution: Challenges of managing teams across different time

zones and cultures can lead to communication breakdowns and coordination
problems.

11. Poor Monitoring and Evaluation

o Lack of regular tracking: Failing to use Key Performance Indicators (KPIs) and
hold regular progress reviews means deviations from the plan are only noticed
when it is too late to correct them.

o Ineffective reporting: Status reports that do not provide accurate, timely, and
actionable information prevent informed decision-making by leadership.

Example: A housing project may fail if the initial budget is drastically underestimated
(Inadequate Resources) and the scope continuously expands with client requests without formal
approval (Scope Creep), leading to incomplete structures and bankruptcy. Similarly, a software
project may collapse due to reliance on an outdated and unsupported framework (Technology
Failures) compounded by a team that was never trained to use it (Inadequate Resources) and a
project manager who failed to escalate these critical issues (Weak Leadership).