Scorecards are like lightweight Rubrics that are set by individual Teams and Groups. Unlike the organizational-wide Rubric, Scorecards do not impact the overall Maturity Level of a Service. Scorecards allow Teams and Groups to measure and track service health against their own unique goals separate from the organizational standards established in the main Rubric.
There are a few use-cases when it would make sense to use a Scorecard instead of the Rubric, including (but not limited to):
- Onboarding: Scorecards allow a quicker onramp to utilizing OpsLevel's powerful Service Maturity model from Day 0 without needing to have the org-wide Rubric established.
- Experimenting with new Rubric categories: There may be a situation in which you're interested in adding a new category to your rubric but would like to do some experimenting and fine tuning first. Scorecards allow you to perform this type of experimentation without having it impact overall Service Maturity Levels.
- Team Autonomy: Let's say there are some action items for an individual team that have come out of a retro or post-mortem (ex. "We want to increase the code coverage for the services that we own") that don't necessarily align with what's in the Rubric. Using Scorecards, teams will now have the ability to drive their own standards for the Services that they own.
To create a new Scorecard, navigate to Scorecards from Service Maturity in the side navigation.
If there are no active Scorecards within your OpsLevel account, you will see an empty state which will prompt you to create your first Scorecard.
You can create a new Scorecard by either clicking this prompt or by clicking the + New Scorecard button. Clicking this button will open a new Create New Scorecard page. From this page you will be able to fill out the following details:
- Name (required)
- Owner (required)
The filter selected for your scorecard will apply to all of the checks added to that scorecard. Scorecard checks also allow you to set filters, which are combined with this top-level filter using the
Example: If you select a scorecard filter that only applies to services owned by the “Order Management Team” and then select a filter on a check within that scorecard that only applies that check to “Ruby” services, the check will apply to the combination of “Ruby services owned by the Order Management Team”.
Note: Although Scorecards can be applied to Services that a user does not own, we suggest you use caution when doing this as to not disrupt other teams.
After creating your new Scorecard, you will be taken to the Scorecard Details page. This page will provide details around your Scorecard such as:
- Maturity Report for the Services impacted by your Scorecard
- Scorecard Rubric
Each Scorecard comes with its own scaled-down Rubric. Levels for Scorecards are set globally from the Settings page and are applied to both the Rubric and Scorecards. This ensures a consistent language across your organization as individual Scorecards cannot have their own unique levels.
To add a new check to your Scorecard, hover over your desired Level and click the + Add Check button.
Clicking this button will launch the same Create Check modal used for both campaigns and the rubric. After filling out the details of your check, select Create to add it to your Scorecard.
Individual Service Owners can see a breakdown of how they are performing against Scorecards by navigating to the Maturity Report tab for their Service. Each Scorecard that applies to an individual Services will now be present within the Service Maturity card below Rubric. Service Owners can filter the Maturity Report across any combination of Scorecards and Rubric Categories.
It is important to note that only the categories or scorecards with the Pie Graph icon highlighted in the image below affect your overall service level.
In addition to creating Scorecards via the UI, you can also create Scorecards using the:
All are options for configuring and maintaining your Scorecards. Below is an example of using the OpsLevel CLI to create a new Scorecard:
$ cat << EOF | opslevel create scorecard -f - name: "Production Readiness" description: "There are many like it, but this scorecard is mine." ownerId: "SOME_OWNER_ID" filterId: "SOME_FILTER_ID" EOF
Updated 21 days ago