4 ms·
I feel like that journalist who wrote an article called "Stop making me defend Donald Trump". I don't particularly like Scrum, but articles like this just give
by robertlagrant 4y ago
I feel like that journalist who wrote an article called "Stop making me defend Donald Trump". I don't particularly like Scrum, but articles like this just give not liking Scrum a bad name. I wouldn't trust anything it says, really.
Here's a sample:
> It has to be timeboxed into a Sprint to make sure software can be released into the market in an “iterative” cycle.
The key is "potentially shippable increment". You don't have to ship it. The point is that if you don't have that mentality then you start to forget all the 50 steps needed to actually release, and also that small changes are more reliable than big changes.
> Sprint Planning happens right before the sprint because that’s when you’ll have the latest insights on what to focus on, just in time.
Yes, true.
> There’s a Daily Standup to have on-the-fly “operational improvements.” (Only developers are allowed to speak and discussion is not allowed because that leaves the machinery idle.)
"Developers" being anyone in the team, including UX. It's not about "leaving the machinery idle" - working a bit of a silly metaphor from the article back into the "why" of Scrum seems pointless - it's about having quick meetings. You can have conversations elsewhere, and regular meetings elsewhere; they just aren't for the daily standup. Unless you have a retro and decide to change it.
> At the end of the sprint there’s a Review to view working software and to determine what was not completed or what needs improvement.
That's sort of right, but an odd emphasis. It's to get feedback from the people you're building for.
> There’s also supposed to be a Retrospective to discuss what went well and what didn’t go well, in the interest of increasing the quantity of output.
No, not necessarily. It could be spotting that quality is low, or the team is taking on too much and burning out, or that things external to the team are really slowing something down (e.g. Todd still doesn't have a new laptop and he can't run the latest XCode), or anything else that would be an improvement. Again, why try working the silly metaphor back into reality?
> The Backlog isn’t core to the Scrum practice, it’s an artifact of the collateral damage and detritus of everything jettisoned during the sprint.
I don't think the author knows what the backlog is (or backlogs are). They are part of Scrum[0].
[0] https://www.scrum.org/resources/what-is-a-product-backlog https://www.scrum.org/resources/what-is-a-product-backlog