Adding more personas and roles to the project management processes

### Which process document do you want to update? (If this is a new document, select '')

octoacme-roles-and-personas.md

### Summary of New Content

Propose expanding the "Roles & Personas" process doc to include additional project roles and clearer responsibility mappings. The goal is to define new personas, their responsibilities, and how they interact with existing roles to improve clarity and accountability across projects.

### Why is this update needed?

Current documentation covers core roles (Developers, Product Managers, Project Managers) but several recurring responsibilities and handoffs are not explicitly assigned. This creates ambiguity during planning, execution, and incident response. Adding more personas (or clarifying sub-roles) will reduce single-point dependencies, speed decision-making, and make handoffs and escalation paths clearer.

This update is needed to:
- Reduce ambiguity in accountability for cross-functional tasks (e.g., observability, release coordination, security reviews).
- Capture specialized responsibilities that occur frequently but are not described (e.g., release management, data validation, UX research).
- Improve onboarding by giving new team members a clearer map of who to contact for specific concerns.

Target doc for this change: docs/octoacme-roles-and-personas.md

### Suggested Content (optional)

Suggested additions (each entry includes responsibilities and interactions with existing roles):

1) Delivery Lead
- Responsibilities: Owns sprint-level delivery, coordinates day-to-day blockers, ensures stories meet DoD, tracks dependencies across teams.
- Interactions: Works closely with PM (scheduling & priorities), Developers (removing blockers), QA (acceptance criteria), and Stakeholders (status updates).

2) Business Analyst (BA)
- Responsibilities: Refines requirements, writes detailed acceptance criteria, facilitates discovery and clarification with stakeholders.
- Interactions: Partners with Product Managers (requirements & prioritization), Developers (clarifications), QA (test scenarios), and UX.

3) UX Researcher / Designer
- Responsibilities: Drives user research, designs flows and prototypes, validates usability before implementation.
- Interactions: Collaborates with Product Managers (user outcomes), Developers (implementation feasibility), and Stakeholders (feedback loops).

4) Release Manager
- Responsibilities: Coordinates release windows, rollbacks, communication plans, ensures release checklist items complete (backups, runbooks, smoke tests).
- Interactions: Works with DevOps/Platform, PM/PD for scheduling, Support for post-release monitoring, and Security for deployment reviews.

5) Observability / SRE Engineer
- Responsibilities: Sets up monitoring and alerting, defines SLOs, supports incident response and postmortems.
- Interactions: Collaborates with Developers (instrumentation), PM (success metrics), and Support (incidents).

6) Security Liaison
- Responsibilities: Reviews security requirements, conducts threat reviews, ensures compliance checks are scheduled and completed.
- Interactions: Works with Developers (secure implementation), Release Manager (pre-release checks), and Product Manager (risk decisions).

7) Data Analyst / Data Steward
- Responsibilities: Validates data contracts, verifies analytics accuracy, provides metric definitions and dashboards.
- Interactions: Partners with PM (success metrics), Developers (data schema), and QA (data validation tests).

8) Support / Ops Lead
- Responsibilities: First-line triage for incidents, captures customer impact, provides runbooks and escalation details.
- Interactions: Works with SRE (incident escalation), Product/PM (customer impact), and Developers (bug fixes).

9) Change Manager (for larger releases)
- Responsibilities: Reviews change impact, coordinates stakeholder sign-offs, schedules communications for major changes.
- Interactions: Works with Release Manager, PM, and Stakeholders.

How this will improve outcomes:
- Clearer handoffs reduce delays and rework.
- Defined escalation and ownership lower MTTR in incidents.
- Better onboarding via explicit role expectations.
- More consistent delivery quality through specialized accountability.

Suggested next steps for the doc update:
- Add new persona entries to docs/octoacme-roles-and-personas.md with the above structure.
- Map each persona to existing roles and decision points (e.g., who approves release, who owns metrics).
- Review proposed additions with PM, Product Lead, Security, and SRE before merging.

### Acceptance Criteria

- [x] Content aligns with existing process docs
- [x] Update improves clarity or closes a documented gap
- [ ] Proposed content has been reviewed with stakeholders (if needed)