Class Introduction
This was a Project Management Foundation training session led by Naz, covering essential project management concepts and terminology. Naz explained the fundamental differences between predictive (plan-driven) and agile (adaptive) project lifecycles, emphasizing that predictive projects have fixed scope, time, and cost while agile delivers business value incrementally with variable scope and fixed time/cost. The session covered the importance of business value alignment with organizational strategy, the role of Project Management Offices (PMOs) as expert departments that can function in supportive, controlling, or directive capacities, and the hierarchical relationship between projects, programs, and portfolios. Naz also discussed organizational structures, explaining how project managers' authority varies from zero power in functional organizations to full authority in projectized organizations, with metrics organizations falling between these extremes in a balance, weak, or strong matrix approach.
Project Management Foundation Training
Naz conducted a training session on Project Management Foundation, explaining key concepts including project definitions, lifecycle approaches, and business value alignment. He discussed the importance of need assessment and business case analysis before project initiation, emphasizing that projects should deliver business value to justify funding and organizational resources. The session covered two main lifecycle approaches: predictive (plan-driven/waterfall) and agile (adaptive), with Naz explaining how each handles scope changes through formal change requests and plan revisions.
Project Lifecycle Methods Overview
Naz explained the differences between predictive, agile, and hybrid project lifecycles, emphasizing that in predictive lifecycle scope cannot be changed without stakeholder approval, while in agile the scope is variable within fixed time and cost constraints. Naz described how hybrid lifecycle combines elements of both approaches, with the project manager responsible for delivering the hybrid product. The discussion concluded with an introduction to PMO (Project Management Office) as a department within an organization that provides expert advice on various project aspects.
PMO Types and Organizational Structures
Naz explained the different types of PMOs (Project Management Offices) and their roles within organizations. He described three types of PMOs: supportive, controlling, and directive, with varying levels of authority over projects. Naz also discussed the hierarchy of project management structures, from individual projects to programs to portfolios, and explained the differences between functional, matrix, and projectized organizational structures. He emphasized how these structures affect the power and authority of project managers within organizations.
Related Offerings
Organizational Structures in Project Management
Naz explained the differences between functional and projectized organizations, emphasizing that in functional organizations, the project manager has minimal power while in projectized organizations, the project manager has significant decision-making authority. He discussed various organizational structures including hybrid and virtual teams, using a real example of a museum project completed through virtual collaboration with international consultants. Naz stressed the importance of focusing on exam questions rather than trying to memorize specific answers, and explained that project management principles should be tailored to each project's unique requirements rather than applying them universally.
Project Management Methodologies Overview
Naz explained the key concepts of project management, focusing on stakeholders, development approaches, and the differences between predictive and agile methodologies. He emphasized that in predictive lifecycle, planning is done upfront, while in agile, planning is adaptive and iterative. Naz also discussed the agile triangle, where scope is variable while time and cost are fixed, and explained how agile teams prioritize delivering higher business value throughout the project.
Agile Development Methodology Overview
Naz explained the Agile development methodology, covering its core principles including iterative development, collaboration, self-organizing cross-functional teams, and the four Agile values of individual and interaction over processes, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan. Naz emphasized that Agile teams should be small (6-9 people ideally, maximum 12), work collaboratively through interactive communication, and focus on delivering working software frequently through iterations not exceeding 4 weeks. The discussion highlighted how Agile promotes sustainable development through regular working hours rather than extended site work, with teams able to adapt to changes even at the last moment of a project.
Agile Principles and Ceremonies
Naz explained Agile principles and practices, focusing on the four ceremonies or meetings in an iteration: planning, review, retrospective, and feedback. He discussed the difference between iterative and incremental Agile approaches, where iterative focuses on perfect delivery at the end while incremental delivers working software after each iteration. Naz also mentioned the importance of business acumen in the new exam format, which focuses 26% on business environment questions.
Strategic Alignment in Project Management
Sri Sathya Sankar discussed the importance of strategic alignment in project management, using Qatar's Vision 2030 as an example to illustrate how projects must support an organization's overall goals and vision. He explained that project managers should seek guidance from the PMO when working in new environments and emphasized the value of leveraging historical project data for similar projects to inform cost estimates and other planning activities.
PMP Exam Concepts Overview
Naz explained the concepts of Organizational Process Asset (OPA) and Enterprise Environmental Factors (EEF) in project management. He emphasized that while historical project information (OPA) provides a valuable reference, it must be customized based on current enterprise factors (EEF) which can include internal or external conditions that have changed since the original project. Naz also discussed upcoming changes to the PMP exam format, including new paragraph-based questions that require careful time management during the exam. The session concluded with Naz announcing that the next class might be rescheduled due to personal commitments, and he encouraged participants to review the shared materials and ask questions via WhatsApp group.
Ready to strengthen your project management skills and prepare for the PMP exam?
