You are browsing a read-only backup copy of Wikitech. The primary site can be found at wikitech.wikimedia.org

Fundraising/tech/DRI: Difference between revisions

From Wikitech-static
Jump to navigation Jump to search
imported>Greg Grossmeier
 
imported>Greg Grossmeier
(Greg Grossmeier moved page Fundraising/tech/DRI to Fundraising/Team processes/DRI: missed this directory)
 
Line 1: Line 1:
In August of 2022, the Fundraising Tech (FR-Tech) team began incorporating a Designated Response Individual (DRI) model.
#REDIRECT [[Fundraising/Team processes/DRI]]
 
== What is DRI? ==
For each sprint, there are 2 individuals designated as the DRIs; a primary and secondary.
 
These two individuals are responsible for fielding the interrupt and reactive work, along with some other work.
 
The goal is to reduce the interruption on the engineers doing the feature-driven sprint work.
 
== General Responsibilities ==
=== In scope activities ===
* Incident response, management, and retrospectives
* Failmail/Fraudmail
* Chores list - {{PhabT|258527}}
* When time available:
** Proactive investigations into sustainability work, eg: performance, testing, technical debt.
 
=== Out of scope activities ===
* Major refactors
 
=== Day-to-day process ===
* Task tracking (kanban): [[phab:project/view/6067/|Fundraising Tech DRI]]
 
== Rotation ==
[[File:FR-Tech - DRI Rotation.svg|500px]]
 
Everyone rotates every 2-week sprint:
* Engineer n -> Engineer n+1 (no effective role change)
* Engineer 4 -> Secondary DRI
* Secondary DRI -> Primary DRI
* Primary DRI -> Engineer 1
 
A full rotation occurs every 6 sprints, which is about every 3 months, so about every quarter.
 
== DRI Roles ==
There are two DRI individuals, a primary and a secondary.
 
When someone transitions from feature work to DRI work they start as the secondary. This is to allow any incidents that started in the previous sprint to have continuity by the now-primary DRI. The secondary can then get up to speed from the primary.
 
=== Primary ===
* Primary incident response.
* Shares relevant updates with Secondary DRI.
* Proactive investigations
 
=== Secondary ===
* Transitioning from feature work duties to DRI duties,
** eg: final code-reviews, hand-offs, or similar.
* Reviewing the activities of the DRI Team’s previous sprint including any active or on-going issues.
* Chores list.
 
=== Both ===
* Automation!
** Especially the chore work.
* Documentation!
** If you answer a question/resolved an issue that wasn’t already documented, document it!
** “Wiki gnome / wiki gardening” activities appreciated.
* Log DRI Team activities on the tracking task.
 
== References ==
* [https://devblogs.microsoft.com/oldnewthing/20150825-00/?p=91741 Microspeak: DRI, the designated response individual]

Latest revision as of 20:44, 2 August 2022