Blog
Mert Özen's blog posts on software development, backend, frontend, and DevOps.
Communicating Estimates and When the Plan Slips: Updating, Delivering Bad News Early and Replanning
When a plan slips, the first move is to deliver the bad news right away together with options; choosing between cutting scope, moving the date or adding people is a business decision, and adding people to a late project rarely saves the date. Bookstore's update after three sprints shows scope grew to 142 points and the full scope slipped to March 26; we compute the options in C# and write a one-page estimate note.
Release Planning: Velocity Ranges, Burn-Up, Fixed Date or Fixed Scope?
A release date comes not from one average velocity but from a range derived from past sprints; if the date is fixed, scope flexes in MoSCoW layers. Bookstore's 130-point Institutional Orders plan lands between February 12 and March 12, and the Must scope fits by March 1 even in the bad case. We also answer the same question with Monte Carlo and see why the two methods disagree.