Current Owners¶
| What | The mapping of current people to the roles used throughout the SOPs. |
| How to use | Keep this table up to date. The process pages reference roles only, so updating people here never requires editing an SOP. |
The SOPs never name individuals (see hard constraint in the playbook): they reference roles such as Development Lead or Support Person. This page is the one editable place that maps those roles to the people currently holding them, so the rest of the playbook stays generic and reusable.
Placeholder, to be filled in
The names below are placeholders. Replace them with the current holders, and add or remove rows as the team changes. The owner may also choose to keep this mapping outside the site entirely (for example in an HR system); if so, link to it here instead of maintaining the table inline.
| Role | Current holder | Backup | Notes |
|---|---|---|---|
| Product Owner | TBD | TBD | |
| Project Manager | TBD | TBD | |
| Development Lead | TBD | TBD | Primary technical contact for Support escalations. |
| Backup Development Lead | TBD | Covers the Development Lead's absence. | |
| QA Lead | TBD | TBD | |
| DevOps / Platform Engineer | TBD | TBD | One owner per platform for monitoring. |
| Support Lead | TBD | TBD | |
| Support Person | TBD | First point of client contact. | |
| Manager | TBD | TBD | Daily dashboard review and SOP oversight. |
| Leadership | TBD | Owns escaped-defect allowances and review cadence. |
Related¶
- Roles and Responsibilities: what each of these roles does across the SOPs.
- Production Support: where the Development Lead, Backup Lead, and Support roles are used most directly.