Two new chapters are finally available. The first is either all or part of the preface or becomes Chapter 1. It's "Why Estimate and Plan" and the second...
Yes, I think it's because people tend to underestimate. --Mike Cohn Author of User Stories Applied for Agile Software Development www.mountaingoatsoftware.com ...
I have a question on Use Case Points. For example, When I say a system is of 100 use case points and I use a productivity number of let us say 15 hours/ucp,...
It all depends where you got your numbers from. When you estimated how many points your use cases would take to develop, were you just estimating the software...
... As Rachel already mentioned, your use case points and productivity number can include whatever you have defined them to include. Are you getting the...
Raj-- Karner's original recommendation of 20 hours per use-case point was for (as Paul points out) from use case to finished product, so it includes ...
Mike, Paul and Rachel: Thanks for your response. I was trying to co-relate UCP as a measure ala' FPs. In my current organization, we typically look at the size...
Hi Raj-- I struggle with whether to include the chapter on use-case points in the planning book. They are worth knowing about but I've experienced similar ...
Some comments on chapter 8. When to re-estimate: I have encountered some situations where estimates have been made by people who do not know the code, stories...
Hi Rachel-- Thank you for all the comments. You make some good points--particularly about spiking before estimating if necessary. I agree too with the point ...
Re-estimating is a thorny subject and a slippery slope, and I think the chapter does a great job of sorting out the issues. The one question I have is, would...
Hi Lisa-- I would re-estimate any time that (a) my features/stories needed it *and* (b) there was going to be sufficient return for the investment in greater ...
I've been wrestling with a question about how to organize the book and would like to solicit everyone's feedback. I'm really trying to make the point that...
... For starters, how about including a motivation such as the one above in the introduction chapter of the book. ( explaining the structure you'll eventually ...
If you use one approach in the body of the book and cover the differences at the end, then I think it would be a good idea to briefly mention all three ...
Mike, Is there one approach you prefer? For example, I remember one draft chapter where you compare UCs to User Stories and then summarize your preference for...
... and would ... <description snipped> ... organized? I've not really thought this through, but throw it out to see if it goes anywhere... I've just read...
My vote too. From distant and probably inaccurate memory (I've left the book at work) I think Alistair Cockburn's talks about people who are at various levels...
I too think that many newbies (and some of us in the middle) will be looking to this book for guidance. In almost all of the agile texts I've read, I feel...
... it ... perspectives; ... That's funny, right before I read this I picked up Alistair's book too to see if I could apply his structure to Mike's book. I do...
Mike: From where I sit, I would prefer to have the fundamentals of what you are suggesting, with exercises that get folks to understand the core of planning as...
Thank you to those who replied with my question about the organization of the book. I appreciate your time and thoughts and I've been thinking about it more....
Would it be worth it to show how high level planning (DEFINE, PLAN, EXECUTE, DEPLOY, IMPROVE) provides a framework for experienced based gut guesstimation and...
... (That seems logical since we estimate before we plan.) However, in my classes and tutorials on this over the past few months I train a fair amount on...
hi mike, just read the re-estimating the chapter. i really like that you used user interface stories as the example of stories that might need to be ...
Owen Rogers
exortech@...
Jan 30, 2005 2:52 pm
179
That sounds like a good idea. It helps to give people a bigger-picture view of where things will fit in. Richard (Dick) Scheel Richard@... ...
Owen-- Great point. I will add something about this in the Re-Estimating chapter. Thanks, --Mike Cohn Author of User Stories Applied for Agile Software...
Hi Mike- I don't really want to spend much time discussing the need to get *better* at estimating because the main approaches I describe (ideal time and ...
Yes, it does. Based on the feedback I've received I'm going to try restructuring the book in this way. Even though I'd figured this out when I present the...
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.
