- Decide which method of Hardening / Acceptance will be used.
- Decide who will be Product Owner(s) and Scrum Master(s).
- Decide who is in the Core Scrum Team (committed, schedulable members) and Extended Scrum Team (non-committed, community members).
- Decide how long the Sprints will be.
- Decide how often and with what technology the Scrum meetings will be held.
- Decide how the notes/results of the Scrum meetings will be communicated, for example wiki, forum, email etc.
- Decide if the Extended Scrum Team will be involved in the Sprint Planning Session and, if so, how.
- Decide how the Extended Scrum Team will be recognized.
- Decide if daily builds will be made available for the Extended Scrum Team or if they will do their own builds from the source.
- Product Owner: Create Product Backlog.
- Product Owner: Publish the Product Backlog on the project website as a document or wiki page.
- Product Owner: Create 2-4 best-guess Sprint Backlogs.
- Product Owner: Publish the Sprint Backlogs on the project website with intended dates.
- Product Owner and Core Scrum Team: Hold the Sprint Planning Session
- Product Owner: Ask the community to participate based on their interest in the individual features in the upcoming Sprint.
- Scrum Master: Hold Scrum Meetings at the decided upon interval. Publish short notes on the project website as a Blog or wiki page.
- Scrum Team: As features are completed publish documentation / screenshots etc to project website.
- Product Owner: Perform Feature Acceptance Reviews of features from current and previous Sprints.
- Build the Milestone release and post to download site.
- Review the contributions made by the Extended team and recognize them (e.g.
- Product Owner: Create and publish the release notes.
- Product Owner: Determine if the feature set for the current release is complete. Once it is perform Sprints for bug-fixing and Acceptance Reviews only.