Agile Scrum Project Management
Ancient wisdom says: plan the work, then throw the plan away. Scrum turns chaos into sprints, meetings into ceremonies, and Post-it notes into strategy. From backlog grooming to burndown charts — learn to ship fast and blame no one.
52
Lessons
7
Modules
4
Levels
1
Agile Foundations
8 lessons- 1 What is Agile? The Manifesto and Principles The Agile Manifesto, its four values, twelve principles, and why seventeen developers on a mountain changed software forever.
- 2 Waterfall vs Agile: When and Why Comparing sequential and iterative approaches — and knowing which one fits your project.
- 3 Overview of Agile Frameworks Scrum, Kanban, XP, SAFe — surveying the Agile landscape and choosing your framework.
- 4 Empiricism: Transparency, Inspection, Adaptation The three pillars of empiricism that form the philosophical foundation of Scrum.
- 5 The Five Scrum Values Commitment, Focus, Openness, Respect, and Courage — the behavioral foundation of Scrum.
- 6 Complex vs Complicated: The Cynefin Framework Understanding the Cynefin domains and why Scrum is designed for complexity, not complication.
- 7 Agile Mindset: Fixed vs Growth How mindset shapes a team's ability to adopt Agile — and why "we've always done it this way" is the most dangerous sentence.
- 8 Common Agile Anti-Patterns ScrumBut, Cargo Cult Agile, and other ways teams sabotage their own Agile adoption.
2
Evidence-Based Management
7 lessons- 1 What is EBM? Goals and Experimentation Evidence-Based Management: using experiments and data to drive decisions, not gut feelings and long meetings.
- 2 Strategic, Intermediate, and Tactical Goals Three levels of goals that connect daily Sprint work to organizational vision — without the dreaming.
- 3 Current Value (CV): Stakeholder Satisfaction Measuring how happy your users are right now — because "probably fine" is not a metric.
- 4 Unrealized Value (UV): The Satisfaction Gap The gap between what users want and what you deliver — your biggest opportunity or your biggest threat.
- 5 Ability to Innovate (A2I): Technical Health Technical debt is like credit card debt — measuring your capacity to innovate before debt eats it all.
- 6 Time to Market (T2M): Speed of Delivery How fast you go from idea to production — and where to find the hidden waste slowing you down.
- 7 Using EBM to Improve: Hypotheses and Experiments Turning gut feelings into hypotheses, and hypotheses into measurable experiments.
3
Kanban for Scrum Teams
7 lessons- 1 Kanban Definition and Principles What Kanban really means: a strategy for optimizing flow, not just sticky notes on a board.
- 2 Flow Metrics: WIP, Cycle Time, Throughput The four flow metrics that tell you how fast (or slow) your team really delivers.
- 3 Little's Law and WIP Limits The mathematical proof that doing less at once means finishing faster — and how to set WIP limits.
- 4 The Kanban Board: Visualizing Workflow How to design and use a Kanban board that actually helps your team — not just looks pretty.
- 5 Definition of Workflow The team agreement that defines how work flows — without it, your board is abstract art.
- 6 Active Management of Work in Progress WIP limits alone are not enough — you must actively manage the items flowing through your system.
- 7 Flow-Based Events in Scrum How to use flow data in every Scrum event — from Sprint Planning to Retrospective.
4
Real-World Agile
6 lessons- 1 Agile in Non-Software Domains Scrum is not just for coders — marketing, HR, education, and even construction teams use it.
- 2 Remote and Distributed Scrum Teams The biggest challenge of remote Scrum is not technology — it is trust.
- 3 Agile Contracts and Fixed-Price Projects The impossible triangle: fixed scope, time, and price. Agile says fix two, flex one.
- 4 Technical Practices: CI/CD, TDD, Pair Programming Without good engineering practices, Scrum is just a well-organized disaster.
- 5 Organizational Agility and Culture Change One team doing Scrum is easy. Making the whole org agile? Culture fights back.
- 6 Preparing for Professional Scrum Certification PSM I, PSPO I, PSK I — exam scope, tips, and one brutal fact: only 50% pass.
5
Scrum Artifacts and Commitments
8 lessons- 1 Product Backlog: Ordering for Value The Product Backlog is not a to-do list — it is a value-ordered ranking. The top item is the most valuable, not the most urgent.
- 2 The Product Goal: North Star The Product Goal answers one question: "What are we building?" If everyone has a different answer, you are in trouble.
- 3 Writing Effective User Stories and PBIs "As a user, I want the system to not crash." That is not a User Story — that is common sense. Learn to write real PBIs.
- 4 Sprint Backlog: The Plan for the Sprint The Sprint Backlog is the Developers' plan, not the PO's orders. It is alive — adjusted daily based on the Daily Scrum.
- 5 The Sprint Goal as Commitment The Sprint Goal gives flexibility — as long as it is met, individual PBIs can be negotiated. Without it, every PBI is a deadline.
- 6 The Increment: Usable and Valuable The Increment is a done, usable product version. Not "almost usable" — usable RIGHT NOW, delivered to the hands of users.
- 7 Definition of Done: Quality Gate DoD is the minimum quality bar. If your DoD is "code is written," your standard is like "rice is cooked" — technically correct but far from good.
- 8 Estimation: Story Points, T-Shirt, #NoEstimates Estimation is not a commitment — it is a conversation starter. If your boss converts story points to hours, your system is already broken.
6
Scrum Events
8 lessons- 1 The Sprint: Timebox for Value A Sprint is a fixed-length timebox — not "done when it's done" but "stop when time's up." The heartbeat of Scrum.
- 2 Sprint Planning: What & How Sprint Planning answers three questions: Why is this Sprint valuable? What can we do? How will we do it?
- 3 The Sprint Goal: Focus and Commitment A Sprint without a Sprint Goal is a journey without a destination — romantic but impossible to report progress on.
- 4 Daily Scrum: Inspect and Adapt 15 minutes daily. Not a status report — it's a team self-inspection. If everyone reports to the SM, you're doing it wrong.
- 5 Sprint Review: Inspect the Increment Sprint Review is not a demo show. It's inviting stakeholders to inspect, give feedback, and adapt the Backlog.
- 6 Sprint Retrospective: Continuous Improvement The Retro is Scrum's most important ceremony — and the most commonly skipped. "Too busy for retros" is exactly why you need one.
- 7 Facilitating Effective Scrum Events Good facilitation produces results. Bad facilitation makes people want to quit. Master silence, timers, and sticky notes.
- 8 When Events Go Wrong: Troubleshooting Planning ran 4 hours with no conclusion? Daily became a 45-minute marathon? Retro and nobody talks? Diagnose and fix.
7
Scrum Roles and Accountability
8 lessons- 1 The Scrum Team: No Hierarchies The Scrum Team structure: no bosses, no titles, only accountabilities — and why that changes everything.
- 2 The Product Owner: Maximizing Value The Product Owner is THE single owner of the product. Two POs means two directions — which is no direction.
- 3 The Scrum Master: Servant Leader The Scrum Master is not a rebranded project manager — they are a coach, impediment remover, and guardian of Scrum.
- 4 The Developers: Cross-Functional & Self-Managing In Scrum, Developers are everyone who creates the Increment — not just coders. They self-manage how to do the work.
- 5 Product Owner vs Project Manager PM manages timelines and budgets. PO manages value and priority. Confusing them is like asking a sushi chef to fry rice.
- 6 Scrum Master Anti-Patterns Helicopter SM, Secretary SM, Invisible SM — the common ways Scrum Masters accidentally undermine Scrum.
- 7 Stakeholder Management in Scrum Stakeholders always want more than you can deliver. The PO's job is saying "no" — in a way that sounds like "later."
- 8 Scaling: Multiple Teams, One Product One product, one Product Backlog, one PO — regardless of how many teams. Multiple backlogs means parallel universes, not Scrum.