In the presence of uncertainty, acquiring information is often the best way to generate value. — Dan Milstein

1 hour of planning can save you 1000 hours of coding. 1 hour of coding can save your 1000 hours of planning. There is no science to figuring out which case you’re in. Only art. — Robert Roskam

OK a queue of tasks: tasks build a feature. In a sprint, the story points (and velocity) are replaced with tasks (or task rate).

Reacting to fast feedback is literally the point. you update the tasks with the new information. Your team can mob around the new information and add new tasks and remove tasks that no longer apply.

You get more accurate projections and estimates because you stopped estimating.

There is one way to control the flow rate from the support queue: quality control and rapid response to support issues. Higher quality control is designed to reduce the output of issues which could potentially trigger support requests. Rapid response allows you to immediately deal with any issues that quality control didn't catch but your customers did.

As rust will last, an decades long IT-project needs to plan for long-term. This blog post provides an overview.

Is it relevant to maintain a part nobody seems to use?

Ne plus mesurer l'item d'un backlog avec son ROI, mais aussi avec l'impact environmental et l'impact social.

Mentoring for the win. But how frequent?The author thinks about once a week