Skip to content

Sprint Planning Meeting 2018 08 08

Jump to bottom
Erik Moeller edited this page Aug 13, 2018 · 2 revisions

Sprint Planning Meeting, SecureDrop, August 8, 2018

Sprint timeframe: Beginning of Day (PDT) 2018-08-08 to Beginning of Day (PDT) 2018-08-22

0) Mini retro

Board review: https://github.com/orgs/freedomofpress/projects/1

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

Functional testing: What, if anything, should have been done differently during the previous sprint?

  • Scoping of tasks on the sprint backlog?
    • TL;DR I ❤️ erik
    • We re-chunked the work with Erik's help and got tons of clarity; we should have done that epic reorg much earlier!
    • We had several instances of "new" work being identified and tickets opened up; that at times muddied the waters, but Erik again provided clarity and accommodated mid-sprint ticket wrangling
    • We were inappropriately optimistic about the scope of work: it was legitimately way harder to ship than we expected.
  • Management of CI failures?
    • I think many of us don't know how CI works
    • Should have preserved CI passing throughout feature branch; don't permit failures
    • Do minimal work to get CI green, i.e. drop in TB instead of Firefox, get green builds, THEN proceed with the next piece. Otherwise we are using developers as CI ;-) (Was not possible without huge amount of changes to get at least the local tests pass). We still don't have those local tests pass in CI. The errors are not related to the functional testing. (I hear ya on the local tests not passing in CI, but I think it was possible to drop in TB instead of Firefox and get staging CI builds passing, modulo any mystery CI issues as discovered in the i18n and template_filters tests)
  • Coordination across timezones?
    • Better delination of hand-off between timezones (so we dont have to keep kushal up all night)
    • Clear test plans highly desirable. Hopping between PRs against the TBB feature branch, I needed to refer back to other tickets in order to view testing instructions.
    • Crazy idea: for long-running feature branches, perhaps a dedicated standup?
    • Kushal was several times blocked on review; more hollering at each other in standup very welcome =)
    • Conor has considered skewing work hours earlier (PT) in order to maximize overlap; maybe switching later for overlap with Kushal's morning would be useful.

1) Review important dates and time commitments.

2018-08-08 to 2018-08-10: Staff travel: Jen, Mickael, Emmanuel at DEF CON
2018-08-08 to 2018-08-10: PTO (cont'd): Kevin
2018-08-08:               PTO: Harris
2018-08-10:               PTO: Erik
2018-08-13 to 2018-08-17: Staff travel: Training team in SF
2018-08-15:               Independence day (India) \m/
2018-08-20:               PTO: Conor
2018-08-22:               Feature freeze for SecureDrop 0.9.0 begins

Time check: https://docs.google.com/spreadsheets/d/1sHXbUnInZPxtF94GXbSYDGnAcSA89QEvJJIwxHGpHS0/edit#gid=0

2) Decide on must-accomplish goals. Proposed:

  • Finish up Tor browser functional testing work to deliver useful value for 0.9.0 pre-release testing. That includes fixing CI.
  • Create critical path dependencies for SD client: API proxy, MVP of SecureDrop SDK
  • Add support for Xenial staging VMs to local environment (not CI)

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

4) Estimate and pick tasks for sprint backlog

https://docs.google.com/spreadsheets/d/1YgM8STcXM3ezTc4U_ra0qUHoGxSCYmPON7aNIMcD00I/edit#gid=0

Clone this wiki locally