Where to Go Next
Picking the right Simyl course based on your answer.
1If You Picked Scrum
Scrum Master Essentials covers the full framework: sprint planning, daily standups, sprint reviews, retrospectives, and the scrum master role in depth. You'll learn how to facilitate each ceremony, protect the sprint commitment, and coach a team through the first few rocky iterations. It also covers the anti-patterns that kill Scrum adoptions — half-hearted sprints, absent product owners, and retrospectives that produce no change. The course assumes you already have the fundamentals from this one — source control habits, meaningful tickets, and basic estimation.
2If You Picked Kanban
Kanban Essentials goes deep on flow mechanics: board design, WIP limits, pull policies, cycle time measurement, and continuous improvement without sprints. You'll learn to spot bottlenecks from board shape alone, run effective replenishment meetings, and use cumulative flow diagrams to forecast delivery without estimation. The course treats Kanban as a management method, not just a board layout — you'll understand the theory well enough to explain your WIP limits to a skeptical stakeholder. Best for teams whose work arrives unpredictably or who want to build flow discipline before considering Scrum.
3If You Want Technical Practices Regardless
XP Essentials focuses on engineering practices that make any methodology work better: pair programming, test-driven development, continuous integration, small releases, and collective code ownership. Where Scrum and Kanban address how teams coordinate, XP addresses how engineers build. The practices reinforce each other — TDD makes CI feasible, CI makes small releases safe, small releases make pair programming practical. These practices are methodology-agnostic — they improve delivery whether you run Scrum, Kanban, or nothing formal. If your team's bottleneck is code quality or integration pain rather than coordination, start here.
4If You Want the Philosophical Foundation
Lean Software Development traces the thinking behind both Scrum and Kanban back to its manufacturing roots: eliminate waste, amplify learning, decide as late as possible, deliver as fast as possible. This course is less prescriptive than Scrum or Kanban — it gives you principles rather than practices and lets you design your own process from first principles. Best for experienced teams or leaders who want to understand why the frameworks work — and have the confidence to adapt them when the textbook answer doesn't fit their context.
5If You're Scaling Across Many Teams
SAFe Essentials is for organizations coordinating multiple teams toward shared objectives — program increments, release trains, and cross-team planning. The course covers PI planning, Agile Release Trains, and the roles that coordinate them — but starts by helping you assess whether you actually need that coordination layer. Don't start here unless you have at least 3–4 teams that genuinely need to synchronize. SAFe solves coordination problems that single teams don't have, and adopting it prematurely creates bureaucracy without benefit. Master the single-team fundamentals first; scaling frameworks assume you already have.
You can pick more than one over time
Most engineers we know have learned Scrum, then Kanban, then XP — not because they switch jobs but because each one teaches something the others don't.
- Each follow-up course is one layer deeper than this one
- Order doesn't matter much; gaps in fundamentals do
- Come back here if your team is struggling with the basics