[Bloat] story points are pointless, measure queues

[Dave Taht <dave.taht@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]

It's nice to see queue theory enter another discipline (scrum software
development), although the article takes a very long time to get there,
first discussing the failures of "points" in the developmental process,
before introducing queue theory 101.

https://news.ycombinator.com/item?id=40969693

The "Full Queues Amplify Variability" chart is nice. Also I had not heard
of Reinertsen before, using different language for other

From the above:

"Reinertsen's books are very, very good. The most recent and most
up-to-date is Principles of Product Development Flow, which that chart came
from. The previous one, Managing the Design Factory, is pretty similar and
I think it's a better read.

Another great takeaway from it is to prioritize things by cost of delay, or
even better, what he calls Weighted Shortest Job First, where you divide
the cost of delay by the expected length of the task."

Perhaps an fq_codel like approach can be applied to complex
product development tasks? i have always been highly influenced by "Getting
Things Done", and both toke and I are huge advocates of org-mode in emacs,
not that modern computing environments make this sort of flow easy.


-- 
Artists/Musician Campout Aug 9-11
https://www.eventbrite.com/e/healing-arts-event-tickets-928910826287
Dave Täht CSO, LibreQos

[-- Attachment #2: Type: text/html, Size: 2841 bytes --]