Nguyen Le Phong
Back to blog

Writing

Agile & Delivery

How real teams run Scrum and Agile — the standard, the customizations, and how to operate it well.

Practical, no-nonsense writing on how software teams actually work: Agile and Scrum in practice, the meaning behind epics, stories, tasks and story points, honest estimation and work logging, reading burndown and velocity charts, and running planning, standups, reviews and retros so they help instead of waste time. Written so anyone on the team — BA, PO, PM, developer, QA or newcomer — can understand it and operate well from day one.

Agile & Delivery

TDD, BDD, DDD, and the Rest of the "-Driven Development" Family, Explained for Engineers

TDD, BDD, DDD, ATDD, EDD, CDD, FDD — the "-Driven Development" alphabet soup confuses even experienced engineers, partly because they're not rivals: they answer different questions and compose together. This is a practical, example-rich guide for software engineers: what each one really means, the core loop or concept, concrete code and Gherkin examples, when to reach for it, the pitfalls — and a clear map of how they fit together on a single real feature.

22 min read
Agile & Delivery

Agile & Scrum in Practice: How Teams Really Run It vs. How It's Meant to Work

Almost every software team says they "do Scrum" — and almost every one does it a little differently. This is a clear, practical field guide for everyone on the team, whatever your role: what an epic, story, task, and sub-task actually are; how status workflows really run; what story points mean (and the mistakes that ruin them); how to estimate and log work honestly; how to read burndown and velocity charts; and how to run planning, daily, review, and retro so they help instead of waste time. The standard, the common customizations, and how to operate it all well — enough to be genuinely useful from day one.

20 min read