Domain expertise is broader than CF

domain-expertise.md

@@ -1,8 +1,8 @@
 <!--- This file was GENERATED.  Do not edit it directly.  Instead, edit the corresponding YAML file --->
-## CF Domain Expertise
+## Domain Expertise
 
 
-You understand the CF Products: How they work together, how they work with the larger ecosystem of non-CF Products. You can navigate the CF system and its engineering teams on a broad level, and know which areas to consider in problem-solving.
+You understand our Products (e.g. PAS, PKS): How they work together, how they work with the broader ecosystem. You can navigate this system and its engineering teams on a broad level, and know which areas to consider in problem-solving.
 
 One example of success in this area: You are trying to decide how to implement a database migration in CCDB. You know that this change may affect CC’s communication with Diego, with Routing, and with Networking. You surface how you think the changes will affect those teams to your PM/Anchor and work to find a solution that would minimize the impact on those teams. Additionally, you loop those teams into the conversation, and ensure that the solution you are moving forward with works as desired for them.
 
@@ -20,7 +20,7 @@ One example of success in this area: You are trying to decide how to implement a
 <td valign="top"><ul>
   <li>Shows curiosity about the product their team is building (eg: how it helps customers, who are the downstream consumers, how to downstream consumers rely on it)</li>
 
-  <li>Shows curiosity about bigger picture (boxes and lines) of CF (eg: watched videos from Cloud Foundry Summit, reads materials relating to technical concepts when presented by colleagues)</li>
+  <li>Shows curiosity about bigger picture (boxes and lines) of our products (eg: watched videos from Cloud Foundry Summit, reads materials relating to technical concepts when presented by colleagues)</li>
 </ul></td>
 </tr>
 
@@ -33,7 +33,7 @@ One example of success in this area: You are trying to decide how to implement a
 
   <li>Relates stories in the backlog to downstream consumers it would affect</li>
 
-  <li>Diagnoses issues that involve interactions with multiple CF components</li>
+  <li>Diagnoses issues that involve interactions with multiple components</li>
 
   <li>Can explain boxes-and-lines version of their team's product</li>
 </ul></td>
@@ -48,7 +48,7 @@ One example of success in this area: You are trying to decide how to implement a
 
   <li>Provides context on their team for historical decisions, features in past releases, and their team's domain</li>
 
-  <li>Can explain boxes-and-lines version of CF and is able to provide a more detailed view on CF components</li>
+  <li>Can explain the boxes-and-lines version of our products (e.g. PAS, PKS) and is able to provide a more detailed view on all components directly or indirectly related to their team.</li>
 
   <li>Can ramp up a new PM on team domain, or fill in for their PM for short periods of time.</li>
 </ul></td>
@@ -57,22 +57,22 @@ One example of success in this area: You are trying to decide how to implement a
 <tr>
 <td><strong>P4</strong></td>
 <td valign="top"><ul>
-  <li>Has working knowledge of an area of CF (eg: the BOSH ecosystem, the Platform, Logging and Metrics)</li>
+  <li>Has working knowledge of an area of our products (eg: the BOSH ecosystem, the Platform, Logging and Metrics, PKS)</li>
 
   <li>Preemptively identifies dependencies/repercussions of an epic to all consumers within a domain area; can suggest changes to required components to resolve it</li>
 
-  <li>Teaches Pivots on their team about a particular CF domain area</li>
+  <li>Teaches Pivots on their team about a particular domain area</li>
 
   <li>Leverages their knowledge of related domain concepts to better the product</li>
 
-  <li>Can explain how a CF domain area has evolved over time (including familiarity with features in past releases)</li>
+  <li>Can explain how a domain area has evolved over time (including familiarity with features and product decisions in past releases)</li>
 </ul></td>
 </tr>
 
 <tr>
 <td><strong>P5</strong></td>
 <td valign="top"><ul>
-  <li>Takes measures to dissipate their CF domain knowledge with a goal of empowering their team</li>
+  <li>Takes measures to dissipate their domain knowledge with a goal of empowering their team</li>
 </ul></td>
 </tr>
 

support.md

@@ -1,7 +1,7 @@
 <!--- This file was GENERATED.  Do not edit it directly.  Instead, edit the corresponding YAML file --->
 ## Support
 
-Passion for supporting our customers on their PCF journey, and ability to approach support issues with a customer-focussed mindset. You are able to handle interrupt-driven and exploratory work (e.g. questions on slack, on-call escalations, participation in cross-team meetings.) You ask relevant questions about an issue, figuring out what a customer needs to move forward, and drive it to resolution. You can communicate what you know respectfully to different audiences. You can also share what you still don’t know, and help identify the steps to learn more. You can apply your acquired CF knowledge on the fly, and are able to explore creative solutions to help meet the customer midway.
+Passion for supporting our customers on their PCF journey, and ability to approach support issues with a customer-focussed mindset. You are able to handle interrupt-driven and exploratory work (e.g. questions on slack, on-call escalations, participation in cross-team meetings.) You ask relevant questions about an issue, figuring out what a customer needs to move forward, and drive it to resolution. You can communicate what you know respectfully to different audiences. You can also share what you still don’t know, and help identify the steps to learn more. You can apply your acquired knowledge on the fly, and are able to explore creative solutions to help meet the customer midway.
 
 One example of success in this area: Your PM notes that there is an open support ticket that the team should help with. You don’t have much context on the issue, but go into the Slack channel with an open mind. You ask good foundational questions, learning where assumptions have been made, and where evidence has been found. After speaking with the customer and with Pivotal Support, you realize that this is a known issue in an upstream product, and point support in the right direction. You explain how you got to this conclusion, and stay in the Slack channel until it’s clear that the issue has been resolved and the customer is satisfied with the outcome.
 

technical-execution.md

@@ -5,7 +5,7 @@ You can be depended upon to pick up a story from the backlog, do it well (quickl
 
 One example of success in this area: You are trusted to drive stories to completion, and answer on-call escalations. Your anchor can depend on you to pair/solo on any story in the backlog, and provide leadership on tracks that need extra guidance.
 
-Another example of success in this area: You join a team whose main responsibility is integrating assets from other teams, and deploying them to a long, running production environment. You have minimal experience with operating the CF platform at scale. You are able to learn the tribal knowledge on the team quickly, and are able to execute on stories in the backlog with little guidance. Soon after, other pairs rely on you to onboard new team members, approach you with questions relating to the domain, and to reliably drive to completion uncertain/risky/technically complex stories.
+Another example of success in this area: You join a team whose main responsibility is integrating assets from other teams, and deploying them to a long, running production environment. You have minimal experience with operating the platform at scale. You are able to learn the tribal knowledge on the team quickly, and are able to execute on stories in the backlog with little guidance. Soon after, other pairs rely on you to onboard new team members, approach you with questions relating to the domain, and to reliably drive to completion uncertain/risky/technically complex stories.
 
 ---
 
@@ -69,7 +69,7 @@ Another example of success in this area: You join a team whose main responsibili
 
   <li>Consistently follows up on tasks/communication from stories</li>
 
-  <li>Can ramp up quickly to become productive on most CF teams</li>
+  <li>Can ramp up quickly to become productive on most R&D teams</li>
 </ul></td>
 </tr>
 

yaml/areas.yaml

@@ -14,7 +14,7 @@ areas:
 
     Another example of success in this area: You join a team whose main responsibility is
     integrating assets from other teams, and deploying them to a long, running production
-    environment. You have minimal experience with operating the CF platform at scale. You are able
+    environment. You have minimal experience with operating the platform at scale. You are able
     to learn the tribal knowledge on the team quickly, and are able to execute on stories in the
     backlog with little guidance. Soon after, other pairs rely on you to onboard new team members,
     approach you with questions relating to the domain, and to reliably drive to completion
@@ -35,11 +35,11 @@ areas:
     your teammate's about the importance of integrating early and often. You are eventually able to
     get your team to a point where CI being red is no longer the norm.
 - id: domain-expertise
-  title: CF Domain Expertise
+  title: Domain Expertise
   description: >-
 
-    You understand the CF Products: How they work together, how they work with the larger ecosystem
-    of non-CF Products. You can navigate the CF system and its engineering teams on a broad level,
+    You understand our Products (e.g. PAS, PKS): How they work together, how they work with the broader ecosystem.
+    You can navigate this system and its engineering teams on a broad level,
     and know which areas to consider in problem-solving.
 
 
@@ -108,7 +108,7 @@ areas:
     ask relevant questions about an issue, figuring out what a customer needs to move forward, and
     drive it to resolution. You can communicate what you know respectfully to different audiences.
     You can also share what you still don’t know, and help identify the steps to learn more. You can
-    apply your acquired CF knowledge on the fly, and are able to explore creative solutions to help
+    apply your acquired knowledge on the fly, and are able to explore creative solutions to help
     meet the customer midway.
 
 

yaml/skills.yaml

@@ -82,7 +82,7 @@ skills:
   area: technical-execution
   level: p3
 - id: s18eaa3cb
-  description: Can ramp up quickly to become productive on most CF teams
+  description: Can ramp up quickly to become productive on most R&D teams
   area: technical-execution
   level: p3
 - id: s7ce63cd6
@@ -221,7 +221,7 @@ skills:
   level: p1
 - id: s523cd8bf
   description: >-
-    Shows curiosity about bigger picture (boxes and lines) of CF (eg: watched videos from Cloud
+    Shows curiosity about bigger picture (boxes and lines) of our products (eg: watched videos from Cloud
     Foundry Summit, reads materials relating to technical concepts when presented by colleagues)
   area: domain-expertise
   level: p1
@@ -238,7 +238,7 @@ skills:
   area: domain-expertise
   level: p2
 - id: scc522ffa
-  description: Diagnoses issues that involve interactions with multiple CF components
+  description: Diagnoses issues that involve interactions with multiple components
   area: domain-expertise
   level: p2
 - id: sf7158cd3
@@ -265,8 +265,8 @@ skills:
   level: p3
 - id: s4e20b350
   description: >-
-    Can explain boxes-and-lines version of CF and is able to provide a more detailed view on CF
-    components
+    Can explain the boxes-and-lines version of our products (e.g. PAS, PKS) and is able to provide a
+    more detailed view on all components directly or indirectly related to their team.
   area: domain-expertise
   level: p3
 - id: sc6072661
@@ -275,8 +275,8 @@ skills:
   level: p3
 - id: s1baf6c7c
   description: >-
-    Has working knowledge of an area of CF (eg: the BOSH ecosystem, the Platform, Logging and
-    Metrics)
+    Has working knowledge of an area of our products (eg: the BOSH ecosystem, the Platform, Logging and
+    Metrics, PKS)
   area: domain-expertise
   level: p4
 - id: s2e251366
@@ -286,7 +286,7 @@ skills:
   area: domain-expertise
   level: p4
 - id: s46177acd
-  description: Teaches Pivots on their team about a particular CF domain area
+  description: Teaches Pivots on their team about a particular domain area
   area: domain-expertise
   level: p4
 - id: s51c43be9
@@ -295,12 +295,12 @@ skills:
   level: p4
 - id: s66f23c3e
   description: >-
-    Can explain how a CF domain area has evolved over time (including familiarity with features in
+    Can explain how a domain area has evolved over time (including familiarity with features and product decisions in
     past releases)
   area: domain-expertise
   level: p4
 - id: sa467f450
-  description: Takes measures to dissipate their CF domain knowledge with a goal of empowering their team
+  description: Takes measures to dissipate their domain knowledge with a goal of empowering their team
   area: domain-expertise
   level: p5
 - id: s8d1ab0e6