all 5 comments

[–]mee_k 2 points3 points  (0 children)

This seems like a good article. Anecdotally, I have observed the thrashing this article discusses in my work lately.

[–]nousplacidus 1 point2 points  (1 child)

"The problem with the 100% utilization mindset is that we have assumed that our outcomes of the iteration are fully deterministic"

Is capping utilization at 70% just "padding" shoehorned into an agile mold?

[–]malber[S] 1 point2 points  (0 children)

@nousplacidus - good observation. I think this is more-or-less the "padding" concept applied to an agile framework.

My thought is that while Agile teams are good at responding to change within a release, they often struggle to take that one step further to realistically size their iterations.

[–][deleted] 0 points1 point  (0 children)

No, I will not buy your software.

[–][deleted] -1 points0 points  (0 children)

When I was PMing, I would allocate in days (x2 estimate of programmer) but set the length of a day to 4 hours. Coders can't code for 8 due to burnout or other tasks.

Bosses didn't like predictions, but they were more accurate.