Hi Jerome, Am 04.02.11 09:59, schrieb jmb: >> This looks like your PO is indeed working as a team member in the scrum >> team which is great. >> >> I would suggest that you do not accept stories directly (neither the PO >> nor individual developers) but instead just change the status of the >> story and use tasks for all of the tasks included. This would mean: >> >> - Two tasks in the beginning: 'Write Documentation' and 'Review >> Documentation' >> - One Team member writes the docs, and then asks another (the PO in this >> case?) to start the second task 'review'. (Maybe this doesn't need to be >> to all eternity? Your Work agreement could maybe just specify a 4 eyes >> principle for documentation?) > > I am not sure what you mean by that. Once the PO has proof read a > document and agrees with the contents, he simply closes the story. > > On re-reading what I wrote above, there might be a misunderstanding on > the word “accept”. I meant it in the Trac sense of checking the > “accept” radio button, not in the Scrum sense of “accepting the story > as done”. Is that where your question comes from?
Ah, sorry there's a lot of confusion that can stem from this slight mismatch in terminology. :/ Trac Accept means that the ticket is assigned to yourself and that you are working on it. Scrum Accept would mean to close the ticket (story) as fixed. Scrum reject would be to set it to 'new' again and put it back in the backlog (or add more tasks if the sprint is still ongoing). The thing is that we do not recommend to "trac accept" stories ever as all the work should happen on task level (and you "trac accept" those when you work on them). Does that make more sense? -- Regards / Mit freundlichen Grüßen Martin Häcker Software Engineer Agilo Software GmbH Gruenberger Str. 54 10245 Berlin, Germany [email protected] http://www.agiloforscrum.com Amtsgericht Charlottenburg: HRB 127146 CEO Marion Eickmann, Andrea Tomasini -- Follow Agilo on Twitter: http://twitter.com/agiloforscrum Please support us by reviewing and voting on: http://userstories.com/products/8-agilo-for-scrum http://ohloh.net/p/agilo-scrum http://freshmeat.net/projects/agiloforscrum You have received this message because you are subscribed to the "Agilo for Scrum" Google Group. This group is focused on supporting Agilo for Scrum users and is moderated by Agilo Software GmbH <http://www.agiloforscrum.com>. To post to this group, send email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo
