Thanks for the comment.

Bruce

Yes the experience of lateness in one project would guide all in arriving at the production points for a company. Say you estimate an use case method then we need to know from experience how much an average developer of our company requires in time to complete an usecase(use case points), like wise we need to have all methods of statistics from past to guide us in present and future.

The conversation ended at this retort from the SVP.

This is the kind of toughness needed to improve, right? Not!

Previously, for at least 7 years, we had regularly delivered major products 3 to 6 and even 9 months late. This “one week late” had been a huge improvement.

The SVP was new (but not new to the company). She apparently didn’t like any improvement that she did not initiate.

She was gone within a couple of years. Not only did she not make a difference, she had suppressed taking advantage of the biggest improvement we had made in years. All she had to do was say “Great job. We need to do more like that and better and here is what I had in mind ….”

Success is not always self evident nor self perpetuating. We may have to work hard to keep making progress. The trick is to realize this is fairly normal and we just need to persevere.

Bruce Benson

The bottom line is that you can know if your project management tool estimating is accurate. More to the point, estimating in a project can be verifiably accurate….