Building a complete software cycle can seem overwhelming for a software engineer, which is why many companies divide these responsibilities into specialized roles: SDEs for writing code, QA for testing, DevOps for deploying to production, and SREs for monitoring, metrics, and alerting. However, this division often results in reduced ownership over customer issues, with software engineers attributing problems to QA for inadequate testing, or to SREs for insufficient monitoring and metrics. The lack of a single owner for the entire process can be detrimental.
Although it may seem daunting for SDEs to manage the entire workflow and acquire the necessary expertise, we can address this challenges by setting up basic building blocks.
What are the basic building blocks for empowering teams
1
Create Culture: Foster a culture of comprehensive ownership and automation.
2
Infrastructure Setup: Establish repeatable methods for rapid infrastructure setup along with golden paths.
3
Code Deployment: Out of the box tools to automate code deployment to eliminate manual tasks , Reduce blast radius and improve deployment safety.
4
Monitor Customer Impact: Allow teams to focus on metrics without worrying about setup aspects, Operational Release and Readiness checklist to allow any team to monitor and scale new services they build or maintain existing service.
5
Establishing Feedback Loop: Releasing any product it’s difficult to eliminate risks but we can reduce customer impact, We need a blame- less culture that can do post mortem on issues and feed into building blocks 1,2,3 and 4.
One response to “Building Blocks for Empowering Teams”
Hi, this is a comment.
To get started with moderating, editing, and deleting comments, please visit the Comments screen in the dashboard.
Commenter avatars come from Gravatar.