4 ms·
Why is Scrum special and needed to be fixed? The question is making an assumption. The point of agile is for the team to self-organize for effectiveness. My que
by karmakaze 2y ago
Why is Scrum special and needed to be fixed? The question is making an assumption. The point of agile is for the team to self-organize for effectiveness. My question would be where does Scrum fit into that, and how is a "one size fits all" hammer, agile?
For my current team, I like either sync or async (in Slack) standups that basically say if anyone's blocked or could use some extra eyes, and what's next in their sights. For a team project board, I prefer Kanban style without estimates--I've never seen velocity tracking used to any purposeful effect. If you want a team to build good features fast, don't bother them with "process theatre", instead ask the team lead/PM the questions and they should either have a good sense or be able to find out soon by having human discussions with the team.
- rerdavies 2y agoI've had great success with velocity tracking. In my experience, once you have a team that's calibrated and humming along nicely, velocity tracking gives you an absolutely spooky ability to predict where the product is going to be two or three months time in the future. Is it perfect? Of course not. But it's far more accurate than any scheduling methodology I've ever used over a long career. I can't speak to why it didn't work for you. But I have seen it fail when an outside managers refused to allow proper calibration. Or when the same outside manager refused to make appropriate schedule or feature tradeoffs. In that particular case, velocity tracking predicted total disaster with 100% accuracy.
- karmakaze 2y agoIt seemed like a round about way of getting the team to come up with as good an estimate as to where the project would be in two or three months without it. And where it totally falls down is when you don't have data for the kind of work that's coming up.