Search the web
Sign In
New User? Sign Up
agileplanning · Agile Estimating and Planning
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Show off your group to the world. Share a photo of your group with us.

Best of Y! Groups

   Check them out and nominate your group.
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.

Messages

  Messages Help
Advanced
Chapter 1 Comments   Message List  
Reply | Forward Message #18 of 442 |
RE: [agileplanning] Chapter 1 Comments

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 work. I’m generally calling it a “user story or feature.” I’m reluctant to take a position that you *must* use stories to do agile plans so I’m using the more generic “user story or feature.”  Scrum, for example, lets you put anything you want on the product backlog and it’s still agile. It’s a bit easier if it’s mostly stories but that’s up to the team. I contemplated including a chapter on user stories near the beginning but settled instead for introducing them in chapter 2 and giving them a page or two of description there. Do you (or anyone) have an opinion about whether that’s adequate or too much or too little coverage of user stories as the preferred unit of work and planning on agile projects?

 

Thanks again for reading,

 

--Mike Cohn

Author of User Stories Applied for Agile Software Development

www.userstories.com

www.mountaingoatsoftware.com


From: Chris Gardner [mailto:chris_gardner76@...]
Sent: Monday, July 05, 2004 3:37 AM
To: agileplanning@yahoogroups.com
Subject: [agileplanning] Chapter 1 Comments

 

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 use the "task" in the figure.  "Story" was not
introduced previously.  Moreover, since you are talking about
traditional plans in this chapter, consider postponing using "story"
until you get to the agile approach.  See comment 3 for a related
issue.

2.  In "Multi-tasking," you may want to add a comma beween the "and"
and the "if" in the following sentence:

"We're rarely blocked on more than one task at a time and if
working on three or more concurrent tasks, the context-switching time
becomes a much more tangible cost and burden."

3.  Question 1.1 presents "stories."  Since (I think) there was no
mention of stories in the chapter (except for Fig 1.3), consider
moving this question to another chapter.  That chapter should be one
in which you talk about what stories are, why you should use them, how
they can make activities more independent, and how they can aid agile
planning.  Hence, you will have set up the context for question 1.1,
hopefully without having rewritten your User Stories book.  If nothing
else, question 1.1 should come after your first official use of the
term "story."

4.  Question 1.2 refers to the Central Limit Theorem.  Most of your
readers probably understand statistics, but consider having an
appendix that describes the statistics you use in the book.  If
nothing else, you may want a footnote that describes the Central Limit
Theorem and points to where the reader could get more information.
Also, is there context for the Central Limit Theorem in the chapter?

Chris





Mon Jul 12, 2004 10:19 pm

mikewcohn
Offline Offline
Send Email Send Email

Forward
Message #18 of 442 |
Expand Messages Author Sort by Date

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...
Chris Gardner
chris_gardner76
Offline Send Email
Jul 5, 2004
9:37 am

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...
Kent J. McDonald
KentMcDonald
Offline Send Email
Jul 11, 2004
5:30 am

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...
Mike Cohn
mikewcohn
Offline Send Email
Jul 19, 2004
9:14 pm

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...
Mike Cohn
mikewcohn
Offline Send Email
Jul 12, 2004
10:19 pm
Advanced

Copyright © 2009 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines - Help