Skip to content

Sprint Planning Meeting 2018 04 04

Jump to bottom
Erik Moeller edited this page Apr 5, 2018 · 3 revisions

Sprint Planning Meeting, SecureDrop, April 4, 2018 Sprint timeframe: 4/4 BOD-4/18 BOD

0) Mini retro (max. 30 mins)

What did we get done? Burndown: https://docs.google.com/spreadsheets/d/1dCbE4PrhVTjOHf_QrVQj43Wkx7ViClAK4R4WhCHiq9A/edit#gid=103941931 Tasks: https://github.com/orgs/freedomofpress/projects/1 - partial or completed Let's also celebrate work beyond the sprint, and recognize how much we got done. :)

How accurate were our time commitments? How can we improve accuracy? https://docs.google.com/spreadsheets/u/1/d/1suD_hQApz2cAm3JT4AZLmgsnuzpYWotgvudE3keulqs/edit#gid=0

How accurate were our estimates? How can we improve accuracy? (Review estimates on tasks that were completed. Were they off base?) https://docs.google.com/spreadsheets/d/1dCbE4PrhVTjOHf_QrVQj43Wkx7ViClAK4R4WhCHiq9A/edit#gid=0

What, if anything, can the PM or the team do to better protect time from interrupts? -> Handle some of the issues/PR triage -> More decomposition/analysis of issues -> update PR autoresponse to make it clearer how we work :)

What, if any, process changes do we want to make?

1) Review our time commitments

https://docs.google.com/spreadsheets/d/1BxpSjKa6GsUG-erEPApm9hhkPtzwQT2KpBSWvYNjOLg/edit#gid=0

Ensure we capture PTO/unusual holidays.

2) Review our tools

Board: https://github.com/orgs/freedomofpress/projects/1?fullscreen=true Task Estimation: https://docs.google.com/spreadsheets/d/1KoagbdTUOi8LhY2T1ChGhyAb2LOgvyFicr4gVDlncyE/edit#gid=0

Task scores: 2, 4, 8, 16, 32

3) Agree on the primary sprint goals.

  • Finish work from previous sprint (we may choose to deprioritize some tasks)
  • Get majority of team members up on Qubes dev env
  • Prep new SD.org for launch (complete Switchover tasks)
  • Work w/ Heartsucker to merge DB migrations work into branch

4) Agree on the rules of engagement

We try to stick to the sprint backlog except for:

  • urgent bug fixes [outage level]
  • urgent security fixes
  • quick (< 1 hour) community PR merges + comments -- alternatively, communicate that PR will be handled next sprint
  • responding to issues

We may run out of tasks that one team member can work on! We will keep an eye on our velocity and may do mid-point adjustment.

5) Estimate and pick tasks for sprint backlog

6) Any immediate blockers we should discuss?

Clone this wiki locally