Data/Platform/General sprint info

Firefox data platform sprint information

The purpose of this doc is to detail the sprint process used by the greater Firefox data team - which includes client, pipeline and devOps engineering.

Who this affects

Teams working on Fx Data Platform: measurement, quality engineering, devops

We currently run 2 sprints:

• Desktop telemetry / Mobile telemetry
• Atmo / pipeline / devops

Breaking down the process

• Our sprints are 2 weeks blocks of work, start on a monday and end on a friday (see sprint calendar here)
• Packing a sprint requires a groomed backlog
• Packing a sprint requires engineers on the team to understand their own capacity.
• Use IRC to communicate challenges or dependencies on other teams/engineers (we are not currently doing a daily stand up)

Grooming and packing

• Teams meet to groom backlog weekly
• Teams meet biweekly to pack sprint

what do I need to do in order to prepare for sprint packing?

understand your capacity

• how many days do you wish to pack/commit to the sprint versus how much time you want to reserve for interrupts, mentorship, meetings etc?
  • for example: Jane is going to commit to 6 days of packed items, and will reserve 4 days for mentoring, interrupts and meetings. However - during the sprint, there were fewer interrupts than expected (hahahahaha). As a result, after finishing her committed P1’s, she grabbed a few P2’s off the stack and does those as well.

How we use bugzilla

Priority flags:

• P1 means current sprint (these are commitments - do not roll something to a P1 unless you believe you can get to it current sprint)
• P2 means next sprint/this quarter (also the pile to pull off if you have extra time and all your p1's are complete)
• P3 is next quarter
• P4 is quarter after that
• P5 z_later

Sizing (Points)

• small is < 1 day (1 point)
• medium 1-3 days (2 points)
• large = > 3 days (3 points) NOTE: it may make sense to break down large items into more actionable chunks - we'd like to avoid a scenario where the same bug spans multiple sprints (this does not apply to meta bugs)

Notes

• Over commit to a sprint? Talk to your team/make it known you won't be able to hit your commitments
• need to be added to a triage/grooming or sprint packing meeting?
  • Pipeline - contact :thuelbert (thuelbert@mozilla.com), Rob Miller (:RaFromBRC) or :kparlante
  • mobile or desktop client - thuelbert (thuelbert@mozilla.com) or :gfritzsche
  • devOps - thuelbert (thuelbert@mozilla.com) or :kparlante
• Remember other groups may be dependent on our work and using priority to track when its done. As a result, its important for the ticket to reflect when it will be worked on.

Sprint status:

• week_of_august_1