2 ms·
> This demand for estimations leads to unproductive and unnecessary estimation meetings. These meetings are unproductive because they cause developers to spend
by lmm 4y ago
> This demand for estimations leads to unproductive and unnecessary estimation meetings. These meetings are unproductive because they cause developers to spend time debating whether something is worth two or three story points instead of actually writing code. They’re also unnecessary because if you feed the system with more work as soon as software comes out, estimations don’t matter.
Only if all tasks are of equal priority, which is rare. Otherwise you need some (very basic) cost estimation in order to prioritize.
> Retrospective sessions are also fundamental for a team to continuously improve the way it works. The problem with these sessions in Scrum is that they either happen too early or late. Although it’s good for teams to discuss their practices and look for ways to improve them, it may not be necessary to hold a retrospective session if everything is going fantastically well. Conversely, it may be harmful to wait for two or more weeks to discuss systemic problems impacting the current pieces of work or the overall goal the team is working towards.
> In Kanban, there’s nothing preventing teams from scheduling regular meetings. Yet, teams have the flexibility to schedule meetings whenever they’re necessary.
But unfortunately this means they also have the flexibility to not hold a meeting when it's necessary.
I don't think this article is exactly wrong - Scrum is to a certain extent a crutch, just as any process is to a certain extent a crutch - but I think it overestimates the average manager/team. In my experience teams that pick Kanban over Scrum tend to have issues with stalled, overly-large, and poorly-prioritised tasks (e.g. an undesirable task can sit indefinitely in the "ready for work" column which is usually not what you want), too little process refinement (in particular, retrospectives end up being rare) and take too long to recognise issues.
Scrum is prescriptive and restrictive, but it's like that because it works. After all, if your team was perfect you wouldn't need Kanban either. Just do the right thing and don't do the wrong thing bro.
- JenrHywy 4y agoPicking up on > They’re also unnecessary because if you feed the system with more work as soon as software comes out, estimations don’t matter. The question is: estimations don't matter to who? As much as I'd like a constant stream of quality features to be good enough, in reality senior managers and clients want to know what they're getting for their money, and when they'll get it (at least roughly). If your software is doing something important, it's likely that people will be depending on it and when a new feature ships can have a significant impact on how they work, and in turn, what they can deliver.
- lmm 4y ago> As much as I'd like a constant stream of quality features to be good enough, in reality senior managers and clients want to know what they're getting for their money, and when they'll get it (at least roughly). IME most of the time they need to get over it. The reality is that estimating in that kind of detail would be expensive and not worth the effort. However what they do reasonably need is the ability to prioritise feature A over feature B and they need a vague comparison of costs in order to do that (like, is feature B going to be 3x as much work as feature A?). Scrum provides that at minimum cost.
- ajmurmann 4y agoIt depends what you are working on, how you ship and how three rest of the company works. I work on Enterprise software that's not SaaS. We ship every 9-12 months. If we do it more frequently it just annoys our slow-moving costumers and increases our support burden because there are now more versions in support that might need patches. Our sales and marketing teams need to know when we ship. Sometimes costumers mighy need to adjust their own release schedules to when our next release is out. If one team needs longer for a critical feature, we need to know as early as possible so that we can discuss cutting scope, pushing the release out, cutting the feature, etc.
- Closi 4y agoYep, or if you are working on a project to build a control system for a new factory which is going live in 18 months, it's pretty reasonable for your management team to want to know that you have confidence you can build the control system within a year. If not, they will probably want to cut the scope or put other risk mitigation in place.