Scrum Process

Sprints

For this project, we will use two-week sprints that correspond to each iteration meeting.

Sprint planning meetings

We meet for the first time at the beginning of each sprint. At these sprint planning meetings, we:

• Create new issues for work that needs to be completed
  • Determine which issues are within the scope of the sprint
  • Give each issue a point value using Scrum Poker
  • We all choose a Fibonacci number to represent the difficulty of the issue, and keep it hidden
  • After a count to three, we all reveal the numbers
• We discuss the point value the issue should have based on the numbers that the team revealed
• Assign a team member to each issue

Sprint scope

Once we decide what issues are in a particular sprint, no more issues should be added or taken away.

Stand-ups

On weeks when we're meeting and not having sprint planning meetings, we will have a "stand-up" where we discuss the current sprint. Each team member discusses the following:

• What they're currently working on
• Risks: issues or pieces of work that might not be finished by the end of the sprint
• Blockers: work that other team members need to complete first before the team member can finish their own work

GitHub Issues

To keep track of work, we will use GitHub issues.

Milestones

We will use Milestones for each sprint to identify which issues need to be completed.

Labels

• front-end: front-end issues
• back-end: back-end server and cacheing issues
• library: protocol and Python FreeJournal library issues
• N-points: indicates the amount of work required for this issue
• needs-review: this issue is done, but someone should review it before it gets merged in.