Skip to content

Sprint Planning Meeting 2018 05 02

Jump to bottom
Erik Moeller edited this page May 2, 2018 · 1 revision

Sprint timeframe: 5/2 BOD PDT-5/16 BOD PDT

Participants: Conor, Jen, Emmanuel, Erik, Freddy, Kushal, Mickael, Mike, Harris, Josh

0) Mini retro (max 15 minutes)

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

Discussion about how to handle review of big changes prior to a release (examples from 0.7: SSH over local network, GUI updater - dozens of commits in a single PR).

Consensus: We need to have at least one full sprint prior to the sprint that includes the feature freeze for review of big PRs. If not ready for review, that PR will be deferred to next release. The motivation for this process is to create more predictability for big changes.

Burndown: https://docs.google.com/spreadsheets/d/1AKoc9EkvRhwrAqh9YzJKCm-tO38OADCzGwRVrrZIW0w/edit#gid=103941931

Tasks: https://github.com/orgs/freedomofpress/projects/1

1) Review important dates for this release:

  • 0.7 Release: May 8, 2018 (Tails 3.7: May 9, 2018)
  • PyCon: May 9-17, 2018 (Kushal attending most of it, Jen partially attending)

2) Review our time commitments

Ensure we capture PTO/unusual holidays.

https://docs.google.com/spreadsheets/d/11x4oi32Vni0kLnzT4N6HKf5hwnhLl1XKLgr8U9Sbfw8/edit#gid=0

3) Review our tools:

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

4) Decide on sprint goal. Agreed:

  • Release SecureDrop 0.7 without earning a new FooInstall moniker :)

If no major release issues:

  • Begin work towards merging big deferred features (local automated upgrade testing, Alembic)
  • Start shifting more dev team time to workstation development

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

However, some large items in the backlog (e.g., QA) will unpack into sub-tasks that can be added to the sprint for tracking purposes.

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

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

7) Any immediate blockers we should discuss?

(Brief discussion of current tasks followed.)

Clone this wiki locally