Matthew MartinMay 19, 2023

#Agile #Scrum un-#SAFe
Sprint velocity shouldn't be confused with a time card or itemized bill for tasks

Let's imagine it was. First off, it will be the worst, most inaccurate ever because you're making guesses about the unknowable future, not commitments. Real time cards are recorded *as it happens* for this reason.

Point estimates are self declared by individual contributors. If there are $ penalties to not reaching velocity, you merely keep your job if you hit velocity, lose your job if not

Show threadHolzerMay 19, 2023
@mistersql
Agree with your insights, but not with conclusions:
A sprint/PI/sth-plan is a PLAN, not a commitment.
If you get fired bc plan is met, that's anti- #agile, it's 20th century style coerce way of work. No one dares giving objective estimates in that case.
I studied some maths: If you plan realisticly, you'll be below plan in - guess what - 50% of the cases. Compensating with slight security adds and just in case some flexible work times, you'll get +/- 80% reliability. More than fair.
Show threadMatthew MartinMay 19, 2023
@holzer Oh, I'm not suggesting any of this is real scrum, agile or even "real SAFe", my org is using federal contracting & project management thinking with agile jargon swapped in. We're building software & pretending it is a bridge and that the work hours are known in advance (build that bridge like the last 50) and there are no unknowns (like military brownies, everything specified to the microgram)
Show threadHolzer
@mistersql
Yeah, classic PM (which I dont consider bad in any way) + agile swapped in. Worst of both worlds will make us successful.
May 19, 2023 at 3:23pmMastodon for Android