Hi Robin, Am 20.01.2010 10:10, schrieb robin.sedlaczek:
1. How to finish a sprint? Following the process means for me that the Product Owner reviews the implemented Tasks, User Stories and Requirements. If he accept an Requirement or User Story it must somehow be closed. How to do that for a sprint?
The product owner usually only reviews user stories. The tasks are only to help the team but in the end, the PO is only interested in user functionality so the tasks don't matter in the demo.
Tasks can be closed in the whiteboard. For User Stories and Requirements, you can go to the edit mode and close them - this also gives the team/PO a moment to really read to story so you're sure that it is really implemented.
2. What about not accepted Tasks, User Stories and Requirements? Will they somehow go to the next sprint? Can I "replan" such Tasks, User Stories and Requirements in the next Sprint meeting?
It depends on the team/PO if they are still useful and should go in the next sprint. If you close a sprint, you can retarget all open one to the new sprint.
3. After reviewing of all Tasks, User Stories and Requirements, how to close or finish the sprint (please see first question)?
To close a sprint, go to Roadmap and click on the Sprint name. There you see the interface to close a sprint.
fs
smime.p7s
Description: S/MIME Cryptographic Signature
