Blog
Mert Özen's blog posts on software development, backend, frontend, and DevOps.
The Increment and the Definition of Done: What "Done" Really Means
The Definition of Done is the Increment's commitment: an item that does not meet it can neither be released nor shown at the Sprint Review, and returns to the Product Backlog. The post writes a concrete Definition of Done for a .NET and Angular team and turns it into a GitHub Actions workflow: in a local run of its steps a vulnerable transitive package broke the build with NU1903, and an uncommitted OpenAPI document made git diff exit with code 1.
Engineering Practices in Scrum: Branching, CI, Feature Flags and Technical Debt
Scrum imposes no engineering practices, but a Done Increment every Sprint is only sustainable with short-lived branches, CI and feature flags. In a real run with Microsoft.FeatureManagement 4.8.0, the return endpoint returned 404 with the flag off and 201 with it on; the same build behaved differently in two environments. The post explains why a flag does not pierce the Definition of Done, three ways to make technical debt visible, and spikes.