#agile #scrum #tech #softwaredevelopment #meme #funny

[ahltorp@mastodon.nu]

@travisfw @kwramm Velocity has been part of the Scrum story since at least then, and saying that it isn’t Scrum is like saying Trump isn’t president of the US because there’s no mention of him in the constitution.

[ahltorp@mastodon.nu]

@woe2you It’s not only ”we suck at gathering requirements”, it’s also ”it’s often not meaningful to gather requirements in a vacuum”. Those are actually among the good parts, having stakeholder representation in the team. ”Fancy name” is among the bad parts.

[ahltorp@mastodon.nu]

@travisfw @kwramm According to Wikipedia, the ”Scrum Guide” has only existed since 2009. Is that true? If it’s true, what holy document were people using before that to say what was Scrum and what wasn’t?

[pavelasamsonov@mastodon.social]

@Cadbury_Moose @mwshook If you liked Laundry Files you might like The Rook, Antimemetics Division, and Monday Begins on Saturday.

[jaystephens@mastodon.social]

@PavelASamsonov @Cadbury_Moose @mwshook
+1 for antimemetics division

[catmisgivings@stranger.social]

@PavelASamsonov this happened to me about as literally as possible on this plane

[highlandlawyer@mastodon.social]

@jaystephens @PavelASamsonov @Cadbury_Moose @mwshook
There is no antimemetics division

[kwramm@mastodon.gamedev.place]

@ahltorp @travisfw The oldest book I have in my library is Schwaber's "Software Development with Scrum" from 2002, which is quite interesting. It's a lot more people / culture focused than even the Scrum guide (there's just so much you can write on 11 pages). They do have burndowns there, but even their they put in bold that it's (delivered) "results" that matter. The burndown shows how much work remains so you can plan. That's it. Overall the book feels very close to the Agile Manifesto

[kwramm@mastodon.gamedev.place]

@ahltorp @travisfw well, yes, it's been part of the Scrum "story" just like certifications, trainers and whatnot. But it's not integral to Scrum.

You can do Scrum without "Velocity". You can use any other method to a) track how much work you do (better = track how much value is delivered and realized) and b) how much you can commit and reliably deliver at the end of the sprint (overcommitting = disappointed client).
You could track man-hours instead, and it works.

[kwramm@mastodon.gamedev.place]

@ahltorp @travisfw I read the Scrum guide first in 2014 or so, after starting off with all kinds of books that add tons of extra complexity.

It's kinda liberating how simple Scrum can be. I feel the simpler you keep it, the more powerful it is.

And if in doubt between the Scrum guide and what helps your team: Talk to your team FIRST about what works for them - that's what Retrospectives are for - that's pretty much in line with Schwaber's book that I mentioned in my other reply. People first!