[ ] Define interrupt
[X] My initial working definition
[X] Terry's three categories
[ ] MPL definition
[ ] Agreement in mailing list, Terry/Lila, and within TPG on definitions
[ ] Document all alternative definitions (inward/outward, new vs existing, scale until not doing it has impact)
[ ] recommended SOP (do it in triage?)
[ ] engagement
[ ] followup
[ ] report on data weekly or per-sprint
[ ] cross-check other teams' data?
Roll out:
[ ] make list of participating teams
[ ] Pick one (Candidates: FR-tech, Analytics, RelEng)
[ ] All three
[ ] Open call
[ ] Try to get a mix of teams: feature teams, interrupt-driven teams, atypical teams, to test assumptions from mailing list. Mobile? Collab? Language?
[ ] Try to have data to show at Engineering off-site in late August
Does a team work mostly on the projects they intend to, or is most of their work in reaction to interruptions? Teams with different purposes may have different ideal ratios.
How can we measure the ratio for a team? Average age of story is part of it, but we are looking for teams that have old stories that continually get bumped by new stories. Ratio of story lifespan for recently Done stories to average age of the backlog?
What are ideal ratios for different teams?
What interventions are indicated by different results?
... [ ] document open questions and get answers where possible