Claudius Link<p>I'm just in a process training. One topic is Weighted Shortest Job First (<a href="https://infosec.exchange/tags/WSJF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WSJF</span></a>). 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.</p><p>The official devicition is </p><p>Cost of Delay / Job Size</p><p>where </p><p>Cost of Delay = User-Business Value + Time Criticality + Risk Reduction and/or Opportunity Enablement.</p><p>IMHO Agile is all about theat we generally don't know the Job Size, and are regularly wrong (biased) about the (User) Buisness Value.</p><p>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)</p><p>Anyone has experience with it?<br><a href="https://infosec.exchange/tags/SAFe" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SAFe</span></a> <a href="https://infosec.exchange/tags/Agile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Agile</span></a></p>