The foundational assumption is that the team has psychological safety, motivation to learn, send of responsibility, a willingness to accept and provide feedback
We encourage the team to respect each other and build trust in each other
In many environments, people are taught to be competitive, and people may feel insecure about asking questions or not knowing something. This, unfortunately, minimizes learning. During our sessions, we encourage the team to have psychological safety
To feel ok about asking questions, to feel ok about not knowing something or asking for help
To be able to accept and receive feedback
We assume that the whole team arrives at the session with a passing build/test
To achieve this, it includes:
Developers have resolved any merge conflicts with their colleagues outside of the coaching session
Developers have checked that their local build is passing - this means compilation passes and tests pass
Developers have checked that their pipeline is passing - this means compilation passes, tests pass and deployment passes (as a minimum)
We expect at the start of the session that all tests are passing; if some tests are in-progress or you're investigating reasons for failure, then those tests should be marked as skipped or ignored (with a reason why)
If the above has not been satisfied, then we will have to spend time during the session to resolve merge conflicts, make the build pass, etc. That would decrease the value of our sessions.
We assume that the team arrives to sessions on time.
To be able to arrive on time:
Please ensure your calendar notifications are turned off
Wrap up your previous meetings
In the case of lateness, we do not extend the session. Even a small 5 mins delay means we are losing out ~ 10% of coaching time.