Project Org & HR: Teams, Roles, Conflict & Motivation

Key Concepts and Definitions

Project Organization Structures

Project organizations define how teams are structured, roles are assigned, and communication flows. Three primary structures exist:

Key Differences:

Human Resource Management in Projects

Recruitment and Team Building

Recruitment involves selecting the right talent for the project. Key steps:

1. Needs Assessment: Identify skills gaps (e.g., a Daraz project needing DevOps engineers).
2. Sourcing: Use internal databases or external platforms (e.g., LinkedIn, local job fairs).
3. Selection: Technical interviews, case studies (e.g., simulating a Kathmandu traffic routing algorithm for a logistics project).
4. Onboarding: Training and integration into the team.

Example: eSewa’s recruitment for its digital payment platform required:

• Frontend developers (for UI/UX).
• Backend engineers (for payment processing).
• QA testers (for security compliance).

Team Building and Conflict Resolution

Teams are the backbone of projects. Conflict arises due to:

• Role ambiguity (e.g., unclear responsibilities in a matrix structure).
• Resource constraints (e.g., shared developers between projects).
• Cultural differences (e.g., remote teams in Nepal vs. overseas).

Conflict Resolution Techniques:

1. Collaborating: Work together to find a solution (best for win-win scenarios).
2. Compromising: Find a middle ground (e.g., splitting tasks between two developers).
3. Forcing: One party imposes their solution (risky; avoid unless critical).
4. Avoiding: Delay resolution (not recommended for long-term projects).

Example: At Ncell, a conflict arose between the network expansion team and the customer support team over prioritization. The project manager used collaborating to align both teams on a phased rollout plan.

Motivation Theories in Project Teams

Maslow’s Hierarchy of Needs

Maslow proposed a pyramid of needs that motivate individuals:

stateDiagram-v2
    [*] --> Physiological : "Unmet"
    Physiological --> Safety : "Met"
    Safety --> Social : "Met"
    Social --> Esteem : "Met"
    Esteem --> SelfActualization : "Met"
    SelfActualization --> [*] : "Fully Met"

Application in Projects:

• Physiological: Ensure fair salaries (e.g., NTC pays competitive rates for telecom engineers).
• Social: Team-building activities (e.g., Pathao’s hackathons).
• Esteem: Recognize contributions (e.g., "Employee of the Month" at Daraz).

Herzberg’s Two-Factor Theory

Herzberg identified hygiene factors (dissatisfiers) and motivators:

• Hygiene Factors: Salary, company policies, working conditions (e.g., ergonomic setups at NEPSE).
• Motivators: Achievement, recognition, growth (e.g., promoting a junior developer to lead a module at Khalti).

Example: At a Nepali bank, developers were dissatisfied due to outdated tools (hygiene factor). Introducing modern IDEs (motivator) boosted morale.

McGregor’s Theory X and Theory Y

• Theory X: Assumes employees dislike work and need micromanagement (e.g., traditional NTC management).
• Theory Y: Assumes employees are self-motivated and seek responsibility (e.g., agile teams at Pathao).

Example: A Theory Y approach at eSewa allowed developers to choose their tech stack, increasing productivity.

Real-World Applications

1. eSewa’s Cross-Functional Teams

Idea Used: Matrix Organizational Structure

• How: eSewa’s payment platform team includes:
  • Backend: Handles transactions (Node.js/Python).
  • Frontend: UI/UX (React Native).
  • Security: Compliance (PCI-DSS).
• Challenge: Balancing functional department goals (e.g., IT security) with project deadlines.
• Solution: Weekly syncs between functional managers and project leads.

2. Pathao’s Agile Teams

Idea Used: Projectized Structure + Theory Y Motivation

• How: Pathao’s delivery app teams are fully dedicated to specific features (e.g., real-time tracking).
• Motivation: Developers are given autonomy to innovate (e.g., integrating AI for route optimization).
• Result: Faster iterations and higher employee satisfaction.

3. NTC’s Network Expansion Project

Idea Used: Conflict Resolution + Resource Histogram

• Scenario: Delayed due to conflicts between civil engineers (tower installation) and telecom engineers (signal testing).
• Solution:
  1. Visualized resource usage (see below) to identify bottlenecks.
  2. Collaborative planning to overlap tower construction and signal testing.

4. Daraz’s Supplier Coordination

Idea Used: Stakeholder Management

• Scenario: Daraz’s logistics team needed to coordinate with 100+ suppliers for a Black Friday sale.
• Approach:
  • RACI Matrix to clarify roles (Responsible, Accountable, Consulted, Informed).
  • Weekly standups to resolve conflicts (e.g., delayed shipments from Kathmandu suppliers).

Worked Example: Team Conflict at a Nepali Bank

Scenario: A bank’s loan processing software project faced delays due to conflicts between:

• Business Analysts (wanted user-friendly forms).
• Developers (prioritized backend efficiency).

Steps to Resolve:

1. Identify Root Cause: Survey revealed analysts felt ignored in design reviews.
2. Apply Collaborating Technique:
   • Joint workshops to align on requirements.
   • Shared success metrics (e.g., "90% user satisfaction + 100% processing speed").
3. Outcome: Reduced rework by 30%, and the project was completed on time.

Exam Tip

1. Diagrams Are Key:
   • Draw organizational structure diagrams (functional/matrix/projectized).
   • Sketch resource histograms or Gantt charts for resource management questions.
2. Theories Must Be Linked to Examples:
   • For Maslow’s hierarchy, relate to salary (physiological) → recognition (esteem) in Nepali IT firms.
   • For Herzberg, contrast hygiene factors (e.g., NTC’s old tools) vs. motivators (e.g., Pathao’s autonomy).
3. Conflict Resolution Questions:
   • Expect scenario-based questions. Use the collaborating technique for win-win solutions.
4. Real-World Tie-Ins:
   • Mention eSewa (matrix), Pathao (projectized), or NTC (functional) in answers to score extra marks.
5. Formulas to Remember:
   • Payback Period (though not in this unit, often paired with HR questions): $$\text{Payback Period}=\frac{\text{Initial Investment}}{\text{Annual Cash Flow}}$$
   • ROI (from past exams): $$\text{ROI}=\frac{\text{Net Profit}}{\text{Initial Investment}}\times 100\%$$
   • Break-Even Point (BEP): $$\text{BEP (units)}=\frac{\text{Fixed Costs}}{\text{Selling Price per Unit}-\text{Variable Cost per Unit}}$$