Re:Why Development Teams Struggle to Deliver on Time, on Bud...
by trey-jones on Tuesday June 05, 2018 @04:37PM
(#17241792)
Do you mind putting out a number of hours (per dev team) that get spent in Backlog curation, story generation, and other budget planning every week? I think perhaps an important missing ingredient for getting budgets right is actually spending the time to do so. The smaller the company, the harder it seems to justify.
Indeed, for a lot of us in smaller companies, getting our clients to actually consider taking an agile approach at all is a stretch.
Re:Why Development Teams Struggle to Deliver on Time, on Bud...
by williamdclt on Wednesday June 06, 2018 @04:02PM
(#17250572)
For a team of 3 devs + 1 scrum master:
- Backlog refinement/grooming: 1.5 to 2h, 1 dev + SM (+ PO)
- Technical refinement: 1.5h, all 3 devs
- Sprint review + retrospective + planning: 4h, all 3 dev + SM (+ PO)
Story generation is done by the PO, that's most of his job (though we split stories during backlog refinement if needed).
I don't know if it sounds like a lot (I feel like it could), but turns out it's actually efficient, every minute of each meeting is productive because we know exactly what we're going in for, how it will go and what you want to get out of it!
We practice a lean-laced Scrum with 1-week sprints. And yes, it works. And yes, we go fast. So yes, it can work (thought we have several years of refining our methodology and have a big culture of pragmatism and problem-solving).