Closed wheresrhys closed 5 years ago
There are some feedback points in the J->M competency. Do we need to go further than this for S1->S2 or is this sufficient?:
J->M
Provides feedback on peer’s work, e.g.
Reviews pull requests and gives actionable empathetic feedback Recognises when a more senior colleague has not given enough detail in an explanation, and asks for clarification Gives realtime feedback in mob programming sessions
And J->M
Regularly gives timely actionable feedback to colleagues, e.g.
Emails positive feedback to a colleague's line manager, after the colleague was especially helpful. Notices that someone in the team has invited everyone to a meeting without an agenda. Asks them to add one so people know what the meeting is for and can prepare properly.
Let's discuss in our 3pm meeting
We also have this in the leadership section for s1->s2
Contributes to the personal development of more junior people, e.g.
- Pairs with more junior team members
- Mentors people
- Line manages people
- Writes blog posts
- Gives talks at meet-ups or conferences
and
Helps resolve disagreements healthily, e.g.
- Helps the team navigate disagreements over the best way to do things. Gets agreement and buy-in from engineers on a solution to a problem
- Encourages team members to speak freely in retrospectives
- Encourages team members to treat each other empathetically
The conclusion to our discussion of this was that delivering feedback is a tool for achieving other competencies around people skills, so doesn't need to be called out in its own competency. Also, successfully doing the competencies from lower levels around feedback is assumed. Are you happy with this @quarterto @leggsimon @Limess @ookejimift
Closing this as it seems like we're in agreement. We can reopen later if necessary
S1 workshop observed that there is nothing here on delivering feedback and probably should be