CAPM Certification: Agile, Scrum & Hybrid

Shift from "command and control" to "empower and adapt." This lecture explores the foundational philosophy of the Agile Manifesto. You will learn to distinguish between "Doing Agile"—the mere use of tools—and "Being Agile" through a mindset focused on human interaction, working solutions, and customer collaboration. We break down the Four Core Values and Twelve Principles, ensuring you can navigate the "Agile Umbrella" of frameworks with the decision-aware precision required for the CAPM exam.

Choose the right lifecycle for your project’s unique environment. Using the Stacey Matrix, we map technical and requirements uncertainty to determine when to use Waterfall (Predictive), Agile, or Hybrid approaches. This lecture resolves common confusion between iterative (refining) and incremental (building) delivery. You will master "Keyword Strategies" to identify project signatures in exam scenarios—from stable, blueprint-driven environments to evolving, feedback-heavy software developments—ensuring you always select the most effective delivery model.

Master the "checks and balances" of the Scrum framework. We redistribute traditional project management authority into three specific roles: the Product Owner (Value), the Scrum Master (Process), and the Developers (Execution). Learn why there is no "Project Manager" in pure Scrum and how the team operates as a small, self-organizing unit of ten or fewer. This lecture provides an "Accountability Split" guide to help you identify roles in exam scenarios based on their specific technical responsibilities.

Establish the "heartbeat" of your project through five timeboxed events. Within the container of a Sprint, you will explore the technical mechanics of Sprint Planning, the Daily Scrum, Sprint Review, and the Sprint Retrospective. We resolve the "status meeting" trap by clarifying that the Daily Scrum is for the Developers, not the manager. Master the "Timebox Logic" and learn to distinguish between inspecting the product (Review) and improving the process (Retrospective) to ensure continuous adaptation.

Build transparency and trust through physical evidence of progress. This lecture details the three Scrum artifacts—Product Backlog, Sprint Backlog, and Increment—and their three essential commitments: Product Goal, Sprint Goal, and the Definition of Done. You will learn to link each artifact to its specific promise of quality or strategy. We also explore the use of Task Boards to visualize work in real-time, helping teams remain decision-aware and identify bottlenecks before they derail the iteration.

Optimize your project’s flow by moving from "push" to "pull." Kanban uses visual signboards to manage work as a continuous stream rather than fixed timeboxes. The core of this lecture is the Work in Progress (WIP) Limit—the technical engine that prevents "logjams" and forces the team to finish work before starting new tasks. You will learn to measure effectiveness through Lead Time and Cycle Time, and understand how Kanban can be integrated into hybrid environments to manage sub-team execution.

Replace rigid specifications with dynamic conversations. We break down the technical format of the User Story—Role, Action, and Benefit—and the "Three Cs" of Card, Conversation, and Confirmation. Learn to apply the INVEST filter to ensure stories are high-quality and the DEEP criteria to maintain a healthy Product Backlog. Most importantly, this lecture resolves the "Value vs. Work" confusion, teaching you to distinguish between User Stories (business value) and Tasks (technical steps) for the exam.

Bridge the gap between a prioritized backlog and immediate execution. In this lecture, teams transition from the "what" to the "how" through decomposition and commitment. We resolve the vital confusion between Velocity (past performance) and Capacity (current availability). You will also learn the technical "exit gate" for an Increment: the Definition of Done. We address common exam traps, such as the difference between a "Done" increment and the business decision to "Release" it.

Master the art of guessing with technical precision. Human beings are better at relative comparison than absolute guessing; we leverage this through Story Points and the Fibonacci Sequence. This lecture covers collaborative techniques like Planning Poker and T-Shirt Sizing, alongside prioritization models like MoSCoW and Kano. Finally, we dismantle the "Velocity Trap," explaining why Story Points belong exclusively to the team that created them and cannot be used for external productivity competitions.

Agile is not "process-free"—it is a disciplined integration of risk and quality into the daily rhythm. Learn to use "Technical Spikes" to fail fast and "Risk-Adjusted Backlogs" to attack uncertainty early. We explore how the Product Owner acts as the Change Control Board, welcoming change as a competitive advantage while protecting the current Sprint Goal. You will also learn to use Cumulative Flow Diagrams to spot delivery risks and maintain built-in quality through the Definition of Done.

No project exists in a vacuum. Tailoring is the deliberate act of adjusting your management approach to fit the unique project ecosystem. This lecture explores the hybrid spectrum, from "Predictive-Heavy" to "Agile-Heavy" models. We detail technical strategies like Agile-Predictive Sub-projects and Sequences, where the project manager acts as the "Integrator". You will learn to manage the "Macro-Schedule" milestones while respecting the agile team's "Micro-Schedule" autonomy.

Leadership in agile is about responsibility for the environment, not the people. This lecture defines the Scrum Master as the quintessential servant leader, focusing on shielding the team from noise and removing impediments. We resolve the confusion of the leader as a "Boss" or "Secretary"—they are actually a facilitator and coach. You will learn core characteristics like listening, empathy, and foresight, and how to apply these supportive behaviors in exam-based scenario questions.

Use data as a technical health indicator, not a tool for punishment. We cover essential metrics including Velocity for capacity forecasting and Sprint Burndown charts for visualizing work remaining. Learn why Burnup charts are the superior tool for identifying scope creep and how Kanban flow metrics like Lead and Cycle Time highlight bottlenecks. This lecture provides the "Metric Purpose" rule to help you match the right chart to the right project need.

Implement technical "quality gates" to ensure professional delivery. The Definition of Ready (DoR) acts as the entry gate, ensuring work is actionable before entering a Sprint. The Definition of Done (DoD) is the exit gate, guaranteeing universal quality and completeness for the Increment. We resolve the confusion between Acceptance Criteria (story-specific) and the DoD (universal standard). Learn why you can cautiously "bend" the DoR but must never "break" the DoD to maintain organizational standards.

The Retrospective is the "engine of evolution" for any agile team. This final event of the Sprint focuses on inspecting the process, people, and tools to plan actionable improvements. We provide a five-stage framework—from "Setting the Stage" to "Closing"—and resolve the difference between a real-time agile Retrospective and predictive "Lessons Learned". You will learn the importance of Psychological Safety and the "Prime Directive" in creating a transparent, high-performing collaborative unit.