I just posted Chapter 15 on Iteration Planning. It's available at http://www.mountaingoatsoftware.com/agileplanning/ I'd appreciate hearing any thoughts or...
Mike: I read with interest Chapter 6 on Use Case Points. I work with a Systems Integrator organization and even though we do not use XP, we have been using UCP...
Hi Raj-- Thanks for taking the time to read and send me your comments. Ever since I wrote the chapter on use-case points I've wrestled with its placement in...
A big thumbs up for the use of cards for testing tasks!!! The examples in this chapter are clear. I think even readers who are new to agile will understand...
Thanks for the suggestion, Lisa. I'll add some further advice on breaking work into sufficiently small pieces. I find that almost all programmers start by...
Using story points to estimate, you mention that you start with a medium-sized story and use a scale appropriate to the diversity of story sizes you have. You...
Hi Simon-- Thanks for the question. The main drawback to a Fibonnacci scale is that you can't make "twice as" and "half the size of" like comparisons. If you...
Hi Mike, This is awesome content and I'm glad you are sharing it with the community. I've had to claw and scrap the content you have over the past three...
Thanks, Bill. I'm glad you've enjoyed the chapters so far. I appreciate the pointer to Tony Rizzo's site. I'll join one of his webinars to learn more. I'll...
Hi Mike, This is great stuff. Your ideas on Story Points and then digging into the details during the estimation planning meeting is something I can probably...
And then I read farther down the outline - doh. Maybe section 4 needs to be renamed to something that gives the impression that it's about the execution phase....
We've been using ideal time for stories and tasks. I read "you should not be surprised or worried if your iteration includes two stories each estimated at 3...
We've been using ideal time for stories and tasks. I read "you should not be surprised or worried if your iteration includes two stories each estimated at 3...
Yikes! It took me a long time to get back to this... ... table of ... for 300 so ... needs to ... Je n'ai fait celle-ci plus longue que parce que je n'ai pas...
Jason-- Thanks for the clarifications. Have a good weekend, --Mike Cohn Author of User Stories Applied for Agile Software Development www.userstories.com ...
Chap 13 Not sure if this is relevant but I've recently observed a project team that seemed to be operating on a fixed budget sort of like how support teams...
Thanks, Jason. You might be right about seeing with more than one person. I've seen it work with one but I've more often seen the one person overwhelmed by the...
Hi Bill-- Thanks for your comments. I've used feeding buffers on agile projects, but only ones with 8+ teams of 5-7 people on each. When I do, I leave the...
Hi Simon-- Thanks for your comments. You're right that the 12-31 example is probably too extreme. Here's my point: A lot of teams seem to think that if they...
Thanks Mike. While i'm digesting this and scratching my head, it's not clear whether you advocate using ideal programming time to estimate engineering tasks or...
I never estimate anything in calendar time. I'll work on the text to make that more clear. --Mike Cohn Author of User Stories Applied for Agile Software...
By the way, I forgot to ask, is there something I can clarify that will ease the scratching of your head? I have a feeling that this discussion is extremely...
Taken individually the concepts of magnitude and ideal time are easy to understand. Personally, i've always used ideal time because it's more tangible, more...
I've posted a new chapter on "tracking progress" at http://www.mountaingoatsoftware.com/agileplanning/. It's chapter 17. This chapter includes a discussion of...
Hi Mike, This chapter was a good read. I liked the sail boat metaphor for navigating a project. I also took interest in your "Task Board" approach. Once...
... 17. Mike, I really like this chapter a great deal. As I was reading your sailing analogy I realized that it also helps me explain the problem with...
the idea of a burn down chart for an iteration is great. I'm going to draw it up as soon as i get back in. I hope it will help the team measure themselves...
The chapter gets off to a great start by reminding me of a song I really like and a book I really liked (_Longitude..._) All the analogies are great, the lawn...
... A real task board could even benefit from using colors for these. Let's say a red X for stuff not tested and a green checkmark for tests that are done. ...
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.
