Blog
Mert Özen's blog posts on software development, backend, frontend, and DevOps.
Actively Managing Flow in Kanban: Blockers, Aging and Flow Reviews
Actively managing flow means reading the board right to left from the oldest item every day, escalating blocked work, limiting expedite and finding the bottleneck with data. We compute CFD band widths from Bookstore data in C#, see how Code Review became the bottleneck in July, how the Theory of Constraints steps solved it (p85 from 16 to 11 days), and why the next constraint is the deploy rhythm.
WIP Limits and Little's Law: Start Less, Finish More
With throughput fixed, raising WIP stretches cycle time by the same factor; Little's Law is the arithmetic behind it. In our C# simulation, raising WIP from 3 to 10 takes average cycle time from 2.4 to 7.9 days, and adding context switching cuts throughput too. We cover Little's Law's assumptions, why it is not a forecasting tool, how to set a first WIP limit and pitfalls like per-person limits.
What Is Kanban? From Toyota to Software, and Why It's More Than a Board
Kanban is not a board but a strategy that optimizes the flow of value by limiting WIP; the board only makes it visible. Using the Bookstore support team's board, we trace the path from Toyota's pull system to Anderson's work at Microsoft and Corbis, compare the Kanban Method with The Kanban Guide 2025.5, and introduce the Guide's three practices and four flow metrics.
The Daily Scrum: A 15-Minute Planning Event, Not a Status Report
The Daily Scrum is a 15-minute planning event in which the Developers inspect progress toward the Sprint Goal and adapt the Sprint Backlog; its output is an actionable plan for the next day, not a report. The post covers why the three questions were removed in 2020, a format that walks the board from right to left and looks at item age, practices for remote and hybrid teams, and the traps of reporting to managers, problem solving and overruns.