InfoQ Homepage Teamwork Content on InfoQ
-
Five Tips on Managing a Remote-First Development Team
Most software development teams have gone remote during the pandemic - and may stay remote even after the lockdowns. Managing remote-first teams is a challenge. Knowing how to do it right can make or break the experience for everyone. Here are five things you can do to succeed as an engineering manager.
-
Goal-Driven Kanban: Improving Performance and Motivating Teams
Goal-Driven Kanban enables teams to choose from and focus on challenging goals along the road. Teams are free to choose their pace and can take a break whenever necessary. They can set a voluntary deadline for the goal chosen together with proper time allocation. Naturally, while pursuing the goal, teams avoid distractions, celebrate achievements, and retrospect frequently.
-
Talking Like a Suit - Communicating the Importance of Engineering Work in Business Terms
This article explores how to construct engineering work as a story, including clearly presenting a problem, offering a solution, and showing the business a path to success that solves their problem and avoids failure. By presenting your case in this way, you significantly increase your chances of getting these engineering problems addressed, while also becoming a better partner for the business.
-
Better Metrics for Building High Performance Teams
There is no agreed way to build and measure high performing engineering teams, let alone to track the success of software engineers. This article explores ways to support individuals and teams right from onboarding and identifies useful metrics which can help make performance factors visible and actionable. Developer onboarding, dynamic documentation, and asynchronous communication are key.
-
How the Financial Times Approaches Engineering Enablement
Companies need teams working on infrastructure, tooling and platforms; the way they work has to change so that they do not become a bottleneck. These teams need to be about enabling product teams to deliver business value. Investment in this area pays off as it speeds up many other teams and allows product-team engineers to focus on solving business problems that provide value to the organisation.
-
Hybrid & Remote Work in 2022 and Beyond
Moving into 2022, ways of working and interacting are continuing to evolve as organisations adapt to the ongoing changes brought about by a wide range of factors influenced by the COVID-19 pandemic. Making remote work sustainable, flexible, hybrid and asynchronous working, recognising the importance of employee experience and supporting mental wellness are important trends in the future of work.
-
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.
-
How Space Shapes Collaboration: Using Anthropology to Break Silos
Software companies strive to keep innovating and changing the rules of the market. These companies are made of people who, unlike smartphones, personal computers or smart watches, have not evolved as much in recent years. This article proposes an analysis of workspaces from anthropology to solve one of the most common problems: the appearance of silos instead of a culture of collaboration.
-
Avoiding Technical Bankruptcy: a Whole-Organization Perspective on Technical Debt
Technical debt is not primarily caused by clumsy programming, and hence we cannot hope to fix it by more skilled programming alone. Rather, technical debt is a third-order effect of poor communication. What we observe and label “technical debt” is the by-product of a dysfunctional process. To fix the problem of accumulating technical debt, we need to fix this broken process.
-
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.
-
Measure Outcomes, Not Outputs: Software Development in Today’s Remote Work World
Today’s remote work world calls for a closer look at how to measure software developer productivity. Currently, there is no standard metric and widely used methods are flawed. The author describes how they successfully lead 500+ remote software developers by measuring outcomes, rather than outputs in order to produce the ideal balance between speed and quality code development.
-
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.