Production Readiness Review
Last updated
Was this helpful?
Last updated
Was this helpful?
The production readiness review (PRR) is a process that identifies the reliability needs of a service, feature (mid to large only) or a significant change to infrastructure. The Mattermost PRR has been inspired from the from the SRE book. A PRR is considered a prerequisite for the Infrastructure team to accept responsibility for managing the production aspects of a service, feature or infrastructure change.
The goals of the readiness review is to improve the followings:
System architecture and interservice dependencies
Observability (metrics, monitoring, logging)
Incident Response
Capacity planning
Change management
Performance, availability, latency and efficiency
Security posture
Increase awareness and boost collaboration with a goal to built a cloud-native product
This will help to increase the collaboration between Product, Security and Infrastructure teams in order to bridge any gaps about a new service, feature or infrastructure change. The review document is not intended to be constantly updated and it reflects a snapshot of the reality of what is being deployed and the discussions around it.
The PRR process is initiated by the DRI of the related work with the following steps:
Run the Mattermost PRR Playbook
The title of the Playbook run should be self-descriptive for the change.
Include the relevant reviewers in the PRR Mattermost channel
Use the checklist in Playbook which will guide you through to complete the review
Once all comments have been addressed and the reviewers are satisfied they could check off the task item in which they are owners. When all the set approvals are there, the playbook run needs to be closed.
SRE review is completed
Platform review is completed
etc.
This will automatically mark the task item list as done based on the current members of the engineering teams.
The PRR playbook uses , so when you are done with your review and you are ready to approve you can just write in the channel the following:
You can find the Infrastructure library