Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Note: Development priorities are based on involvement and input from community members in a variety of ways. Many factors go into determining what is worked on and how. What's below focuses on how the program team translates priorities into organized development.

SprintsSprint Basics

  • Sprints are intended to help focus and organize the work of the program team developers. The work of other developers, such as contractors, may relate to what's happening in a sprint, but is not usually the focus of a sprint.

  • Three-week sprints, beginning the third second Thursday of each month.

  • Other weeks of the month will be are used to review and hone processes, work on code maintenance, and focus on other tasks and priorities not specifically linked to individual JIRA issues.

  • A sprint planning meeting kicks off the sprint and is focused on assigning issues; reporting back on the outcome of work on assigned issues happens through a retrospective (which may be a separate meeting or part of the next sprint planning meeting). Progress is also discussed in standups, short meetings held several times a week with all involved parties.

Roles

Product Owner (Program Manager): 

  • Identify overall development theme or focus for a sprint.

  • Identify JIRA issues from the prioritized backlog that relate to the chosen theme. 

  • Work with Scrum Master to ensure that individual JIRA issues are clear and assignable. 

  • Work with Scrum Master to ensure that the pool of prioritized JIRA issues for each sprint planning meeting is appropriate. 

  • Work with Testing sub-team and other testers to ensure adequate testing of issues. 

  • Final acceptance of tested issues.

...

  • Work with Scrum Master to assign story points to issues during the sprint planning meeting. 

  • Work with Scrum Master to assign the specific issues each developer will work on during the sprint.

  • During the sprint, work on and deliver issues. 

  • Report on progress with assigned issues during standups and the retrospective. 

  • During the retrospective, update story points for an issue if there was a difference between what was expected and what happened. 

...