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.
| Level | Skills |
| P1 |
- 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)
- 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)
|
| P2 |
- Has working knowledge about the product their team is building.
- Has working knowledge about how other teams/downstream consumers/customers use their product
- Relates stories in the backlog to downstream consumers it would affect
- Diagnoses issues that involve interactions with multiple components
- Can explain boxes-and-lines version of their team's product
|
| P3 |
- Has sound knowledge of the team's product(s) and its downstream consumers, and can be counted upon to represent the team's interests.
- Preemtively identifies dependencies/repercussions of features on downstream consumers and past releases
- Provides context on their team for historical decisions, features in past releases, and their team's domain
- 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.
- Can ramp up a new PM on team domain, or fill in for their PM for short periods of time.
|
| P4 |
- Has working knowledge of an area of our products (eg: the BOSH ecosystem, the Platform, Logging and Metrics, PKS)
- Preemptively identifies dependencies/repercussions of an epic to all consumers within a domain area; can suggest changes to required components to resolve it
- Teaches Pivots on their team about a particular domain area
- Leverages their knowledge of related domain concepts to better the product
- Can explain how a domain area has evolved over time (including familiarity with features and product decisions in past releases)
|
| P5 |
- Takes measures to dissipate their domain knowledge with a goal of empowering their team
|