Mike, Please forgive me if you've addressed this in your draft, but one of the challenges I had to deal with last year was the impact of acquiring needed...
... I agree. This is as much an investment (or more) than pure software development for some organizations. The agile practices to my knowledge have not gone...
Hello-- I guess I didnąt think I was ignoring these topics in the book but I can see how it looks that way. In my mind, if a project uses a third-party ...
Mike, One thing to consider from that perspective are those projects where the majority of the work is selecting, acquiring, installing and integrating a piece...
I suspect that much of the book will cover acquisition projects but there is nothing specific in the book about such projects, just as there is nothing ...
"In my mind, if a project uses a third-party technology there is going to be at least one user story about that technology." What might that story say? ...
It really depends on what the technology is. I'm working with a client right now who has signed a huge contract to buy ClearQuest, the defect tracking system...
To extend the example to help my understanding... So say that Clear Quest meets the story out of the box. In a development project, you would pull that story...
To stick with this real case, ClearQuest is a very complex install. The process will take months with various configuration options being set, etc. For the...
... I'm thinking about two scenarios. The first is a team I worked with last summer. They were told by the company essentially to use a specific commercial...
Hi Mike, First off, I'm honored to be the topic of the side bar in chapter 5, page 53! ;-) A couple of additional comments: The difference is a procedural vs....
I've posted two updated chapters: 13 - Planning the Multi-Team Project 14 - Tracking Progress Also, since it's a book on planning, it's only fair that I post...
Hi Patrick-- I think we're saying we use the same approach. I don't typically have a user story that says "Set up ClearQuest." Instead it says "Let users do...
Hi Paul-- Thanks for the clarification and additional information. I'll add some more explanation of the benefits and motivation into that sidebar when I start...
Hi Mike, I am not fully sure whether you have already done so, but I feel you could include the scope vs schedule vs Cost balancing nature of Agile (Include...
Sridhar-- You are correct that I haven't correctly set this out as a fundamental issue. I plan to better address this in one of the first chapters. Thanks, ...
Hi, Is anyone aware of any work, papers written on how to estimate project effort using agile methodologies such as XP? As this information is required in...
Take a look at www.mountaingoatsoftware.com/agileplanning or at www.agilealliance.org/articles. Mike Cohn Author of User Stories Applied for Agile Software...
Mike, I was reading Chapter 5 (Iteration Planning) hoping it would help me give better advice. I notice in the section titled "From features to tasks" you have...
Hi Mike-- Good questions. First, that list isn't meant to be sequential. I'll mix it up in the next draft so it doesn't look that way. My recommendation is...
When I teach or coach iteration/sprint planning with a team, I like to discuss with them two approaches to task breakdowns -- a "horizontal" approach and a...
Hi Mike, Excuse me if this has already been addressed, but I didn't see a topic on budget forecasting in the PDFs published to date. I did a talk at a...
I have been struggling with providing my various product owners with a reasonable (that is they can explain it back to me) explanation about the duration of an...
Paul-- Fantastic distinction. I tend to guide teams toward what are considered by others to be very small stories (typically 2 to no more than 5 days of work ...
Hi Victor-- That topic is covered in the "Buffering Plans for Uncertainty" chapter. In that chapter I write about how to estimate a schedule (and staffing...
Interesting strategy Ron! In my own personal experience, iteration length has been bounded from above and below by the answers to the following two questions: ...
Interesting notions, Brad ... ... We differ here, on two grounds: First, I have found that shorter iterations are almost always "better" (TDB if interesting); ...
Interesting notions, Brad ... ... We differ here, on two grounds: First, I have found that shorter iterations are almost always "better" (TDB if interesting); ...
Thanks Mike, I look forward to reading it, I'll check back periodically. Great work, btw, this book is a long time coming. -- Victor Szalvay ... chapter. In ...
The more skilled the team, the faster they'll go. Therefore more gets done in an iteration and it's risky to go too long. I completely disagree with extremely...
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.
