Agile Estimation - Learning from traditional Project Management

I have long wondered why Agile (well, read Scrum) planning is so simplistic.

Yes, having the team estimate the tasks and then agree to them is, frankly, a world away from the handed-down-from-on-high estimation found in most companies, big and small. Even where estimation is initially done by the teams, I have found a number of times that the estimates are either massaged, or are part of a in-all-but-name waterfall approach.

Even a little more sophistication can lead us to estimates that are dramatically more useful outside the team, and that tends to lead to teams getting left alone with a reputation for hitting thier promises.

So I suggest that all Planning Poker estimates are provided with PERT three-way estimation points, and then thyat is

Planning poker is based on Wide-Band Delphi which came out of RAND Corporation via Barry Boehm.

Flow control in networking and Agile estimation

  • team ramps up slowly then halves it’s rate if it ever missed

Notes