Sprint Planning Meeting 2018 05 30

Sprint Planning Meeting, SecureDrop, May 30, 2018

Participants: Jen, Erik, Kushal (partial), Mike, Mickael, Harris. Absent: Conor (PTO)

Sprint timeframe: 5/30 BOD-6/13 BOD

0) Mini retro (max 15 minutes)

What did we get done? What do we want to change?

0.7.1 and kernel issues: kernel upgrades still significantly more challenging than anticipated, even with a more recent baseline.

• Potentially testing SecureDrop kernels in CI
• Use of Google Cloud in CI expands our options, since we can now run grsec kernels

How can we increase predictability/maintainability here?

Other actions:

• Vet binary wheel packages during QA process as mitigation against #3270

1) Review important dates:

EOD June 12: Feature freeze / 0.8.0 QA begins (0.8.0 Release date: June 26)

By previously agreed process, this means we should prepare big PRs (e.g., Alembic) early in this sprint, so they can get sufficient review prior to the feature freeze.

2) Review our time commitments

Ensure we capture PTO/holidays (incl international).

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

3) Review our tools:

Board: https://github.com/orgs/freedomofpress/projects/1 Task estimation: https://docs.google.com/spreadsheets/d/1XvB6mMobxM1FkNpgdm8EHYnpoWzZzG5UNwHhztFeEx4/edit#gid=0

4) Decide on sprint goals. Proposed:

• Finish up securedrop-admin testing improvements
• Land alembic in develop
• Prep for round 2 of SecureDrop.org (landing page scanner)

5) 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

6) Estimate and pick tasks for sprint backlog => screenshare

Consider tasks not in the spreadsheet: bugs, PRs, other urgent issues