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.
| Level | Skills |
| P1 |
- Follows along with existing engineering process on teams (eg: TDD, pairing, CI and Tracker discipline, etc.)
|
| P2 |
- Understands and explains the importance of improving feedback loops
- Makes small tweaks to engineering process on their team, in response to retro items or team discussion.
- Can onboard new team members on existing processes
- Understands and explains why balanced teams and balanced decision-making is important
- Can explain parts of our engineering process in terms of improving feedback loops
- Shows discipline in upholding the team's engineering process
- Provides feedback to teammates.
|
| P3 |
- Understands and explains the XP/Agile principles behind specific practices of team's engineering process
- Identifies larger problems on teams that can be fixed by changing engineering process
- Advocates for a balanced team, and facilitates balanced decision-making
- Actively works to improve engineering process and feedback loops on teams
- Provides T.A.S.K feedback to teammates, that helps teammates grow
|
| P4 |
- Provides challenging feedback (kindly) and coaches teammates to change their behaviour
- Teaches our engineering process to new Pivots and relates it back to XP/Agile principles
- Recommends and proliferates team-wide changes to engineering process, to fix team pain-points.
- Adapts to different flavors of process and ties it back to XP/Agile principles
- Is an exemplary role-model for practicing and facilitating balanced decision-making
- Continually works to evolve the engineering process on their teams
|
| P5 |
- Innovates on engineering process and evangelizes that change across the org. Follows through by helping relevant and interested teams adopt it successfully
|