Sample RACI Matrix for Release Planning

I love a RACI matrix.

Such a simple tool to define who is doing which task in a process. It’s not only an incredibly useful communication tool, but also a way to spot gaps in capability, authority and process steps.

There is no one-size-fits-all for a RACI matrix - not the tasks nor who is assigned to each level. It entirely depends on how you want to release, and who you have in your organisation, both roles and individual people and skills.

Below is my sample of one for a software release planning process citing, what I think, are the foundational key steps. Some additional ones for a more established process may also be:

  • T-shirt sizing

  • Create release documentation & release comms for users

  • Create release documentation & release comms for internal staff

  • Update product documentation (user journeys, user stories, UI/UX design spec, product vision document etc.)

  • Update technical documentation (system architecture docs, API docs, knowledge base articles etc.)

  • Update user documentation (wiki help articles, manuals, installation guides, FAQs etc.)

  • Update regression testing pack

  • Update release roadmap plan

  • Create or update training materials

Task/Activity Responsible Accountable Consulted Informed
MoSCoW analysis, prep potential scope of the release Helpdesk Manager Head of Business Development Customer Stakeholders, Development Team, QA/BA Specialist, Design Lead Project Manager
Gather Requirements on tickets, create acceptance criteria BA/QA Specialist Head of Business Development Customer Stakeholders, Development Team Project Manager
Technical Resource Allocation Development Team Lead Development Team Lead Development Team Project Manager
Release plan Project Manager Project Manager Development Team Lead, Development Team, QA/BA Specialist, Design Lead Head of Business Development, Helpdesk Manager
Progress review & oversight Project Manager Project Manager Development Team Lead, Development Team, QA/BA Specialist, Design Lead Head of Business Development, Helpdesk Manager
Risk Management Project Manager Project Manager Development Team Lead, Development Team, QA/BA Specialist, Design Lead Head of Business Development, Helpdesk Manager
Development Development Team Development Team Lead QA/BA Specialist Helpdesk Manager
System testing Development Team Development Team Lead QA/BA Specialist Helpdesk Manager
Internal QA Testing BA/QA Specialist Project Manager Development Team Lead, Development Team Helpdesk Manager
E2E regression testing BA/QA Specialist Project Manager Development Team Lead, Development Team Helpdesk Manager
Release Readiness Review Project Manager Project Manager Development Team, QA/BA Specialist Head of Business Development, Helpdesk Manager
Deployment Development Team Development Team Lead BA/QA Specialist, Head of Business Development Customer stakeholders
 
Previous
Previous

Some rules of engagement for Release Planning

Next
Next

Do not cancel your project team meetings