InfoQ Homepage Collaboration Content on InfoQ
-
Open-Source Testing: Why Bug Bounty Programs Should Be Embraced, Not Feared
The growing importance of the Web3 ecosystem based on blockchains shows how important community test programs are. Some within the testing community see this trend as a threat. However, it is actually an opportunity. Bug bounties and open-source test contributions are a great tool for test teams, and there is every reason for testers to embrace this new trend rather than to fear it.
-
How to Introduce Innovation into the DNA of 21st Century Companies
An innovation mindset is about the tiny little improvements any employee can do; hundreds of simple, low-cost- no-effort activities are in plain sight just waiting for somebody to deploy them. This article provides guidelines that can support you in changing the attitude of employees in your organization providing trust, time, space, teams, a second operating system, MVPs, and co-creation.
-
What Kind of Coach Does Your Team Need?
Coaching is primarily client-driven; the client chooses the right coach for a particular need at a particular time. However, the team may first need to understand what coaching is before deciding what kind of coach they need, and why they need it. This article examines the role that a coach can play in establishing, maintaining and nurturing a safe space for teams to grow and achieve their goals.
-
How to Accelerate Your Staff+ Career through Open Source Engagement
It takes many factors for an engineer to land a Staff+ position. In this article, you’ll find how contributing and engaging to open-source can help you sharpen critical Staff+ skills like writing communication, while helping increase your visibility and the odds of landing in such a position.
-
Pipedrive Agile Framework: How a Unicorn Company Customized Agile Processes to Scale
Pipedrive would not have become a unicorn company by using a standard off-the-shelf agile framework. Instead, the company created its own framework. It makes a distinction between Mission Teams versus Launchpads and relies heavily on dynamic reteaming. In Pipedrive's Agile Framework, the product managers pitch new ideas and software engineers volunteer to lead their Mission Teams.
-
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.
-
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.
-
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.
-
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.