Writing about how the things that look good in the book actually work in the field.
Notes on Scrum ceremonies, team leadership and software engineering. Every post follows the same skeleton: what it is for → how it should work → how it breaks → checklist. Practice, not theory.
Scrum and Process
The ceremonies are a chain: broken refinement makes planning drag, broken planning turns the daily into a status report. That is why these are written to be read in order.
Being Agile vs Doing Scrum
Agile does not end the chaos; it makes it visible. That is why teams can run every ceremony and still not be agile.
PART 02Backlog Refinement: Kill Bad Ideas Early
Refinement is a funnel, not a meeting. Back-of-the-envelope filtering and ROI in one shared currency.
PART 03Grooming: Not a Ticket Reading Session
The PO's job is not to read out what will be built, but to explain why it matters.
PART 04Sprint Planning: Commitment, Not Estimation
Good planning is boring. If surprises show up, the preparation failed. Capacity math and the pull system.
PART 05Daily Standup: Synchronization, Not a Status Report
If what you did yesterday does not affect today, it does not matter. Walking the board, and the async option.
PART 06Sprint Review: A Feedback Loop, Not a Demo Show
If nobody objects, nobody is listening. Silence is the worst signal.
PART 07Retrospective: Tracked Actions, Not Wishes
Definition, owner, deadline — without all three it is a wish, not an action.
PART 08Epic, Story, Task: How to Break Work Down
Why should a task never exceed one day? Six ways to cut work, walked through a real e-commerce returns project.
PART 09Does Scrum Make Customers Happy?
Bringing the customer inside: from 1 project to 9, from 1 person to a team of 14. A real story from the field.
Team Leadership
The human side rather than the process: hard conversations, performance, what replaced authority, and what a manager is actually for in the age of AI.
How to Give Negative Feedback
Why does the sandwich fail? The event → impact → expectation pattern, with real dialogue.
LEADERSHIPCan You Measure Performance With OKRs?
Tie a bonus to a target and people shrink the target. Why story points inflate, and what to read instead.
LEADERSHIPNew-Generation Leadership: Authority Is Gone, Now What?
The information monopoly ended, dependence ended. What replaced them, and the power of "I do not know".
LEADERSHIPAI or Leadership?
Writing got cheap, verifying got expensive. The junior learning path and the leader's changed job.
Engineering
Concurrency, distributed systems, scaling and coding with AI — all with real incidents and code examples.
Race Conditions: Why Does Stock Go Negative?
Invisible in staging, catastrophic on sale day. Six fixes, with SQL examples.
ENGINEERINGDistributed Locks: Getting It Right
Six traps in a Redis lock, fencing tokens, and the fact that most cases need no lock at all.
ENGINEERINGWorker Sharding: The Right Way to Split Work
Four workers, one at 100% CPU and three idle. Hot keys, rebalancing and ordering guarantees.
ENGINEERINGHow Pod Scaling Actually Works
Pods went from 4 to 24 and the system got slower. Why is CPU the wrong metric?
ENGINEERINGVibe Coding Rituals
Why does three hours of work turn into two days of debugging? Ten habits that work.
Who this is for
You are running Scrum, but the meetings keep growing, sprints keep spilling over, and nobody looks at the retro actions. Every post ends with a checklist; if you are in a hurry, read only those and share them with your team.