InfoQ Homepage Distributed Team Content on InfoQ
-
Successful Remote Working
For both employees and employers, remote work requires intentional design and implementation to be effective. People find remote work challenging because the established mindset says that being in an office is how work gets done. Despite the challenges, when remote work is done well, the advantages to employees and employer are sufficient to make it worthwhile.
-
Remote Work Flourishes and Enables Business Continuity
Buffer.com and AngelList recently published the 2020 State of Remote Work survey results. The survey coincides with a report by the Wall Street Journal on a sudden boom in remote working within China. Remote work has enabled business continuity across companies like Alibaba, in response to mobility restrictions imposed due to the COVID-19 virus.
-
Making Remote Mob Testing Work
Remote mob testing can be done successfully, but requires suitable communication technology, a moderator who keeps everyone on board, and you need to frequently change the driver between local team members and remotes.
-
Developing Cultural Sensitivity in Working with Other Cultures
Cultural differences can be a challenge in an international workplace, but at the same time cultural diversity can also be fascinating, said Rachel Smets. At Positive Psychology in Practice 2019 she suggested we prepare ourselves when working with other cultures or moving abroad, and develop our cultural sensitivity by learning about new cultures as much as we can.
-
DOES London: Team Topologies and Cognitive Load
At the DevOps Enterprise Summit in London this year, authors of the soon-to-be-published 'Team Topologies', a book that aims to offer a practical, adaptive model for organisational design, Matthew Skelton and Manuel Pais, took to the stage to share their thoughts with the audience.
-
Defining Bounded Contexts — Eric Evans at DDD Europe
A bounded context is a defined part of software where particular terms and rules apply in a consistent way, Eric Evans explained in his keynote at DDD Europe earlier this year; it should have a refined model and a language with unambiguous definitions. In a recently published presentation, he describes different kinds of bounded contexts, including some that involve microservices.
-
Experiences from Working with Distributed Agile Teams
Not being able to frequently connect with your colleagues face-to-face makes successful communication more difficult in distributed teams, said Shabi Shafei, Scrum Master at ABN AMRO Bank. A Q&A about how distributed teams can transform into great agile teams.
-
Building High-Quality Products with Distributed Teams
To ensure the quality of the products and services, Intermedia uses a common test & pre-production environment for all distributed teams. Lilia Gorbachik, product manager at Intermedia, mentioned at European Women in Tech that having a mature testing process, working with risks, and making daily decisions from a high-quality product perspective are key aspects to build high-quality products.
-
Experiences from Remote Mob Programming: Q&A with Sal Freudenberg
At Cucumber, mob programming is done remotely by using a cycle in which the driver pulls down the latest code and then shares their screen, the team mobs for 10 minutes or so and commits the code. Next, the driver’s role rotates. “Remote mobbing works really well for me”, says Sal Freudenberg, “because it lets me tailor my working environment and work in a spot where I feel comfortable.”
-
How to Work Effectively with Agile in a Remote Team: Trust, Accountability and Communication
In a session titled Being Agile in a Remote Team at the recent Agile2018 conference, Shane Hastie and Shannon Ewan addressed the topic of distributed agile teams and what makes them work. They discussed qualities of high performing teams, myths of remote teams and strategies to make remote teams work while sharing their story of how they work at ICAgile (a fully remote team and organization).
-
Keeping Distributed Teams in Sync
The biggest challenge of distributed teams is communication, which is essential for establishing ground rules on collaboration. Shifting working hours to accommodate each other and team liaisons help to communicate and synchronize work. Teams based on trust, respect, and openness will encourage themselves to help people throughout the organization and foster a culture that keeps teams in sync.
-
QCon New York Day 1 – High Velocity Development Teams Track Summary
QCon New York was heeled this week. This is a summary of the key messages from the opening keynote and from the High Velocity Development Teams track.
-
Making Distributed Development Work
Distributed development depends on effective communication: you need to look for ways to have robust and diverse communication, build empathy towards each other to encourage feedback, and keep an eye on motivation. Team members are more engaged and creative when there’s shared ownership and responsibility for complete delivery from idea to production in distributed teams.
-
Eric J. McNulty : Your People’s Brains Need Face Time
In a recent Strategy and Business article, leadership author Eric J. McNulty wrote about why distributed teams need to get together on a regular basis in order to be most effective. He cites research into distributed teams which shows that the value of face-to-face sessions far exceeds the cost of bringing people together.
-
Opinion: What 2017 Has in Store for Culture & Methods
We polled the InfoQ Culture & Methods editors for their takes on what 2017 has in store for the technology industry, what are the trends which we see coming to the fore and what the implications will be for organizations around the globe.