The post Leave Scrum to Rugby, I Like Getting Stuff Done appeared first on Qvault.
Scrum is a buzzword, the virtue signal of choice for middle-m...
For further actions, you may consider blocking this person and/or reporting abuse
I think you'll really enjoy these two talks by Allen Holub, which align very well with this article:
The death of Agile and #NoEstimates or skip to #NoEstimates End Summary
In summary, the death of Agile is that Scrum is basically the antithesis of remaining agile (lowercase on purpose). You can't respond quickly to customers and have locked sprints. You can't remain agile and have silo roles.
NoEstimates claims that you can't estimate and you shouldn't even try. You can project once you've started and you can prioritize so you know you're always working on the right thing. Beyond that, just work based on priority (and ruthlessly prioritize) and get stuff done.
Thanks for sharing Lane, very well written!
Have seen a lot of scrum hating recently, and I can understand all your points, the thing I'm missing in your post and in many others are alternatives!
Scrum was created as an alternative to the old waterfall way, and so far, haven't see anything that complete as alternative, a proper framework that can guide any development team.
Do you know about any proper documented frameworks that can help solving this problems?
Hi, I wrote some articles about agile not so long ago. You might want to check it out.
Also, I've found the process used at Basecamp is quite close to what we use at my work. And it works for us. Its called ShapeUP, check it out.
I don't think that's the right way to look at it. There are real problems with scrum and they show themselves in frustration of people involved with it. The are things that work in scrum and things that don't. Daily standup is excellent for instance. Pointing stinks. Scrum master should not even be a role, but a shared understanding of few principles.
Thanks for writing this up. I thought I was alone in feeling some of the pain points you have expressed. Scrum intentionally disengages the estimates from reality with the hopes that it would save developers from schedule pressure. The intent is good, but solution is wrong. It would be more helpful to agree on a system where estimates are updated regularly. It will improve the communication and make us better at estimating over time.
Another problem of estimating in points is that we don't know what a point represents. My current team has taken a decision that points are based on complexity, not time. So, we often get into discussions whether something is complex or time consuming.
Another reason I don't like points is that we often have to go back to review things we pointed before to anchor ourselves at the scale. We have to do that because each one of us has a different imaginary scale in our minds. If we used days estimate instead, we would have none of these issues.
I really think points are pointless. It helps nobody, but creates extra confusion. It makes it hard to communicate with the business, who won't care about your imaginary points but cares about when things will be available.
Nice article, thanks for sharing. I'm on the same boat. I worked in many Scrum projects and teams, thats why at my current job we are staying away from it.