InfoQ Homepage Teamwork Content on InfoQ
-
Why the Dual Operating Model Impedes Enterprise Agility
Most organizations adopt a dual approach to agility, with some parts of the organization working in an agile way that delivers value in increments, measures the response and adapts accordingly, while the “traditional” organization continues to work as it always has in a relatively top-down way. In this article, This approach must eventually be left behind after an Agile transition.
-
How to Run Your Product Department Like a Coach
Having found what I thought was my calling as an agile coach, I took the tough decision to move sideways into Product Management in the hopes of using what I’d learned to one day run my own department. I believed that coming from coaching would allow me to see things others could not and create something special. Time will tell if I have succeeded. This is the story of where I am so far.
-
Connecting Goals to Daily Teamwork
While we all believe that goal setting is important, it’s work that often doesn’t feel quite urgent enough to be included in our daily routine. It is critical to team success for managers to implement a regular cadence that connects daily work more directly to high-level goals, removing administrative roadblocks while helping teammates focus on what matters most.
-
Reducing Cognitive Load in Agile DevOps Teams Using Team Topologies
In this article we will be sharing our experience from 12 months of adopting certain management and organisational insights from the book Team Topologies. It explores how we identified areas of responsibility and assigned those into mostly customer-facing domains which could be given to our teams. It shows how an inverse Conway manoeuvre can be used to improve the architecture.
-
Making Agile Work in Asynchronous and Hybrid Environments
Making Agile work in the age of hybrid and remote teams requires extra effort to stay aligned and collaborative. This article explores how development teams can stay agile, even when face-to-face collaboration isn’t an option, by using visual collaboration to build context and alignment, and adopting new practices for engaging meetings.
-
How Psychological Safety at Work Creates Effective Software Tech Teams That Learn and Grow
This article provides the foundations of psychological safety and shows how it has been applied for team effectiveness. It explores how psychological safety supports learning and improvement and how we can foster a psychologically safe culture in tech teams.
-
InfoQ Culture & Methods Trends Report - March 2022
The culture and methods trends report for 2022 shows that organizations, teams, and individuals face challenges on multiple fronts. Tackling hybrid work, the impact of the great resignation, wellness, diversity, and inclusion are topics that leaders need to address head-on to build creative and collaborative cultures
-
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.