Summary
DRI / Directly Responsible Individual
Apple coined the term “directly responsible individual” (DRI) to refer to the one person with whom the buck stopped on any given project. The idea is that every project is assigned an empowered DRI who is ultimately held accountable for the success (or failure) of that project.
https://www.quora.com/How-well-does-Apples-Directly-Responsible-Individual-DRI-model-work-in-practice
Issues, proposed changes, etc should be raised directly with the DRI; the DRI’s decision is final - however, the DRI must effectively communicate and document the reasons, goals, and subsequent lessons for any changes implemented.
PRINCIPLE: Every initiative will have a DRI
Sprint Sovereign
The Sprint Sovereign runs (i.e. is the DRI for) Tapas as well as Retro 👉 and Backlog👉 sessions.
PRINCIPLE: Sovereign rotates every 2 weeks throughout every member of the team. You’re encouraged to volunteer, otherwise a random name will be picked via Slackbot
Tandem
Amongst the many issues of working in a fully distributed team 👉 the biggest shock was the loss of serendipitous, casual conversation. After iterating through various methods to address this (more regular Zoom calls, scheduled frequent catchups, all day calls, etc) it became clear that this is primarily a [[workflow & tooling]] problem, not an [[attitude, cultural, or management]] issue. To that end we added Tandem to our toolkit; through considered UI and frictionless usability, this enables a quicker and more informal way to see what colleagues are doing and jump into voice rooms with them.
🚀 Purely through using this tool - the right tool - we’ve increased collaboration, efficiency, wellbeing, and standard of work
🚀 We also still use Zoom, Teams, Slack, etc - the right tool depends on the task at hand. It is incorrect to view e.g. Tandem as a replacement for Teams, even if superficially they seem similar.
DRI: os
Changelog
Changes to ways-of-working (standup, retro, backlog, toolkit, etc) are documented in a changelog 👉.
This creates a traceable flow of logic that explains are current working cadence, ensuring we don’t end up repeating things over time.
DRI: os
Task-tracking, team-tracking, Jira, and Asana
We currently use Jira Cloud for both task-tracking and management-information. We’ve previously tried:
- Asana (lacked MI)
- Jira (not ‘helpful’)
DRI - BS ER
RescueTime & Slack integration
- Sign in here https://www.rescuetime.com/integrations/slack
- Once signed-in, on the top-right choose SETTINGS, and choose API & INTEGRATIONS from the pop-up menu
- Choose SLACK (Learn More)
- Scroll down, turn it OFF and ON again
- Scroll down, choose which categories of apps your Slack Status should be updated for
- Choose SAVE
- Wait about 15 mins for it to activate