Changes

== Sprints ==

== Sprints ==

* Have a defined start and end date lasting 3 weeks, ending on a Friday. When one sprint ends, the next one immediately begins.

* Have a defined start and end date lasting 3 weeks, ending on a Friday. When one sprint ends, the next one immediately begins.

* It begins with a 2 - 4 hour sprint planning meeting, which includes all developers, the scrum master and product owner(s). Short planning meetings may be necessary for specific products/projects to make better use of everyone's time. These are the guidelines on amount of effort for unplanned work during a Sprint

* It begins with a 1 hour sprint planning meeting, which includes all developers, the scrum master and product owner(s). Short planning meetings may be necessary for specific products/projects to make better use of everyone's time. These are the guidelines on amount of effort for unplanned work during a Sprint

** 20% for being humans (admin work, content switching, bathroom breaks, etc)

** 20% for being humans (admin work, content switching, bathroom breaks, etc)

** 15% for skills development, learning, training and R&D activities

** 15% for skills development, learning, training and R&D activities

** 15% for special requests

** 15% for special requests

*Each day of the sprint includes a 15 minute scrum starting at 10am via Zoom. The development team are the only ones required to attend the daily scrum. If people aren’t able to attend, they will post a summary in Slack prior to 10am. A daily scrum answers these questions:

* Each day of the sprint everyone on the team posts a status update. Every Wednesday everyone on the team joins a 15 minute scrum starting at 10am via Zoom. A daily status update answers these questions:

** What did I work on yesterday

** What did I work on yesterday

** What am I working on today

** What am I working on today

** What do I need help with

** What do I need help with

* At the end of the sprint a 1 hr sprint review will be held. Short review meetings may be necessary for specific products/projects to make better use of everyone's time. The sprint goals will be evaluated against the definition of done.

* At the end of the sprint a 1 hr sprint review will be held. Short review meetings may be necessary for specific products/projects to make better use of everyone's time. The sprint goals will be evaluated against the definition of done.

* A 2 - 4 hr retrospective will be held which the development team are the only ones required to attend. This will include constructive conversation around:

* A 1 hr retrospective will be held which the development team are the only ones required to attend. This will include constructive conversation around:

** What worked this sprint

** What worked this sprint

** What didn’t work this sprint

** What didn’t work this sprint

These are the tools we will use to manage our product and sprint backlogs, for release and/or sprint purposes, and daily tasking.

These are the tools we will use to manage our product and sprint backlogs, for release and/or sprint purposes, and daily tasking.

* GitHub Issues

* GitHub Issues

* Aury to investigate other tools

* GitHub Projects

[[#top| [ Top ]]]

[[#top| [ Top ]]]