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:

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