Leading a 400-fix release to its planned date
I led the India developers on a release that cleared the bug backlog with over 400 fixes. The India team did almost all of the work from development to QA, and the release shipped on its planned date.
- Delivery
- Quality
- Leadership
400+
bug fixes in one release
about 80 more queued items closed as not bugs
What would have happened
Releases without a hard customer date had a record of slipping dates or dropping scope.
The call
Hold the planned date anyway, and use the release to fix the old date-logic problems for good.
What I did
Led the India developers through the fixes and the date-logic rework, then thanked the team and invited them out to celebrate.
What changed
Over 400 fixes and about 80 non-bugs closed. The US head of development called it a bang up job and said the rework would pay big dividends.
Proof
The original documents are held in my private record and can be shared on request.
What people said
“You all did a bang up job in getting this release out.”
“I believe we did over 400 bug fixes, we also eliminated a bunch of items that were in the queue that were not bugs in the end (about 80 of them).”
