Adding areas of contribution.

alignment.md

@@ -0,0 +1,46 @@
+## Alignment and Adaptibility
+You take on the most important challenge with an open mind; to what degree are you willing and capable to take on the challenge that the organization would find the most impactful, even if it's not your first choice. You actively consider how you can best help the organization, and work with leadership to align your strengths and goals with important challenges. You improve leadership's visibility into difficult problems while engaging positively in solving them.
+
+Example of success in this area: You would like to work on <project 1> next, to improve your technical execution skill. Leadership would like you to rotate to <project 2>, which is under-allocated and needs your experience and guidance. You have already been on this team before, and would probably not choose to take on this challenge of your own volition. However, you agree to the change in plans, approach <project 2> with positivity, find ways to grow your skills in other areas while you are there, and are able to address the challenges on the team.
+
+---
+### Proposed Levels and Skills
+<table>
+<tbody>
+<thead>
+<td><strong>P1</strong></td>
+<td><strong>P2</strong></td>
+<td><strong>P3</strong></td>
+<td><strong>P4</strong></td>
+</thead>
+<tr>
+
+<!-- P1 -->
+<td valign="top"><ul>
+  <li>Volunteers for and is curious about stories/chores in the backlog that are important but less interesting</li></ul>
+</td>
+
+<!-- P2 -->
+<td valign="top"><ul>
+  <li>Volunteers for tedious/unglamorous but necessary tasks, such as chores/stories/action items/support tickets/open GitHub issues, and drives them to completion.</li>
+  <li>Responds to allocations changes by striving to understand the new team’s needs and context in the organization.</li>
+  <li>Contributes to previous decisions on a story, without disregarding previous work</li>
+  <li>When asked, gives feedback to team leadership about less-than-ideal team experiences.</li></ul>
+</td>
+
+<!-- P3 -->
+<td valign="top"><ul>
+  <li>When presented with a less-desired but important project, can adapt their skills and make a positive impact on the team.</li>
+  <li>Contributes positively to team decisions/artifacts that they would have done differently</li>
+  <li>Actively surfaces less-than-ideal team experiences (e.g. tension during inception, fears surrounding upcoming release) to team leadership and can be coached to resolve them.</li>
+  <li>Can identify useful context to assess team health.</li></ul> 
+</td>
+
+<!-- P4 -->
+<td valign="top"><ul>
+  <li>Frames less-interesting but high-priority work to highlight the value and learning-opportunity, improving the entire team’s outlook on that work.</li>
+  <li>Engages deeply with difficult, less-glamorous challenges and transforms them to be more desirable and actionable.</li>
+  <li>Is aligned with the priorities of the organization, and approaches their team allocation as a collaborative effort with leadership.</li>
+  <li>Adapts their personal growth and contributions to the organization's needs.</li>
+  <li>Makes sustainable progress towards current goals by continuously building on legacy codebases</li>
+  <li>Surfaces uncomfortable issues affecting the team in a kind, honest, and direct manner; keeps leadership in the loop while working to resolve the issues.</li></ul></td>  </tbody></table>   

cf-domain-expertise.md

@@ -0,0 +1,48 @@
+## Cloud Foundry 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.
+
+*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.
+
+---
+### Proposed Levels and Skills
+
+<table>
+<tbody>
+<thead>
+<td><strong>P1</strong></td>
+<td><strong>P2</strong></td>
+<td><strong>P3</strong></td>
+<td><strong>P4</strong></td>
+<td><strong>P5</strong></td>
+</thead>
+<tr>
+<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></ul>
+</td><td valign="top">
+<ul>
+  <li>Has working knowledge about the product their team is building.</li>
+  <li>Is learning about how other teams/downstream consumers/customers use their product</li>
+  <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>Can explain boxes-and-lines version of their team's product</li></ul>
+</td><td valign="top">
+<ul>
+  <li>Has sound knowledge of the team's product(s) and its downstream consumers, and can be counted upon to represent the team's interests.</li>
+  <li>Preemtively identifies dependencies/repercussions of features on downstream consumers and past releases</li>
+  <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 ramp up a new PM on team domain, or fill in for their PM for short periods of time.</li></ul> 
+</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>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>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></ul>
+</td><td valign="top">
+<ul>
+  <li>Takes measures to dissipate their CF domain knowledge with a goal of empowering their team</li></ul>
+</td>
+</tbody></table>   

collaboration.md

@@ -0,0 +1,61 @@
+## Collaboration
+You communicate clearly, proactively, and kindly. You initiate the communication in challenging situations. You behave in a way that ensures safety, inclusion, and recognition of fellow pivots. Your behavior leaves space for others to speak, and to disagree with your views. You contribute positively to our culture.
+
+*One example of success in this area*: One of your teammates has a frequent habit of interrupting others in meetings, especially when they’re excited about an idea. You find them after a meeting, and directly but kindly deliver this feedback. They don’t know what you’re talking about. You ask if it would be okay to stop them next time this happens. They agree. In the future, the team feels comfortable with giving feedback about interrupting in meetings in the moment.
+
+---
+### Proposed Levels and Skills
+
+<table>
+<tbody>
+<thead>
+<td><strong>P1</strong></td>
+<td><strong>P2</strong></td>
+<td><strong>P3</strong></td>
+<td><strong>P4</strong></td>
+<td><strong>P5</strong></td>
+</thead>
+<tr>
+
+<!-- P1 -->
+<td valign="top"><ul>
+  <li>Communicates clearly and kindly with team mates</li>
+  <li>Actively leaves space for others to share their ideas</li>
+  <li>Is conscious and respectful of team's agreements (eg: core working hours)</li>
+  <li>Communicates with the intent to learn, and creates a safe space for others to disagree</li>
+  <li>Pairs easily/successfully with most Pivots and/or teams</li></ul>
+</td>
+
+<!-- P2 -->
+<td valign="top"><ul>
+  <li>Actively works to build a more inclusive team.</li>
+  <li>Takes responsibility for their mistakes and/or misunderstandings, and can then focus on future improvements at the personal or team level.</li>
+  <li>Asks questions with humility, adding context about their existing knowledge or uncertainty.</li>
+  <li>Is self-aware and seeks feedback from their pair in the moment to ensure they are aligned</li>
+  <li>Initiates cross team communication when necessary</li>
+  <li>
+</ul></td>
+
+<!-- P3 -->
+<td valign="top"><ul>
+  <li>Sets an example for clear and kind communication in a disagreement.</li>
+  <li>Openly reflects on the impact of their own behaviour and makes improvements.</li>
+  <li>Recognizes and gives T.A.S.K feedback about exclusionary behaviour</li>
+  <li>Tailors their communication style to collaborate well with a variety of personalities.</li>
+  <li>Fosters a healthy learning environment, by teaching and modeling a blameless culture. e.g. Facilitates growth-oriented discussion following a mistake or fire, encourages teammates to share their own growth goals</li>
+  <li>Brings teams together by promoting cross team collaboration (including orchestrating logistics, facilitating group meetings)</li>
+</ul></td>
+
+<!-- P4 -->
+<td valign="top"><ul>
+  <li>Strongly facilitates decision-making where there are several conflicting viewpoints</li>
+  <li>Knows their blind spots and actively works towards managing them</li>
+  <li>Skillfully speaks up to address exclusionary behaviour in the moment</li>
+  <li>Coaches Pivots to recognize areas which could be benefitted by cross team collaboration</li>
+  </ul></td>
+
+<!-- P5 -->
+<td valign="top"><ul>
+  <li>Is a source of guidance across Pivotal in areas of productively managing personal conflict and/or contention</li>
+  </ul></td>
+</tbody></table>    

engineering-process.md

@@ -0,0 +1,50 @@
+## Engineering Process
+You understand the importance of maintaining feedback loops on an engineering team. You can expand on the philosophy behind our engineering process. You can innovate on our existing process to tailor practices to your team's needs. 
+
+*One example of success in this area*: Your team is not very disciplined about build failures in CI. You start a conversation with your team to understand what could make CI more useful and share the pain you observe when CI is red. After discussing it, you make a chore to refactor your concourse pipeline, in order to get more actionable signals from each portion of the pipeline. Over time you use these signals to incrementally improve your CI pipeline and educate 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.
+
+---
+### Proposed Levels and Skills
+
+<table>
+<tbody>
+<thead>
+<td><strong>P1</strong></td>
+<td><strong>P2</strong></td>
+<td><strong>P3</strong></td>
+<td><strong>P4</strong></td>
+<td><strong>P5</strong></td>
+
+</thead>
+<tr>
+<td valign="top">
+<ul>
+  <li>Follows along with existing engineering process on teams (eg: TDD, pairing, CI and Tracker discipline, etc.)</li>
+</td><td valign="top">
+<ul>
+  <li>Understands and explains the importance of improving feedback loops</li>
+  <li>Makes small tweaks to engineering process on their team, in response to retro items or team discussion.</li>
+  <li>Can onboard new team members on existing processes</li>
+  <li>Understands and explains why balanced teams and balanced decision-making is important</li>
+  <li>Can explain parts of our engineering process in terms of improving feedback loops</li>
+  <li>Shows discipline in upholding the team's engineering process</li>
+  <li>Provides feedback to teammates.</li></ul>
+</td><td valign="top">
+<ul>
+  <li>Understands and explains the XP/Agile principles behind specific practices of team's engineering process</li>
+  <li>Identifies problems on teams that can be fixed by changing engineering process</li>
+  <li>Advocates for a balanced team, and facilitates balanced decision-making</li>
+  <li>Actively works to improve engineering process and feedback loops on teams</li>
+  <li>Provides T.A.S.K feedback to teammates, that helps teammates grow</li></ul> 
+</td><td valign="top">
+<ul>
+  <li>Provides challenging feedback (kindly) and coaches teammates to change their behaviour</li>
+  <li>Teaches our engineering process to new Pivots and relates it back to XP/Agile principles</li>
+  <li>Recommends and proliferates team-wide changes to engineering process, to fix team pain-points.</li>
+  <li>Adapts to different flavors of process and ties it back to XP/Agile principles</li>
+  <li>Is an exemplary role-model for practicing and facilitating balanced decision-making</li>
+  <li>Continually works to evolve the engineering process on their teams</li></ul>
+</td><td valign="top">
+<ul>
+  <li>Innovates on engineering process and evangelizes that change across the org. Follows through by helping relevant and interested teams adopt it successfully</li></ul>
+</td>  </tbody></table>   

flow.md

@@ -0,0 +1,49 @@
+## Flow
+You understand how software makes it from an engineering team to the customer, from start to finish. You can evaluate and explain the "flow" of work through this system, and identify bottlenecks. You can help your team prioritize these bottlenecks, optimizing for a positive impact on downstream consumers or for customers. You use your flow knowledge to advise teams surrounding yours, and to avoid blocking their work.
+
+*One example of success in this area*: An investigation in your backlog has been blocked for days. Your teammates have made a valiant effort, but no one has found a way forward. You find a way to implement the feature without needing the blocking dependency. You outline a plan for integrating the dependency once it’s ready, and talk to the upstream team to finalize it.
+
+---
+### Proposed Levels and Skills
+<table>
+<tbody>
+<thead>
+<td><strong>P1</strong></td>
+<td><strong>P2</strong></td>
+<td><strong>P3</strong></td>
+<td><strong>P4</strong></td>
+</thead>
+<tr>
+<td valign="top"><ul>
+  <li>Is learning about how their team's artifacts flow to the customer (eg: release process, CI pipelines, dependencies)</li>
+</ul></td>
+
+  <td valign="top">
+<ul><li>Recognizes symptoms of reduced flow on their team (eg: persistently red CI, flaky tests, manual release process)</li>
+  <li>Cognizant of blockers (eg: blocked stories, CI, releases) and work with the team to unblock them</li>
+  <li>Resolves flow-related pain using modifications to existing process or tools</li>
+  </ul></td>
+
+  <td valign="top"><ul>
+  <li>Recognizes when and why team has reduced flow; surfaces the feedback to team leadership and at team retros</li>
+  <li>Frames symptoms of reduced flow in terms of customer impact</li>
+  <li>Can smoothly integrate upstream depedencies into team's work with little impact to team's rate of delivery</li>
+  <li>Ensures that their team is communicating clearly so as to avoid blocking others when possible</li>
+  <li>Adapts to changes in volumes of prioritized work so as to enable smooth delivery (eg: can work with PM to plan for tracks that can be parallelized, or unified to increase/decrease throughput)</li>
+  <li>Reflects on a team's release process and continually evolves it to improve flow over time</li>
+  <li>Can articulate the impact of breaking changes to downstream teams and to customers</li>
+  <li>Breaks out of the existing tools or processes when necessary, to reframe and fix a flow issue</li>
+  </ul></td>
+
+<td valign="top"><ul>
+    <li>Recognizes systemic bottlenecks in delivering value to customers</li>
+    <li>Can identify and implement processes that provide the team ongoing feedback on flow</li>
+    <li>Intervenes to address systemic bottlenecks in delivering value to customers, using a variety of skill areas (e.g. technical execution/process)</li>
+    <li>Has knowledge of flow across the organization, and proactively shares context to unblock teams.</li>
+    <li>Applies engineering principles (rather than manual processes/toil) to improve flow</li>
+    <li>Can coordinate, execute, deliver to customer on complex integrations amongst multiple teams</li>
+
+ </ul>
+
+
+</td>  </tbody></table>   

niche-skill.md

@@ -0,0 +1,8 @@
+## Niche Skill
+Optional placeholder category, for specific skill-sets or specializations which are not expected of every pivot. A Niche skill is way for Pivot's to express their unique contributions to the org, and a way for leadership to recognize the impact of their unique skill. In order to use this category, the engineer, manager, and director must create and agree upon a career ladder for this skill-set. Once it's been created, the pivot commits to following this ladder if they want to be evaluated for performing that skill.
+
+Examples: subject matter expertise in MySQL, Facilitation
+
+*One example of success in this area*: You are on a team that has gone through two back-to-back rewrites. They haven't been able to ship and deliver on customer outcomes in over a year. You notice that the previous attempts to solve the customer problem didn't work because no one on the team has deep domain expertise on how container to container networking works. Additionally, you notice that there are other parts of the organization that could benefit from having thought leadership in this space. 
+
+Your manager, director, and you talk through what it could mean for you to develop expertise in Networking as it relates to Distributed Systems. All three of you collaboratively build a career ladder of value you could bring to the organization by developing this expertise at a beginner level all the way upto a P6 level. You embark on the journey to add 'Subject Matter Expertise in Networking' as a Niche Skill to your Skills Matrix, and commit to stay on the journey to improve your expertise in Networking for the foreseeable future.