01Agile foundations Days 1–10

You'll know what Agile is for, when it fits the work, and how light your process can be.

Team session guide →

  1. 01Measure what shipped, not what met.Agile that ships. Not Agile that meets.
  2. 02Over, not instead of.Four values. Still radical.
  3. 03Make it visible. Look often. Change course.Decide on what you see.
  4. 04Fit the method to how work arrives.Fit the method to the work.
  5. 05Thin, whole, useful. Then better.Build it in slices.
  6. 06Known path: plan it. Unknown path: iterate it.Waterfall isn't evil.
  7. 07Match the method to the problem. Agile for complex.What kind of problem is this?
  8. 08Limit the load. Clarify how teams work together.Design teams for flow.
  9. 09Compliance in every sprint, not at the end.Compliance is a requirement.
  10. 10Keep what helps. Drop what doesn't.Small team. Light process.

02Scrum done right Days 11–20

You'll run Scrum events that each end in a decision, with one clear backlog behind them.

Team session guide →

  1. 11Three accountabilities. Five events. Three artifacts. That's it.Scrum on one page.
  2. 12Why, what, how. In that order.Why, what, how. In that order.
  3. 13One sentence. One outcome. Room to flex.One sentence. One outcome.
  4. 14Plan the day. Toward the goal. In fifteen.Not a status meeting.
  5. 15Working software. Real people. Real feedback.A review, not a recital.
  6. 16One change. Owned. Checked next time.Retros that change something.
  7. 17Serve the team. Change the system.Coach, not secretary.
  8. 18One backlog. One order. One accountable person.One backlog. One voice.
  9. 19Refine the top. Two sprints ahead. Little and often.Little and often.
  10. 20Spot one pattern. Fix one pattern. Repeat.Six ways Scrum goes wrong.

03Kanban & flow Days 21–30

You'll see where work gets stuck and finish more by starting less.

Team session guide →

  1. 21Map the work as it is, not as it should be.You can't fix what you can't see.
  2. 22Stop starting. Start finishing.Stop starting. Start finishing.
  3. 23Four numbers tell you how work really flows.Four numbers that matter.
  4. 24Customers feel lead time. Teams control cycle time.Fast for you. Slow for them.
  5. 25Want it faster? Start less.Want it faster? Start less.
  6. 26If everything's urgent, nothing is.Not all work is equally urgent.
  7. 27Old work is a warning. Act before it's late.Old work is a warning.
  8. 28Parallel bands: healthy. Widening band: bottleneck.One chart. The whole story.
  9. 29Based on data. Used every day.Answer “when?” before they ask.
  10. 30Blend on purpose. Not by drift.Blend on purpose.

04Backlog & requirements Days 31–40

You'll write stories that are small, testable and clear about what done means.

Team session guide →

  1. 31Card, conversation, confirmation.A story is a promise to talk.
  2. 32Six checks for a story worth building.Six checks for a good story.
  3. 33Examples first. Written together. Tested for real.Agree what done looks like.
  4. 34Slice vertically. Every slice usable.Slice it vertically.
  5. 35See the whole journey. Release the thinnest path.See the whole journey.
  6. 36A guide for talking, not a gate for blocking.Ready, or blocked?
  7. 37Done means usable. Written down. Every time.Done means done.
  8. 38One question. A timebox. A decision.Buy knowledge, not code.
  9. 39Triage fast. One backlog. Close honestly.Triage fast. Close honestly.
  10. 40Explain the why. Keep it visible. Pay as you go.Pay down debt as you go.

05Estimation & forecasting Days 41–50

You'll give dates as honest ranges, based on your own history.

Team session guide →

  1. 41Estimates are guesses. Treat them like it.Estimates are guesses.
  2. 42The conversation is the value. The number isn't.Points aren't hours.
  3. 43Big gaps are gold. Small gaps don't matter.The gaps are the gold.
  4. 44Count the work. Keep it small. Still forecast.Count, don't estimate.
  5. 45Velocity plans. It doesn't measure worth.Planning tool. Not a scoreboard.
  6. 46Give a range and a confidence. Let them choose the risk.A range, not a promise.
  7. 47Your history is your best forecaster.Let your history forecast.
  8. 48Fix the date or the scope. Never both.Fix the date or the scope.
  9. 49Early numbers are wide. Narrow them by learning.Early numbers are wide.
  10. 50Ranges, reasons, regular updates. Bad news early.Bad news early.

06Delivery management Days 51–60

You'll manage dependencies, risks and reporting so problems surface early.

Team session guide →

  1. 51Own the flow of delivery, not the people doing it.Own the flow, not the people.
  2. 52Map them. Remove what you can. Plan the rest.The best dependency is the one you removed.
  3. 53Short, owned, reviewed weekly.Short, owned, reviewed.
  4. 54Risks need owners before they become issues.Might happen, or happening?
  5. 55Headline, forecast, decisions. One page.Headline first. Decisions next.
  6. 56Answer questions people actually ask.Answer real questions.
  7. 57Add one, drop one. Show the impact.Add one. Drop one.
  8. 58Fund in stages. Stop when value stops.Fund in stages.
  9. 59Contract for collaboration, not for blame.Contract for collaboration.
  10. 60Say it early. Choose deliberately. Stopping is an option.Say it early.

07Engineering practices Days 61–70

You'll release small changes often, without trading speed for stability.

Team session guide →

  1. 61Small changes. Automated checks. Boring releases.Make releases boring.
  2. 62Merge small. Merge often. Hide with flags.Merge small. Merge often.
  3. 63Small, fast, kind, and about what matters.Small, fast, and kind.
  4. 64Many fast tests. Few slow ones.Many fast. Few slow.
  5. 65Build it together. Run it together.One team. One outcome.
  6. 66Speed and stability rise together.Speed and stability.
  7. 67Fewer environments. Regular trains. Masked data.Fewer queues. Regular trains.
  8. 68Fix the system, not the person.Fix the system, not the person.
  9. 69Know the interest. Pay the expensive debt first.Know the interest.
  10. 70Close to the code. Reviewed like code. Used for real.Docs that stay true.

08Scaling Days 71–80

You'll know when to scale, how to plan across teams, and what to remove first.

Team session guide →

  1. 71Scale last. Simplify first.Scale last. Simplify first.
  2. 72Cross-team blockers. Short, focused, frequent.Short, focused, cross-team.
  3. 73Borrow what solves your problem. Skip the rest.Borrow, don't buy whole.
  4. 74One product. One backlog. Many teams.More with less.
  5. 75Copy the principles, not the org chart.Copy principles, not org charts.
  6. 76Commit to objectives, not every story.Plan together. Adapt together.
  7. 77Plan in the room. Vote on confidence.Plan in the room.
  8. 78Start fewer. Finish more. At every level.Limit WIP at the top, too.
  9. 79Outcomes, not outputs. Aligned, not cascaded.Outcomes, not outputs.
  10. 80Add slowly. Remove regularly.Every quarter, remove something.

09Teams & coaching Days 81–90

You'll build teams where bad news travels fast and people own their decisions.

Team session guide →

  1. 81Stable teams. Give them time to form.Teams take time.
  2. 82Make bad news safe to say early.Make bad news safe.
  3. 83Clear boundaries. Real authority inside them.Clear boundaries. Real authority.
  4. 84Clear purpose. Every voice. Decisions out.Every voice. Decisions out.
  5. 85Choose how you handle it. Don't just react.Fight about ideas, early.
  6. 86Know which hat. Ask more than you tell.Ask more than you tell.
  7. 87Write it down. Include by default.Include by default.
  8. 88Written together. Short. Revisited.Agree how you'll work.
  9. 89Ask regularly. Watch the trends. Act on red.Ask. Watch. Act.
  10. 90Earn influence. Spend it carefully.Influence is earned.

10Transformation Days 91–100

You'll have a plan to change how work gets done, starting with one real problem.

Team session guide →

  1. 91Change the system, not just the ceremonies.Change the system, not the rituals.
  2. 92Small start. Real problem. Let success spread.Small start. Real problem.
  3. 93Measure outcomes customers and teams actually feel.Measure what people feel.
  4. 94Leaders go first. Then fix what only they can.Leaders go first.
  5. 95Expect the dip. Support people through it.Expect the dip.
  6. 96Agile stops at the org chart. Unless you invite them in.Invite the rest in.
  7. 97Expert help, part-time, with a handover plan.Expert help, part-time.
  8. 98AI drafts. Teams decide.AI drafts. Teams decide.
  9. 99Build it in. Keep inspecting. Never “done.”Never quite done.
  10. 100Start small. Measure. Keep going.Start Monday.