Suggested Reading:
- Scrum Overview ( a longish guide from the Scrum Alliance )
...
I've setup this Scrum Board in JIRA.
Members:
- ScrumMaster
- Product Owner(s)
- Testing Lead ( and any other testers wishing to join )
- Developers
- Documentation Writers ( if they wish )
- Bug Wranglers ( if they wish )
- Anyone wanting to take on tickets
Anyone is allowed to join the meetings, but only those willing to take on work assignments can participate.
I've setup this Scrum Board
Call should be at least an hour, with half hour for retrospective ( closing a sprint ) and planning ( starting a sprint ). The first half of the meeting is a retrospective, where we go over the work the was completed, not completed, and rejected. This is also where we can talk about things that are working or not working or need improving.
Second half of the meeting, we plan the next sprint.
...
The planning session starts with the ScrumMaster going through the list of tickets in order, asking the PO questions to clarify. Tickets do not have to be totally specified before the call, but it would be appreciated ( we can do it during ). Teams member have the chance to ask questions, voice concerns or support, etc. The Scrum Master and PO will both try to document the "What does done look like" for each story and bug, so that everyone is on the same page ( PO, developers, teststesters, etc )
If someone agrees to take the ticket, it will be dragged up into the sprint and assigned, The assignee will estimate the amount of effort required to complete the ticket.
...
The sprint is planned once all the participants have filled up their point quotas or the meeting has run out of time.