Software delivery, taught honestly.

• Software Delivery Fundamentals

  3-4 hours · 5 modules · 19 lessons · beginner
  The basics — source control, tickets, estimation, and choosing your first process

• Scrum Master Essentials

  6-8 hours · 6 modules · 21 lessons · beginner
  Master the art of servant leadership and agile facilitation

• Kanban Essentials

  4-5 hours · 5 modules · 25 lessons · beginner
  Master flow-based delivery for knowledge work

• XP Essentials

  5-6 hours · 5 modules · 25 lessons · beginner
  Master the practices of technical excellence and iterative delivery

• Lean Software Development Essentials

  5-6 hours · 5 modules · 26 lessons · beginner
  Apply Toyota's thinking to software delivery

• SAFe Essentials

  7-9 hours · 6 modules · 19 lessons · intermediate
  Scale agile across teams, programs, and portfolios

• The Bottleneck Moved to Code Review. Your Metrics Didn't.

  Throughput is up and delivery is down, and the four keys will not tell you why. Under heavy AI adoption the constraint left the keyboard and settled in the review queue — median time in PR review up 441.5%, PRs merged with no review at all up 31.3%. Here is what to instrument instead.

• Your Method Already Has Retrospectives. It Calls Them Lessons Reports.

  You were told Simyl Flow is for agile teams. It's for teams with dates and tickets. If you run phases and milestones, your method already contains every ceremony in the product — you just run them by hand, into documents nobody reopens.

• Twelve Working Agreements for Machine-Written Code

  The vibe-coding hangover retro ends with rules on a whiteboard. Here are twelve you can steal — each one a single-sentence rule, the number that moves if it's holding, and the check-in that keeps it honest.

All posts