Learning paths
Learning path

Ways of Working

How teams build software: why Agile happened, Scrum and Kanban, estimation, DevOps, spec-driven development and AI.

7 lessons
How do you want to learn?
  1. Lesson 1

    Start here: Ways of Working

    How software delivery moved from waterfall to Agile to AI-assisted work, and why each shift kept running into the same problems.

  2. Lesson 2

    Why Agile Happened

    Why Agile came about, what Royce's "waterfall" paper actually warned against, and how Agile itself turned into bureaucracy.

  3. Lesson 3

    Scrum, Kanban and XP in Practice

    Effective software delivery requires a balance of project cadence, workflow limits, and rigorous engineering practices, as highlighted by frameworks like Scrum, Kanban, and Extreme Programming (XP).

  4. Lesson 4

    Planning and Estimation

    Modern software development practices emphasize agile methodologies that move away from traditional command-and-control models and rigid, feature-driven roadmaps in favor of empowered product teams focused on delivering…

  5. Lesson 5

    DevOps and Continuous Delivery

    Modern software engineering requires continuous deployment and integration, where development teams rely on automated pipelines to frequently merge, build, and test code changes with minimal manual intervention.

  6. Lesson 6

    Spec-Driven Development

    Modern software development increasingly relies on AI coding agents and spec-driven methodologies to streamline project creation and maintenance.

  7. Lesson 7

    Is Agile Dead in the Age of AI?

    Whether Agile still fits when AI writes much of the code, what AI-assisted development changes, and why it can slow teams down.

Save to playlist

Manage playlists →

Share