Hi Mike (Cohn) - I enjoyed your talk on estimating at SD West. During one of our conversations last week you mentioned that you typically don't record...
Hi Dave-- I'm glad you enjoyed the talk at SD West. There are a number of problems with capturing actuals: 1) Yes, it sets up an unhealthy dynamic. Programmers...
Hi Mike- ... Yes, unless you precisely measure start time, stop time and interuption time for each episode of work on a task (which itself takes both time and...
I am slowly implementing SCRUM, and see immediate benefits. Like many of us, we have to make concessions (like a fake project plan to keep senior management...
In addition to the reasons Mike cites, the reason estimates are needed is to decide if the value of a feature is worth investing in the cost. Estimates of the...
Accountability for meeting estimates cannot rest solely with the development side of the team or failure is almost certain. Instead the whole product team,...
1. In "Lateness is Passed Down the Schedule", you use the word "task" to describe the activities. In Fig 1.3, you use the word "story." It seems you should...
I just posted a new chapter to http://www.mountaingoatsoftware.com/agileplanning/. This is the second chapter in the book and is meant to give an overview of ...
1. In "We Prioritize Often," p. 13, second paragraph, "interation" should be "iteration" in this sentence: "This is another reason why it is important that all...
Hi Mike and John, Hey, Great book so far. I'm looking forward to reading it all the way through. Here's my feedback on chapter 1. 1) I think you should...
I have started reading your Book draft and am looking forward to reading the entire thing. I think the subject of Estimating and Planning is something that...
In my point #3 below, "additonal" should be "additional" (unless I accidentally destroyed the spelling of the word when I was putting together the original...
1. In the last paragraph of section "Archetypal Programmer Days," remove "I find" from the following: "I find this normally means that the archetypal...
Thanks for this feedback, too, Chris. I changed the first item to "task" as you suggested. I've wrestled with the whole issue of what to call an agile unit of...
Hi Chris- Sorry for the slow response but thank you very much for taking the time to read the draft chapters and send me your comments. I appreciate it. I've ...
First off, a typo on page 3 - Local Safety. "What is frigthening..." should be frightening. Page 4 - Lateness is Passed Down the Schedule. I'm not sure this...
First of all, Mike, how the heck are you finding time to write another book so soon after the other one?!? :) ... Chap 1: Critical chain stuff is good. Don't...
Hello- I've just posted two new chapters: 13. Improving Accuracy: Planning with Buffers 14. Planning the Multi-Team Project The first addresses the questions I...
Hi Mike great work so far I think your book will be a great addition to the development community. A couple of thoughts... Chapter 9 While this is not a book...
Clarke- Thanks for the comments. You're right that I should point out the big problems of a waterfall-based approach. I like your suggestions there. There are...
Hi Kent- Thanks for the additional reasons. There's a chapter (or introduction, really) that will come before the chapters listed on the website that will be...
Karl-- Thanks for the suggestions. These will be helpful and I'll make some changes based on these when I get back around to the early chapters. Addison-Wesley...
Hi Jason-- Finding time is tough but I've been at this book since before the end of the last one. Also, I used to just take whatever deadline a publisher gave...
Hi Rüdiger -- You've got two main points so let me address them separately: IRR: I tried to point out the concerns and risks with using IRR. I'll review the...
Please don't drop the Advanced Project Economics chapter, even though you may be venturing into Boehm territory. Part of the problem is that many product and...
Thanks, Chris. I'm hopeful to get back onto the Advanced Econ chapter soon and can post it for everyone's opinion as to whether to include it or not. I've read...
Mike, In Chapter 13 you have a section entitled "A Buffer is not Padding". At this point you've described the use of a project buffer, but this is the first...
... This is what I think of when I hear "padding". Padding is a way to lash out due to fear, whereas buffer is risk management. Intent is key. Of course, Mike...
Hi Chris-- I'm glad you've enjoyed the book so far. Thanks for emailing. I guess I've heard "padding" too many times in my career to mean "extra time added on...
Having problems with message search?
Fill out this form to ensure your group is one of the first to be migrated to the new message search system.
