Re:Estimates are difficult for developers and product owners
by namdnay on Sunday December 07, 2025 @03:55PM
(#46185067)
> technically it is irrational
Only if your company operates in a vacuum, without investors or customers
Re:Estimates are difficult for developers and product owners
by poguemahoney on Sunday December 07, 2025 @04:13PM
(#46185205)
As an investor, I don't like a investment that throws away 10-30% of its resources, perpetually lowers morale except among the least creative and misses opportunities because their competition is faster.
Re:Estimates are difficult for developers and product owners
by js8 on Monday December 08, 2025 @02:21AM
(#46189369)
Investing or buying into something new and unknown is by itself not a rational act (to the extent the thing is novel).
IMHO rationality (optimization) only makes sense relative to a well-defined goal.
Re:Estimates are difficult for developers and product owners
by greenchair on Sunday December 07, 2025 @07:35PM
(#46186973)
Another reason kanban doesn't work for large projects is because you have to coordinate your cycles with multiple dependencies teams roadmaps and releases.
Re:Estimates are difficult for developers and product owners
by js8 on Monday December 08, 2025 @01:31AM
(#46189092)
I don't think so, only if they need to have a schedule as well. Most OSS projects operate as Kanban and it's just fine.
Waiting on a dependency is kinda like waiting on a lock held by another process in the operating system. It has little bearing on whether dispatch queue is effective or not; in fact, it shows the solution: Do something else instead of waiting. (This is why the OS analogy is so useful for project management, if only PM's would listen!)
It's again, if you need to plan things ahead (for some reason) when the dependencies become a problem.
But maybe I misunderstand what you mean, if you still disagree provide a more specific example.
You can make good estimates, but it takes extra time researching and planning. So you will spend cycles estimating instead of maximizing throughput, and to reduce risk, plan is usually padded up so you lose extra time there according to the Parkinson's law. IME a (big) SW company prefers to spend all these cycles, even though technically it is irrational (that's why we don't do it in the operating systems).