Pop-Culture Project Management Fundamentals: Waterfall&Agile

Introduce project management in module 1, inviting reflection on everyday projects, and explain the goal to understand what product management is while exploring future methodologies.

trace the history of project management from ancient builders to the 1950s formal discipline, then compare waterfall and agile, highlighting the 2001 Agile Manifesto and delivering value incrementally.

Explore how a project is a temporary, unique endeavor to produce a product, service, or result, guided by the PMBOK and PMI through initiate, plan, execute, monitor, and close.

Explore the core of project management through PMI and the PMBOK guide, mastering goal setting, scope, constraints, budget, and schedule with agile and waterfall approaches across software and construction.

Examine the project drivers—time, scope, and cost—and their symbiotic relationship in achieving project success. Learn how meeting agreements and delivering agreed features lead to customer satisfaction and on-schedule, on-budget delivery.

Explore standard waterfall plan-driven project roles across executive, management, and associate levels, detailing steering teams, sponsors, customers, the PMO, functional managers, project managers, core team members, and SMEs.

Explore the executive, managerial, and associate agile roles—product manager, product owner, scrum master, agile coach, and development team—and their responsibilities from backlog to sprint ceremonies.

Explore the project management life cycle from initiation to closure, detailing planning, execution, and monitoring and controlling, with waterfall and agile perspectives illustrated by a blockbuster movie.

Explore the project management lifecycle, from initiation and planning to executing, closing, and realizing, with emphasis on stage approvals and model variations aligned to organization.

Identify a business need and project idea, assess feasibility, define scope and deliverables, identify stakeholders, and build a business case and SOW to authorize the project.

Monitor and control project progress by tracking effort and cost, identifying deviations, and implementing changes to keep work on track with the original plan.

Explain the closure phase by delivering final deliverables, releasing resources, and evaluating project success against goals and budget. Assess team performance, document closure, and capture lessons learned for future projects.

Pivot to the agile development lifecycle and drive iterative sprints of 1 to 4 weeks from ideation to deployment, featuring constant feedback, collaboration, and continuous improvement.

Define the beginning of a project with a charter that states purpose, scope, and objectives, aligning stakeholders, risks, and success criteria through Avengers, Star Trek, and Game of Thrones analogies.

A project charter acts as an informal contract between the project team and the sponsor, a living document that authorizes the project manager to proceed and to plan the project.

Identify and describe the key elements of a project charter, including title, scope overview, business case, background, milestone schedule, risks, assumptions, constraints, resources, stakeholders, team principles, and signatures.

Explore agile project chartering vs waterfall, using an informal charter and product roadmap, with product owner approval, release and iteration, and definition of done.

Explore project structure, culture, and roles using pop culture analogies from starship, Simpsons, and Avengers to show how clear roles and a balanced culture drive project success.

Explore how functional organizations group people by specialization and how a functional manager controls budgets and project communications. Learn the advantages and disadvantages of this structure.

Explain the projectized organization: a project manager controls budgets and personnel with unified command and fast communication, while weighing cost impacts and potential loss of lessons learned.

Explore how organizational culture shapes project outcomes by influencing values, rituals, ethics, communication, cooperation, decision-making, and how people are treated, rewarded, and organized across internal and multi-organization projects.

Explore waterfall plan-driven project roles, behaviors, and skills, from evaluating fit and requirements to sequential execution, strict documentation, risk management, and quality assurance.

Explore agile project roles and behaviors, including product managers and owners prioritizing user needs, market insights, and vision, with scrum masters acting as servant leaders enabling collaboration and continuous improvement.

Lead and develop project teams by building shared purpose, trust, and clear communication. Pop culture examples illustrate adaptability, collaboration, and leveraging diverse skills to deliver a plan.

Explore how project managers guide teams through forming, storming, norming, performing, and adjourning to enhance competencies, interaction, and overall performance per the PMBOK.

Lead agile teams through transformational, servant, and developmental leadership, sharing vision, removing obstacles, and fostering collective ownership, pair programming, openness, courage, and respect with scrum master support for continuous improvement.

Develop skills to manage project teams by assigning tasks and roles, tracking performance, giving feedback, resolving issues, and using legitimate, reward, and expert power to optimize outcomes.

Define, control, and verify project scope through scope planning. Apply sequential planning and data-driven analysis to prioritize resources under budget constraints, illustrated by Back to the Future and Moneyball.

Plan scope management teaches defining project and product scope, setting boundaries, and avoiding scope creep, with real-life examples like buying a car, planning a vacation, and cooking dinner.

Collect and translate project requirements by capturing the voice of the customer, identifying stakeholder needs, and tracing them to measurable specifications to guide tradeoffs and success.

Define the scope by translating stakeholder needs into a project scope statement that specifies deliverables, acceptance criteria, work to be done, boundaries, and constraints to prevent scope creep.

Master change control by establishing a formal process, the integrated change control system, and managing the baseline and change requests to minimize disruptions and keep projects on track.

Waterfall vs agile scope planning, detailing requirements, who leads (project manager vs product owner), work breakdown structure, backlogs, work packages, user stories, personas, and how changes are handled.

Explore budgeting for projects through estimating costs, allocating resources, and tracking progress. Use comic book examples like Stark Industries, Shield, and the Justice League to illuminate budgeting concepts.

Develop and refine a cost management plan for planning costs, including cost estimating, budgeting, baselines, and cost control to align with the parent organization and inform project decisions.

Develop cost estimates by applying fixed vs variable, direct vs indirect, and recurring vs nonrecurring costs, using analogous, parametric, and bottom-up methods within rolling wave planning to guide budgets.

Explore how uncertain events can impact project progress, positively or negatively, using Jurassic Park and the Simpsons monorail as pop culture examples to illustrate project risk.

Plan risk management by defining activities, success measures, and a risk management plan that addresses threats, opportunities, risk premium, and mitigation through contracts and agreements.

Explore risk response strategies, build contingency plans for tech glitches, and update the risk register with probability, impact, and quantitative analyses to safeguard schedules, budgets, and communications.

Compare waterfall and agile risk planning, showing early risk assessment in both, agile detail through iterations, daily stand-ups, and retrospectives, and the role of risk alerts and stakeholder coordination.

Learn how project closure marks the final phase of the life cycle, ensuring work meets plan and gains stakeholder approval, illustrated by local cleanups, fundraisers, and home renovations.

Examine the anatomy of project closure in the final phase. Review deliverables, quality, and outcomes with stakeholders, then craft a transition plan, capture lessons learned, and produce closeout reports.

Compare waterfall and agile project closure, emphasizing agile scope validation at each iteration with early stakeholder feedback, versus waterfall’s end-of-project validation and lessons learned.