3 ms·
I'll go against all the other answers and say that I have seen that in practice. I'm even doing that in practice, every day of the week. A half-day task would e
by williamdclt 8y ago
I'll go against all the other answers and say that I have seen that in practice. I'm even doing that in practice, every day of the week. A half-day task would even be a big task, most of our tickets are a couple hours maximum.
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).
- trey-jones 8y agoDo 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.
- williamdclt 8y agoFor 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!