Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

Build Psychological Safety in Teams Through Code Reviews

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

How would you describe your experience when someone reviews your code?

Many developers report this is a source of stress, conflicts, and even power and ego struggles.

The above-described situation can be framed as a psychological safety problem.

Psychological Safety is key in team dynamics and was identified as the most important factor that predicts Google’s successful team in Google’s team effectiveness research.

“Psychological safety …is a shared belief that the team is safe for interpersonal risk-taking. In psychologically safe teams, team members feel accepted and respected”(source: Wikipedia)

“Protecting people is the most important thing we can do because it frees people to take risks and unlocks their potential.” (source: Industrial logic: Anzeneering)

Code reviews are a frequent opportunity for building (or jeopardizing) Psychological Safety in the team.

The first step is to acknowledge and pay attention to psychological safety.

Here are 8 tips for leveraging code reviews to build safety – 

Regularly discuss with the team – Start talking openly about the review process. In the team’s retrospective meeting, ask “how do you feel about this process?”, “What are the main insights we learned?” As a leader, it is recommended to share your own mistakes (be vulnerable) to free people from their defensive mode.
Code review together – Make the code review a great learning experience by avoiding offline reviews: review the code together – pair review (it may sound initially like a waste of time but give it a try, you will probably not  regret it).
Be empathetic  – invest in explaining alternatives and asking clarifying questions. Don’t be judgemental, use open and curious questions.
Be positive – approach the session as a learning experience and use a positive tone.
Explain coding guidelines and best practices   – In your comments point to standards and guidelines that were agreed to and defined (e.g., “this is how we write python here”).
Frequent small reviews – Try having frequent reviews, on small changes, to get fast feedback. Short and focused discussions are easier to absorb. 
Separate the wheat from the chaff – is this comment really important now?
Have a clear “Definition of Done” – For example, what level of the automated test is expected?

Code reviews play a central role in the dynamics of development teams. A poorly executed process may be a significant source of delay and bad morale. A great process provides great learning opportunities and grows a high-performing team that people want to be part of. 

Yael & Yaki

Subscribe for Email Updates:

Categories:

Tags:

AgileSparks
The Agile Coach
Frameworks
Agile Assembly Architecture
Agile Israel Events
Story Slicing
LPM
Kanban 101
chatgpt
Operational Value Stream
PI Planning
Implementing SAFe
Release Train Engineer
Legacy Enterprise
IT Operations
Agile Product Ownership
RTE
Hybrid Work
Continuous Planning
speed at scale
Business Agility
Perfection Game
Certification
Iterative Incremental Development
Product Ownership
Development Value Streams
Nexus
ART Success
Program Increment
Scrum Values
Agile Release Management
A Kanban System for Software Engineering
Lean Risk Management
Agile Project Management
Accelerate Value Delivery At Scale
Risk-aware Product Development
Agile Release Planning
Entrepreneurial Operating System®
Large Scale Scrum
Risk Management on Agile Projects
RSA
Pomodoro Technique
Elastic Leadership
Coaching Agile Teams
Artificial Intelligence
Sprint Iteration
Daily Scrum
SPC
ALM Tools
Agile Outsourcing
Agile in the Enterprise
Effective Agile Retrospectives
Scrum Master Role
ATDD vs. BDD
Kanban Basics
Lean Budgeting
PI Objectives
lean agile change management
ROI
Built-In Quality
Nexus and Kanban
Agile
SAFe Release Planning
Spotify
SAFe DevOps
System Archetypes
Advanced Roadmaps
Tips
Continuous Delivery
Change Management
Scaled Agile Framework
The Kanban Method
Agile Exercises
Tools
Certified SAFe
speed @ scale
Managing Projects
Value Streams
Kaizen
Professional Scrum Master
Atlaassian
Agile Games and Exercises
Applying Agile Methodology
Agile Development
Nexus and SAFe
GanttBan
Achieve Business Agility
Agile Project
Software Development Estimation
Lean Agile
Agile Product Development
Engineering Practices
Agile Community
Introduction to ATDD
AI Artificial Intelligence
SAFe
Video
POPM
Scrum.org
Kaizen Workshop
Rapid RTC
ARTs
Scrum
Professional Scrum with Kanban
DevOps
Slides
Agile Risk Management
Jira Plans
Principles of Lean-Agile Leadership
Agile Contracts Best Practices
Agile Techniques
Nexus vs SAFe
Lean and Agile Principles and Practices
Agile Games
Continuous Integration
Continuous Deployment
Professional Scrum Product Owner
Risk Management in Kanban
ATDD
Agility
Agile Mindset
Lean Agile Management
Agile Testing Practices
Lean Agile Leadership
Scrum Primer
Portfolio for Jira
Lean-Agile Software Development
Introduction to Test Driven Development
What Is Kanban
predictability
Manage Budget Creation
agileisrael
Scrum and XP
Agile India
Agile Delivery
Self-organization
Scrum Master
Process Improvement
Kanban
WIP
RTE Role
Jira Cloud
Software Development
System Integration Environments
Lean Software Development
BDD
Kanban Kickstart Example
Games and Exercises
Presentation
Lean and Agile Techniques
Sprint Retrospectives
Sprint Planning
EOS®
Agile Marketing
Reading List
Atlassian
Scrum Guide
An Appreciative Retrospective
LeSS
SA
Covid19
Jira admin
Scrum With Kanban
NIT
Code
Enterprise DevOps
Agile Israel
Releases Using Lean
Legacy Code
Systems Thinking
Quality Assurance
Agile Program
ScrumMaster Tales
Agile Basics
Amdocs
Continuous Improvement
Lean Agile Basics
Planning
System Team
Lean-Agile Budgeting
Limiting Work in Progress
Nexus Integration Team
Product Management
Agile and DevOps Journey
LAB
AI
User stories
Kanban Game
Implementation of Lean and Agile
Lean Agile Organization
Test Driven Development
Lean Startup
Webinar
Agile for Embedded Systems
TDD
Acceptance Test-Driven Development
QA
Jira
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart