Brutkey

Claudius Link
@realn2s@infosec.exchange

I'm just in a process training. One topic is Weighted Shortest Job First (#WSJF). For some reason if got a bad feeling about the use of WSJF. It feels like adding several unknown values (guesstimates) and dividing by some more unknowns, leading to an arbitrary result with questionalble value which isn't free.

The official devicition is

Cost of Delay / Job Size

where

Cost of Delay = User-Business Value + Time Criticality + Risk Reduction and/or Opportunity Enablement.

IMHO Agile is all about theat we generally don't know the Job Size, and are regularly wrong (biased) about the (User) Buisness Value.

The samme applies to Risk Reduction and Opportunity Enablement. If there isn't a fixed external dealine also the Time Criticality is pretty arbitray (reading pure opinion or politics)

Anyone has experience with it?
#SAFe #Agile


Claudius Link
@realn2s@infosec.exchange

A related #quote which comes to my mind in situations like this

β€œThere's no sense in being precise when you don't even know what you're talking about”
― John von Neumann

Falk Appel
@FalkAppel@sueden.social

@realn2s@infosec.exchange "Metrics on guessed numbers are the easiest metrics to improve"
- Falk Appel
😜😜