InfoQ Homepage Team Collaboration Content on InfoQ
-
Creating Psychological Safety in Your Teams
Psychological safety is a work climate where employees feel free to express their questions, concerns, ideas and mistakes. We cannot have high-performing teams without psychological safety. In this article, you will learn practical ideas, interesting stories, and powerful approaches to boost psychological safety in your team.
-
Remote Ensemble Testing - How an Experiment Shaped the Way We Work
This article shares how an experiment evolved into a common practice at the workplace, using an experimental approach with remote ensemble testing to get teammates on our cross-functional team more involved in the testing activities of the jointly created product. This all started in the times of a global pandemic where the entire team was working from home.
-
Growing an Experiment-Driven Quality Culture in Software Development
Have you ever faced a challenge at work that you weren’t sure how to tackle? Experiments to the rescue! In a complex environment like software development, no one can tell what might work, so we have to try things out. Read this article to learn about key challenges, insights and lessons, and get inspired for your own path to experimentation.
-
Hybrid Work is Here to Stay, and Software Teams Need to Adapt
In a post-pandemic workplace, face-to-face conversation is no longer the de facto collaboration method. As hybrid and distributed software development teams emerge, we look at ways that tools and processes can foster collaboration no matter where the team is located. Asynchronous work, a single source of truth, clear documentation and owners, and automation will empower hybrid development teams.
-
How to Enable Team Learning and Boost Performance
Team performance is dependent on safety, teamwork and ongoing learning. Clarity in roles, psychological safety, breaking bad habits and constantly learning are critical to enabling high performance.
-
How to Recognise and Reduce HumanDebt
We know TechDebt is bad; chances are HumanDebt is worse, and once you’ve seen it, you can’t “unsee” or ignore it. What is now needed is a focus on the humans who do the work. Psychological safety in teams is key. The “people work” -both at an individual, but especially at a team level- is the key to sustainability and growth of high-performing tech teams.
-
DEI Is Rooted in Justice: Stop Making it about Profit
Diversity, equity, and inclusion practices exist for the betterment of every single person within a company from the ground floor to the glass ceilings. Don't build a case for diversity, equity, and inclusion. You are an establishment that depends on other humans to operate your business and bring success. Their sense of belonging, inclusion, and psychological safety is your direct responsibility.
-
Facilitating Feedback That's Psychologically Safe
This article focuses on feedback with regards to a plan or proposal - ways to make it easier to give and receive feedback, so the psychological safety of the team can increase. The aim is to give you insights, models, structures and practical things to try, in order to facilitate feedback that boosts psychological safety in your team(s).
-
Augmenting Organizational Agility Through Learnability Quotient (LQ) - an Architect’s Perspective
By creating a robust learning framework for the organization, and involving architects and other key technical leaders, Halodoc improved their organizational agility.
-
Building Stronger Human Teams by Managing the Inner Lizards
Each of us has an inner lizard that frets constantly about our safety. People come with brains that are pre-configured to scan everything you say for threats to their safety. Learning to recognize when you're operating under reptilian influence is a great start. This article introduces some techniques to help you manage the lizard within you along with those around you.
-
Software Engineering at Google: Practices, Tools, Values, and Culture
The book Software Engineering at Google provides insights into the practices and tools used at Google to develop and maintain software with respect to time, scale, and the tradeoffs that all engineers make in development. It also explores the engineering values and the culture that’s based on them, emphasizing the main differences between programming and software engineering.
-
Evolutionary Architecture from an Organizational Perspective
Creating an architecture that can evolve over time is not simply a technical challenge, and requires collaboration with non-technical people in an organization to ensure the software adapts as needed.