Section 11
Product Development Roles & Responsibilities: RACI Matrix Reference
Product Development Roles & Responsibilities: RACI Matrix Reference
Quick Reference for Who Does What
Understanding RACI
-
R (Responsible) : Does the work
-
A (Accountable) : Final authority, delegate decision
-
C (Consulted) : Provides input before decision
-
I (Informed) : Kept updated after decision
Key Rule: Each activity should have ONE person Accountable, but multiple can be Responsible.
Phase 0: Discovery
| Phase 0: Discovery | |||||
|---|---|---|---|---|---|
| Activity | P<br>M | Sponsor | Tech Lead | Analyst | Designer |
| Customer interviews | R | C | - | R | - |
| Market research | R | A | I | R | - |
| Problem statement | R | A | C | C | - |
| Competitive analysis | C | - | - | R | I |
| Business case | R | A | C | I | - |
| Executive approval | C | A | - | - | - |
Phase 1: Initiation
| Phase 1: Initaton | |||||
|---|---|---|---|---|---|
| <br>Activity | P<br>M | Sponsor | Tech Lead | Dev Lead | Scrum Master |
| Project charter | R | A | C | I | I |
| Stakeholder identification | R | C | - | - | I |
| Team assignment | R | A | C | C | I |
| Kickoff meeting | R | A | - | I | C |
| Slack/Git setup | C | - | R | C | - |
| Communicationplan | R | A | - | I | C |
Phase 2: Planning
| Phase 2: Planning | ||||||
|---|---|---|---|---|---|---|
| Activity | P<br>M | BA | Tech Lead | Dev Lead | QA Lead | Designer |
| MRD | R | C | - | - | - | I |
| PRD | R | C | C | C | I | C |
| User storycreation | R | R | C | C | I | C |
| RTG (Living Traceability Graph) | R | C | C | C | I | C |
| Product roadmap | R | C | I | I | - | - |
| Resourceplanning | R | - | C | A | C | - |
| Cost estimation | R | C | C | - | - | - |
| Risk register | R | A | C | I | I | - |
| Tech stack decision | C | - | R | A | C | I |
| Timeline creation | R | - | C | A | - | - |
Phase 3: Design
| Activity | Desi<br>gner | PM | Tech Lead | Backend Lead | Frontend<br>Lead | QA |
|---|---|---|---|---|---|---|
| Design system | R | A | - | - | I | I |
| UI/UX<br>mockups | R | A | C | - | C | C |
| Prototypes | R | A | - | - | I | - |
| System<br>architecture | - | C | R | A | I | I |
| HLD (High-<br>Level Design) | - | - | R | A | I | - |
| LLD (Low-Level<br>Design) | - | - | C | R | C | I |
| Database design | - | - | C | R | - | - |
| API<br>specification | - | C | C | R | A | I |
| Security<br>architecture | I | C | R | A | I | C |
| Design review | A | R | C | - | C | - |
| Approval sign-<br>off | A | R | A | - | - | - |
Phase 4: Development
| Activity | Dev<br>Lead | Back<br>end<br>Devs | Frontend<br>Devs | DevOps | PM | QA |
|---|---|---|---|---|---|---|
| Sprintplanning | R | C | C | - | A | - |
| Backlog<br>refinement | - | C | C | - | A | C |
| Code<br>development | - | R | R | - | - | I |
| Code review | A | R | R | - | - | - |
| Unit testing | - | R | R | - | - | I |
| CI/CD setup | - | - | - | R | I | - |
| Build & artifact<br>creation | - | - | - | R | - | - |
| Integration<br>testing | C | R | C | C | - | A |
| Staging<br>deployment | - | - | - | R | I | I |
| Performance<br>tuning | C | R | C | C | - | - |
| Documentation | - | R | R | C | - | - |
Phase 5: Testing
| <br>Activity | QA Lead | QA Engineers | Dev Lead | P<br>M | Security |
|---|---|---|---|---|---|
| Testplanning | R | A | C | I | C |
| Test scenario design | - | R | C | I | C |
| Test case creation | - | R | C | - | - |
| Test environment setup | C | - | - | - | R |
| Functional testing | A | R | C | - | - |
| Automated testing | - | R | A | - | - |
| Performance testing | R | A | - | I | - |
| Securitytesting | A | R | - | - | R |
| Bugtracking& triage | R | R | A | - | - |
| Defect resolution | A | - | R | - | - |
| UAT coordination | C | - | - | A | - |
| UAT execution | A | - | - | - | - |
| UAT sign-off | I | - | - | A | I |
| Activity | QA Lead | QA Engineers | Dev Lead | P<br>M | Security |
|---|---|---|---|---|---|
| Qualitysign-off | R | C | A | - | - |
Phase 6: Deployment
| Activity | DevOps | Tech Lead | P<br>M | QA | Sponsor |
|---|---|---|---|---|---|
| Releaseplanning | C | R | A | C | I |
| Release notes | - | - | R | C | - |
| Deploymentprocedure | R | A | I | I | - |
| Rollbackprocedure | R | A | I | - | - |
| Production setup | R | C | - | - | - |
| Pre-deployment checklist | A | R | A | A | - |
| Code freeze approval | - | R | A | - | C |
| Smoke test creation | - | A | - | R | - |
| Deploytoproduction | R | C | I | - | - |
| Smoke test execution | A | - | - | R | - |
| Monitoringsetup | R | C | - | - | - |
| Post-deployment monitoring | R | C | I | A | - |
| Go/No-Go decision | - | R | A | A | A |
| Customer communications | - | - | R | - | A |
Phase 7: Operations
| Activity | DevOps | Backend Lead | P<br>M | Support | On-Call |
|---|---|---|---|---|---|
| Real-time monitoring | R | C | I | - | C |
| Alert configuration | R | C | I | - | - |
| On-call rotation setup | A | - | R | I | - |
| Incident response | A | R | I | - | A |
| Root cause analysis | A | R | I | - | - |
| Support ticket handling | - | C | - | R | - |
| SLA tracking | A | - | R | A | - |
| Performance optimization | C | R | A | - | - |
| System monitoring | R | C | - | I | A |
| Status reporting | - | C | R | - | - |
| Activity | DevOps | Backend Lead | P<br>M | Support | On-Call |
|---|---|---|---|---|---|
| Backup& recovery | R | C | I | - | - |
| Database maintenance | R | A | - | - | - |
Phase 8: Closure
| Phase 8: Closure | |||||
|---|---|---|---|---|---|
| Activity | P<br>M | Tech Lead | Dev Lead | Sponsor | Admin |
| Retrospectiveplanning | R | A | - | - | - |
| Retrospective facilitation | R | - | - | - | - |
| Lessons learned documentation | R | A | C | - | - |
| Finalproject report | R | C | - | - | - |
| Budget reconciliation | A | - | - | R | - |
| Team recognition | R | - | - | A | - |
| Knowledge transfer | - | R | R | - | I |
| Operations handoff | C | R | - | - | A |
| Documentation archive | A | - | - | - | R |
| Project closure approval | A | R | - | A | - |