PM - Agile Methodology

Here is a summary of the key topics covered in the video:

• Definition of Agile: Agile is a project management methodology centered on flexibility, collaboration, and customer centrality. It uses an iterative development model, working in cycles that allow for regular adaptation and feedback.
• Origin and Waterfall Comparison: Created in 2001 by 17 software developers who wrote the Agile Manifesto, Agile addresses the limitations of traditional, rigid Waterfall methods that follow a strict sequence (requirements $\to$ design $\to$ implementation) where changes mid-project are difficult.
• Key Benefits:
  • Customer Satisfaction: Delivers products aligned with actual user needs through continuous feedback.
  • Collaboration: Fosters ongoing communication among team members and stakeholders.
  • Speed & Flexibility: Enables faster product releases and continuous planning, debunking the myth that Agile lacks planning.
• 4 Core Values of the Agile Manifesto:
  1. Individuals and interactions over processes and tools.
  2. Working software over comprehensive documentation.
  3. Customer collaboration over contract negotiation.
  4. Responding to change over following a plan.
• 12 Principles & Key Features: Supported by 12 principles, Agile focuses on early/continuous delivery, welcoming change, self-organizing teams, and three main features: customer-centricity, collaboration, and flexibility.
• Scrum Framework: A structured framework for applying Agile principles, built around Sprints (2- to 4-week time-boxed cycles aiming to produce a shippable product increment).
• Scrum Roles:
  • Product Owner: Manages the product backlog and prioritizes user stories.
  • Scrum Master: A servant leader who facilitates events and removes blockers.
  • Development Team: A cross-functional, self-organizing group that executes the work.
• Scrum Artifacts:
  • Product Backlog: Master list of all potential project work.
  • Sprint Backlog: Specific list of items selected for the active sprint.
  • Burndown Charts: Visual tools showing daily remaining work.
• Scrum Ceremonies:
  • Sprint Planning: Sets goals for the upcoming sprint.
  • Daily Stand-Up: Quick check-in to surface obstacles.
  • Sprint Review: Showcases completed work to stakeholders.
  • Sprint Retrospective: Allows the team to discuss internal process improvements for future cycles.

See also:

• PM - Introduction — foundational project management concepts including the five-phase lifecycle and organizational structures.
• From Cogs to Collaboration - The Evolution of Management Thought — traces the historical evolution from classical hierarchies to modern agile frameworks.
• The Ultimate Project Management Jargon Lexicon — defines Agile, Scrum, sprints, and other key project management terminology.
• Every Business Is a Software Business - Core Frameworks and Enterprise Transformation — explores how agile, continuous delivery, and Scrum underpin software-driven business transformation.
• Projects vs Operations in Project Management - Key Differences and Examples — contrasts the temporary nature of projects with ongoing operations.
• Te Āpiti Wind Farm - A Case Study in Risk Management and Infrastructure Resilience — a real-world case study in agile project execution under disaster conditions.