TLDR: Start implementing SCORP™ Process Cycle in your team today – don’t overthink it! Build it into your routine, forming an atomic habit.
This tool is here to help.
Your Internal Guide to SCORP™: Use this guide as your “how-to” for getting SCORP™ up and running with your team. Simply copy and paste this content, make any necessary edits, and refer to the template below to create your dashboard. Good luck, and let us know how it goes!
Overview of SCORP™ Process Cycle
SCORP™ combines Continuous Improvement practices with the Well-Architected Framework, creating a process to elevate team confidence and drive engineering excellence. It represents an acronym for Security, Cost, Operational Excellence, Reliability, and Performance – the five foundational pillars in frameworks used by leading Cloud Service Providers.
These pillars are essential to our journey toward engineering excellence, enabling us to assess our current status against these critical areas and steer ourselves towards continuous improvement.
Each report should evolve based on your team’s specific topology and the type of team you identify with. Refer to Team Topologies for insights.
Tip: Avoid automating dashboards too early. Initially, a manually updated dashboard can deepen your understanding of the data before you proceed to automation.
Note: SCORP™ is not intended for comparing teams.
Dashboard Template
Use the following as a framework for setting up your SCORP™ dashboard:
- Metrics Table: Start with a basic table to track metrics across Security, Cost, Operational Excellence, Reliability, and Performance.
- Frequency: Set a cadence for reviewing and updating metrics.
- Actions: Record action items and follow up.
Participating Teams
List your teams here:
- Team name
- Engineering lead
- Management lead
- Link to dashboard page
Team Working Agreements
- All team members’ views are respected, and everyone’s voice is valued.
- Everyone is encouraged to contribute comfortably and authentically.
- We strive to be punctual.
- We respect the unique qualities of each team.
- We celebrate small wins and support each other.
- Negative feedback is balanced with positive reinforcement to maintain a constructive atmosphere.
- Communication will continue beyond review meetings through regular team channels.
- Regular meetings occur every two weeks, even if the usual facilitator is unavailable.
SCORP™ Check-In Meeting Details
- Frequency: Every two weeks on [day]
- Facilitator: Team Architect or Staff Engineer
- Attendees: Tech leads, team members, etc.
- Focus: Primarily a dialogue between Architects and Tech Leads
- Duration: 60 minutes
FAQ
What is SCORP™?
SCORP™ is an open conversation between technical leaders, driven by tangible metrics to pinpoint improvement areas. It often highlights potential issues early on.
What does management expect from this?
Nothing! SCORP™ is “by the team, for the team.” The goal is to determine what the team wants to improve – be it performance, security, or another pillar – and then work on that improvement.
Can we create an automated dashboard?
Yes, but flexibility is crucial at first. Keep the dashboard as a simple table until you’re sure of the metrics you want. It may take six months to establish.
What if a metric is time-consuming to collect?
Consider if it’s truly valuable. If so, then automating it may be worthwhile. If not, discontinue it.
As an Engineering Manager, I’m concerned my team is too busy for this. Can we skip it?
Sometimes, but it’s best to keep SCORP™ consistent. It can occur asynchronously, but the quality of conversation is key.
Will senior leadership view the dashboard?
Possibly, though SCORP™ is primarily for the team. Leaders might check in, but the process is designed for engineers and architects, with management’s support.
How often should pages be updated?
Aim for at least once per sprint.
How can I get leadership buy-in?
Start with a focused 30-minute discussion on a single SCORP™ pillar (e.g., Cost, Performance). Keep dashboards simple, record actions, and update leadership after several sessions. Slow, steady progress builds credibility.
Need help facilitating?
Slow down and ask open questions. Avoid competition and don’t compare teams. Create a collaborative, polite, and open environment.
For more details, refer to SCORP™ on GitHub.
Best of luck, and let us know how your journey with SCORP™ unfolds in the comments below!