OPS11-BP08 Document and share lessons learned
Document and share lessons learned from the operations activities so that you can use them internally and across teams. You should share what your teams learn to increase the benefit across your organization. Share information and resources to prevent avoidable errors and ease development efforts, and focus on delivery of desired features.
Use AWS Identity and Access Management (IAM) to define permissions that permit controlled access to the resources you wish to share within and across accounts.
Desired outcome:
-
You use version-controlled repositories to share application libraries, scripted procedures, procedure documentation, and other system documentation.
-
You share your infrastructure standards as version-controlled AWS CloudFormation templates.
-
You review lessons learned across teams.
Common anti-patterns:
-
You suffered an extended outage because your organization commonly uses buggy library. You have since migrated to a reliable library. The other teams in your organization do not know they are at risk. No one documents and shares the experience with this library, and they are not aware of the risk.
-
You have identified an edge case in an internally-shared microservice that causes sessions to drop. You have updated your calls to the service to avoid this edge case. The other teams in your organization do not know that they are at risk.
-
You have found a way to significantly reduce the CPU utilization requirements for one of your microservices. You do not know if any other teams could take advantage of this technique.
Benefits of establishing this best practice: Share lessons learned to support improvement and to maximize the benefits of experience.
Level of risk exposed if this best practice is not established: Low
Implementation guidance
-
Document and share lessons learned: Have procedures to document the lessons learned from the running of operations activities and retrospective analysis so that they can be used by other teams.
-
Share learnings: Have procedures to share lessons learned and associated artifacts across teams. For example, share updated procedures, guidance, governance, and best practices through an accessible wiki. Share scripts, code, and libraries through a common repository.
Resources
Related best practices:
Related documents:
Related videos:
