InfoQ Homepage Team Collaboration Content on InfoQ
-
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.
-
Culture & Methods Trends Report March 2021
The most significant impact on culture and methods in 2021 is the disruption caused by COVID-19. We look at what's needed for good remote and the impact of bad remote, how management practices are evolving, and the importance of people skills for technologists. Paying attention to ethical issues, diversity and inclusion, tech for good, employee experience and psychological safety are important.
-
Sociotechnical Implications of Using Machines as Teammates
AI has become more than just a tool; it is now meriting consideration as an additional teammate. While this increases a project’s efficiency and technical rigor, AI teammates bring a fresh set of challenges around social integration, team dynamics, trust, and control. This article provides an overview of sociotechnical frameworks and strategies to address concerns with using machines as teammates.
-
Who is on the Team?
Ahmad Fahmy and Cesario Ramos take the changes to the new Scrum Guide as an opportunity to explore what it means to be "on a team." They draw on research to create an ACID test to differentiate who is on the team and who isn't. They discuss different mental models around the idea of a team with the hopes that you take this opportunity to discuss and elevate the roles within your organization.
-
Learning from Incidents
Jessica DeVita (Netflix) and Nick Stenning (Microsoft) have been working on improving how software teams learn from incidents in production. In this article, they share some of what they’ve learned from the research community in this area, and offer some advice on the practical application of this work.
-
Dealing with Remote Team Challenges
Remote working provides challenges such as providing equitable access, ensuring adequate resources and tooling, addressing social isolation and issues of trust. Remote-first and truly asynchronous teams tend to consistently perform better. In the future, organisations will continue to have remote on their agenda. Fully realising the benefits of remote teams requires trust building and intent.