Lecture 1: Introduction to Advanced Project Management

Introduction to Project Management

• Definition of a Project: A temporary endeavor undertaken to create a unique product, service, or result (PMI, 2021)
• Project Management: The application of knowledge, skills, tools, and techniques to project activities to meet project objectives (PMBOK Guide)
• Projects differ from operations, which are ongoing and repetitive.
• Core elements of project success: scope, time, cost, and quality (known as the Iron Triangle, developed by Martin Barnes, 1969)
• Project management involves balancing competing demands: stakeholder expectations, resource constraints, and risks

Key terms: Project, Iron Triangle

The Project Lifecycle

• Projects follow a lifecycle that describes distinct phases: Initiation, Planning, Execution, Monitoring & Control, Closure.
• Creating project deliverables is central to each phase.
• Initiation should define clear objectives, constraints, and stakeholders.
• Planning involves detailed scheduling, budgeting, and risk analysis.
• Execution is about performing activities to generate project outputs.

Key terms: Project Lifecycle

Key Methodologies: Waterfall

• The Waterfall model emphasizes linear, sequential stages (Winston W. Royce, 1970)
• Each stage must be completed before the next one begins.
• Widely used in construction, manufacturing, and traditional software development.
• Strengths: Clear structure, straightforward planning, ideal for projects with stable requirements.
• Weaknesses: Rigid process makes it less adaptable to changing needs.

Key terms: Waterfall Model

Key Methodologies: Agile

• Agile methodology promotes iterative development cycles and flexibility (Agile Manifesto, 2001)
• Focuses on delivering small, incremental improvements (sprints) rather than completing everything at once.
• Prioritizes collaboration, adaptability, and customer involvement.
• Common frameworks include Scrum, Kanban, and Extreme Programming (XP).
• Strengths: Emphasizes adaptability and responsiveness to change.

Key terms: Agile Manifesto

Organizational Context in Project Management

• Projects must align with organizational strategy and objectives
• Project managers operate within the constraints of the organizational culture
• Governance structures influence project decision-making and reporting
• Stakeholder interest and power analysis are key to project success
• Organizational resources, such as budgeting and staffing, impact project feasibility

Key terms: Mendelow’s Matrix

Risk Management in Projects

• Risk management involves identifying, assessing, mitigating, and monitoring risks
• The Risk Register is essential for tracking risks throughout the lifecycle
• Quantitative analysis uses methods like Monte Carlo simulation or Expected Monetary Value (EMV)
• Qualitative analysis categorizes risks based on likelihood and impact using tools like risk matrices
• Risk response strategies include avoidance, mitigation, transfer, and acceptance

Key terms: Monte Carlo Simulation, Risk Register

Team Dynamics and Leadership in Project Management

• Effective project teams require diversity in skills and perspectives
• Bruce Tuckman’s model (1965) outlines stages of team formation as Forming, Storming, Norming, Performing, and Adjourning
• Leadership styles like transformational, transactional, and servant leadership affect team motivation
• Conflict management techniques include collaboration, compromise, and accommodation
• Clear communication channels prevent misunderstandings and enhance productivity

Key terms: Tuckman’s Model, Transformational Leadership

Effective Communication in Project Management

• Communication accounts for over 80% of a project manager’s time (PMBOK Guide, 7th Edition).
• Key stakeholders must be identified and informed throughout project execution.
• Effective communication channels differ between Waterfall and Agile methodologies.
• Project managers must develop strategies to manage conflicts arising from miscommunication.
• Technological tools such as Slack, Trello, and MS Teams streamline project communication for distributed teams.

Key terms: Stakeholder Engagement, Conflict Resolution

Resource Allocation and Optimization

• Resource allocation involves distributing tasks, manpower, budget, and materials appropriately.
• Tools like Resource Levelling ensure that resources are not overworked or underutilized.
• The Critical Path Method (CPM) identifies key activities that directly affect project timelines.
• Time, cost, and scope—the triple constraints—dictate trade-offs in resource allocation (PMI).
• Agile methodology facilitates iterative resource adjustment; Waterfall locks resources during planning stages.

Key terms: Critical Path Method (CPM), Triple Constraints

Monitoring and Control Systems

• Monitoring progress ensures projects remain on track with planned objectives.
• Earned Value Management (EVM) provides metrics for cost and schedule performance.
• Key Performance Indicators (KPIs) vary depending on project context, e.g., delivery rate vs budget utilization.
• Control systems prevent scope creep by enforcing original project parameters.
• Agile leverage frequent sprint reviews as iterative control mechanisms to identify deviations early.

Key terms: Earned Value Management (EVM), Scope Creep

Advanced Concepts: Stakeholder Management in Projects

• Stakeholders are individuals or groups with an interest or impact on the project.
• The Stakeholder Salience Model (Mitchell, Agle, and Wood, 1997) categorizes stakeholders based on power, legitimacy, and urgency.
• Stakeholder analysis involves identifying, prioritizing, and engaging stakeholders effectively.
• Strategies include stakeholder mapping, interest-impact matrices, and communication plans.
• Managing stakeholder expectations requires regular updates, feedback, and resolving conflicts.

Key terms: Stakeholder Salience Model, Interest-Impact Matrix

Practical Applications: Case Study in Project Management

• Case studies provide a real-world lens to project management frameworks and methodologies.
• The Sydney Opera House project faced schedule overruns and budget escalation, providing lessons in risk and expectation management.
• Applying the Agile methodology transformed Spotify from a struggling platform to a global market leader.
• Leadership lessons from NASA’s Apollo Program highlight effective resource coordination and stakeholder alignment.
• Post-mortem analysis of failed projects like the Challenger disaster teach the value of robust risk and communication protocols.

References

• PMI (2021) A Guide to the Project Management Body of Knowledge (PMBOK Guide). 7th edn. Newtown Square: Project Management Institute.
• Barnes, M. (1969) 'The Iron Triangle of Project Management', Official PMI Conference Paper, Project Management Institute.
• Royce, W.W. (1970) 'Managing the Development of Large Software Systems', Proceedings of IEEE WESCON, Los Angeles, California.
• Beck, K. et al. (2001) 'Manifesto for Agile Software Development', Agile Alliance.
• Mendelow, A.L. (1981). 'Environmental Scanning: The Impact of Stakeholder Concept', ICIS Proceedings.
• Kerzner, H. (2022). Project Management: A Systems Approach to Planning, Scheduling, and Controlling. 13th edn. Hoboken: Wiley.
• PMBOK Guide (2021). A Guide to the Project Management Body of Knowledge, 7th edn. PMI.
• Tuckman, B.W. (1965). 'Developmental Sequence in Small Groups', Psychological Bulletin, 63(6), pp. 384–399.
• Bass, B.M. (1985). Leadership and Performance Beyond Expectations. New York: Free Press.
• Project Management Institute (2021). PMBOK Guide – Seventh Edition.
• Shore, J. and Warden, S. (2007). The Art of Agile Development. Sebastopol: O'Reilly Media.
• Kerzner, H. (2017). Project Management: A Systems Approach to Planning, Scheduling, and Controlling. Hoboken: Wiley.
• Fleming, Q.W., and Koppelman, J.M. (2016). Earned Value Project Management. Hoboken: Wiley.
• Mitchell, R.K., Agle, B.R., and Wood, D.J. (1997) 'Toward a Theory of Stakeholder Identification and Salience: Defining the Principle of Who and What Really Counts', Academy of Management Review, 22(4), pp. 853–886.
• Flyvbjerg, B. (2005) 'Design by Deception: The Politics of Megaproject Approvals', Journal of Planning Education and Research, 24(3), pp. 356-369.
• Cohen, D.J., Lindvall, M., and Costa, P. (2004) 'An Introduction to Agile Methods', Advances in Computers, 62, pp. 67–97.