4 ms·
Misunderstood Parts of the Scrum Guide
- rightbyte 4y agoHe just lists Scrum's all flaws and says it is not real Scrum. Maybe time to just give up defending Agile already? > 2. Scrum is not about chopping work up into smaller items > 4. The Product Owner and Scrum Master don’t have a higher hierarchical position > 6. Scrum events don’t serve to plan the output of the team > 8. The items on the Sprint Backlog aren’t the team’s commitment
- bazoom42 4y agoDon’t conflate scrum and agile. The agile manifesto says “Individuals and interactions over processes and tools”. Scrum (as it is usually implemented) tend to favor process sbove everything.
- rightbyte 4y agoCapital a Agile. But ye, I agree. Scrum is hillariously stiff and very much not agile (the adjective). However, given all the false prophets I just want run anytime "agile methods" is mentioned. I actually applied to my new job becouse they said they did not work by agile methods, which usually implies Scrum, while most ads wanted "agile dev experience".
- lupire 4y agoScrum helps talented but disorganized people do more effective work. That's it. If you don't want to do Scrum, Scrum isn't for you. If the team doesn't want to do Scrum, Scrum will not work for the team. Scrum is not a silver bullet. It doesn't make untalented workers do good work. It doesn't stop micromanagers from micromanaging. It doesn't stop self-centered backstabbing ladder climbers from doing their thing.
- rightbyte 4y ago> It doesn't stop micromanagers from micromanaging. One of the flaws with Scrum in my opinion is that it enables micromanaging. It makes it easier. The whole concept of sprints with tasks and hardline prioritization before the work is in progress is a micromanagers dream. When you adapt Scrum suddenly there might be micromanaging where there were none before. It happened at my last employer.
- isitmadeofglass 4y agoScrum protects against micro management. The product owner can make a plan in the product backlog, but what goes into the sprint backlog is controlled by the team. I’f the PO says give me X in 3 weeks and the teams says no, then that should never go into the sprint backlog. Once planing is done the PO doesn’t have a say on what happens when and who does what or why. There is a forecast of work that will be done by review, and that is all. Doing micromanagement in scrum means you’ve not clearified who end what in scrum. If the PO thinks that they own the sprint backlog and cans dictate what you do and when you do it that’s a clear misunderstanding.
- senectus1 4y agoour company went through a fair bit of growth recently and we appeared to have acquired a bunch of scrum and agile enthusiasts.. These people frighten me a bit. they're like some sort of a cult. the get super agitated and enthused about all things agile and scrum and they start talking using phrases and terminology that is alien and overtly cerimonial... CONSTANTLY. You need to bring people to the watering hole, not drop an ocean on them.
- kthejoker2 4y agoAs a design pattern, Scrum purports to work for certain development teams, doing certain kind of work, with certain kinds of requirements, timelines, stakeholders, etc. Additionally by being modular, it purports to accommodate even wider ranges of these requirements. The only questions are * Does your particular development team and lifecycle fall under this spectrum? * What alternative patterns also might apply? And what's the right criteria to evaluate competing patterns? The answers are increasingly clear that Scrum works in a small minority of development scenarios, maybe < 5%. So it should be treated as a niche pattern applied when certain specific pathologies exist in your current SDLC / team. It's also helpful to understand those boundaries, and how misapplications of Scrum manifest in real world delivery mamagement. I wish this article was a bit more holistic, instead of a quasi-rant.