diff --git a/CNAME b/CNAME deleted file mode 100644 index 2dd9fd4..0000000 --- a/CNAME +++ /dev/null @@ -1 +0,0 @@ -response.spearhead.systems \ No newline at end of file diff --git a/before/different_roles/index.html b/before/different_roles/index.html index 607d61c..3f25ca2 100644 --- a/before/different_roles/index.html +++ b/before/different_roles/index.html @@ -281,14 +281,14 @@
There are several roles for our incident response teams at Spearhead Systems. Certain roles only have one person per incident (e.g. support engineer), whereas other roles can have multiple people (e.g.System/Solution Architects, juniors, etc.). It's all about coming together as a team, working the problem, and getting a solution quickly.
+There are several roles for our incident response teams at Spearhead Systems. Certain roles only have one person per incident (e.g. support engineer), whereas other roles can have multiple people (e.g. Sysadmins, Solution Architects, etc.). It's all about coming together as a team, working the problem, and getting a solution quickly.
Here is a rough outline of our role hierarchy, with each role discussed in more detail on the rest of this page.
A Team Leader acts as the single source of truth of what is currently happening and what is going to happen during an major incident. They come in all shapes, sizes, and colors. TL's are also the key elements in a project (boards in DoIT).
Take a look at our Team Leader training guide.
A Deputy is a direct support role for the Incident Commander. This is not a shadow where the person just observes, the Deputy is expected to perform important tasks during an incident.
+A Sysadmin is a direct support role for the Team Leader. This is not a shadow where the person just observes, the Sysadmin is expected to perform important tasks during an incident.
It's important for the IC to focus on the problem at hand, rather than worrying about documenting the steps or monitoring timers. The deputy helps to support the IC and keep them focussed on the incident.
+It's important for the TL to focus on the problem at hand, rather than worrying about documenting the steps or monitoring timers. The Sysadmin helps to support the TL and keep them stay focussed on the incident.
The Deputy is expected to:
+The Sysadmin is expected to:
Any Incident Commander can act as a deputy. Deputies need to be trained as an Incident Commander as they may be required to take over command.
+Any Team Leader can act as a Sysadmin. Sysadmins need to be trained as an Team Leader as they may be required to take over command.
Take a look at our Deputy training guide. Deputies also need to be trained as an Incident Commander.
+Take a look at our Sysadmin training guide. Sysadmins also need to be trained as an Team Leaders.
TODO:::move scribe responsibilities to TL and Sysadmin +::: or assign this to our juniors?
A Scribe documents the timeline of an incident as it progresses, and makes sure all important decisions and data are captured for later review.
@@ -547,12 +549,13 @@Anyone can act as a scribe during an incident, and are chosen by the Incident Commander at the start of the call. Typically the Deputy will act as the Scribe, but that doesn't necessarily need to happen, and for larger incidents may not be possible.
Follow our Scribe training guide, and then notify the Incident Commanders that you would like to be considered for scribing for the next incident.
+TODO::: END move scribe responsibilities to TL and Sysadmin
A Subject Matter Expert (SME), sometimes called a "Resolver", is a domain expert or designated owner of a component or service that is part of the PagerDuty software stack.
+A Subject Matter Expert (SME), sometimes called a "Resolver" or "Architect", is a domain expert or designated owner of a component or service that is part of the Spearhead Systems service delivery concept.
The IC and deputy are not all-knowing super beings. When there is a problem with a service, an expert in that service is needed to be able to quickly help identify and fix issues.
+The TL and Sysadmins are not all-knowing super beings. When there is a problem with a service or a particular system, an expert in that service is needed to be able to quickly help identify and fix issues.
All of the other roles will be actively working on identifying the cause and resolving the issue, we need a role which is focused purely on the customer interaction side of things so that it can be done properly, with the due care and attention it needs.
Any member of the Support Team can act as a customer liaison.
diff --git a/index.html b/index.html index 1072cfc..bcedaa2 100644 --- a/index.html +++ b/index.html @@ -517,6 +517,7 @@