Am 06.05.2010 18:39, schrieb boflynn:
Maybe I'm missing something, but if I go into Agilo and accept a user
story, the underlying user tasks aren't accepted. I also have to go
into each task and accept them?
Of course!
In Scrum, you commit to a number of stories and put these into your
sprint backlog (by setting the sprint, pressing 'confirm commitment').
If you like to 'accept' the story you can do that but from a Scrum point
of view it is not necessary.
Afterwards the whole team will work on the tasks of that story. If a
team member starts working on a task, he can accept it.
It is a common mistake of new scrum teams to assign one person per user
story.
Also once I've finished all the tasks, the user story doesn't move to
complete/testing/etc. I have to do that manually?
Yes, because:
In Scrum, a story is done if the implementation fulfills the user need
and meets all conditions of satisfaction. It does not matter in which
state all the tasks are. Therefore we want to have a manual step at the
end (closing the story) so that the team is forced to read the story
again and check if they really fulfilled the story.
fs
--
--
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 received this message because you are subscribed to the Google
Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH
http://www.agile42.com and is focused in supporting Agilo for Scrum users.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/agilo?hl=en
