Interview Q&A
Home
Admin
Edit Q&A #4
← Admin list
Category
Delivery Manager
Program Manager
Scrum Master
Question
*
Alternate Questions
(one per line)
Recommended Answer
Situation: I took over delivery for a brand new team assembled from external hires and internal transfers, geographically distributed — developers in Hyderabad, QA in the US. They didn't know each other, had communication friction, and had no established ways of working. Velocity was 23 story points with 50% carry-forward sprint to sprint. Task: Diagnose the root causes and turn this into a predictable, high-performing delivery team. Action: I ran a retrospective-style analysis and found three root problems: QA wasn't co-located with developers so feedback loops were slow; BAs and POs were writing BRD-style documents instead of user stories — too large, poorly defined; the team only estimated dev effort, not testing, integration, or rework. I introduced story refinement sessions to right-size work. I moved them from time-based estimation to planning poker with story points, which forced cross-functional thinking. I brought in senior developers from other teams to mentor newer members. And I coached the PO and BA directly on writing proper user stories — the hardest part, since they were used to waterfall documentation. Result: Over six to seven sprints, velocity went from 23 to 42 — nearly doubled. Carry-forward dropped from 50% to single digits. But the biggest win was predictability. We could tell leadership and client success with real confidence what we'd deliver each sprint. That changed how the client perceived us — from unreliable to a trusted partner.
Key Beats
(one per line — shown as numbered list)
1. Systematic root cause diagnosis — slow feedback loops, BRD stories, estimation gaps 2. Planning poker — forced cross-functional thinking, not just dev effort 3. Story refinement — right-sized user stories, taught agile to the whole team 4. Brought in senior devs to mentor — highest-leverage intervention 5. Coached PO/BA on user stories — hardest cultural shift, waterfall to agile 6. Numbers — velocity doubled (23→42), carry-forward single digits, predictability restored
Coach Notes
Lead with the biggest decision — bringing in senior devs to mentor. Own numbers confidently: 'velocity doubled from 23 to 42.' Add one sentence about what you'd do differently next time to show self-awareness.
Score
(0 – 10, optional)
Save Changes
Cancel