5894OT: Re: Concurrent work in product backlog
- Jan 6, 2005lol
I followed your link to see what your book is up to, Mike. I was
excited to see that your Appendix includes "Answers to All Question"
!!! How wonderful, I have lots of questions. For starters... a
Canadian conundrum: it's freezing rain outside - should I drive or
take the streetcar? :-)
But then I realised that there IS NO DOWNLOAD LINK for this chapter...
oh, how disappointing. Guess I'll just have to buy the book :-D
Happy new year, Mike, and thanks for all your help and input here.
Hope 2005 brings you lots of royalties.
(Happy new year, all... may 2005 bring you wonderful surprises!)
--- In firstname.lastname@example.org, "Mike Cohn" <mike@m...> wrote:
> I hate to steer you toward a book again. But, hey, this one's free (for
> now). See http://www.mountaingoatsoftware.com/agileplanning/ and look at
> Chapter 10, "Simple Release Planning." It should address your
> you may want to read the earlier chapters (on estimating, especially in
> Ideal Time, since it sounds like that's what you're doing).
> --Mike Cohn
> Author of User Stories Applied for Agile Software Development
> -----Original Message-----
> From: the_heidster [mailto:the_heidster@y...]
> Sent: Wednesday, January 05, 2005 7:46 AM
> To: email@example.com
> Subject: [scrumdevelopment] Concurrent work in product backlog
> Folks - I am creating my first product backlog. I know that the
> estimate for each requirement/feature should be done in days.
> Questions, do I just add up the days to estimate the completion
> date? This would indicate that each day is consecutive. How does
> this take into account concurrent work (or does it?) Also, by what
> criteria should I decide the "adjustment factor"? How important is
> the adjustment factor?
> To Post a message, send it to: scrumdevelopment@e...
> To Unsubscribe, send a blank message to:
> Yahoo! Groups Links
- << Previous post in topic Next post in topic >>