This is a living outline—you can add screenshots, links, and richer notes whenever you like.
Repository setup
- Create a repository and give everyone access.
- Developers clone the repository to their machines.
-
Optionally protect
main(branch protection rules) so merges only happen through reviewed pull requests.
Plan and prioritize
- Read the project requirements together and discuss how to split the work into small issues.
- Create issues with as much detail as possible (scope, acceptance hints, links).
- Discuss and agree on priorities.
- Assign each issue to one person or a small group (two or three people maximum).
Research and develop
- Record on the issue everything relevant: research notes, decisions, and progress on development work.
- Everyone assigned to an issue starts a branch for that work (named consistently with the issue).
- Add findings and write-ups as Markdown files on that branch as you go.
Review and merge
-
When the work for an issue is in good shape, open a pull request toward
main. - A different person or group reviews the PR, requests changes if needed, then approves.
- Merge the PR (following your branch-protection rules if you use them).
Keep going until done
- If issues are still open, people or groups take the next available issue and repeat the same cycle (branch → work → PR → review → merge).
- Continue until all planned issues for the goal are addressed.
When the sprint ends
- Everyone joins the retrospective: reflect on how the work went and plan adjustments for the next sprint (see game rules for timing).