InfoQ Homepage Team Collaboration Content on InfoQ
-
Incident Management During Remote Work
Michael Fisher, a technology enthusiast and group product manager at OpsRamp, recently blogged about how IT operations and DevOps teams can take a problem-first approach towards the incident management process. On the same lines, Dr. Laura Maguire and Nora Jones wrote about similar challenges as the world reacts to COVID-19.
-
How Team Interactions Help Kubernetes Adoption with Manuel Pais at QCon London
Manuel Pais talked at QCon London about how team interactions are vital to reduce cognitive load to have a successful adoption of Kubernetes. Pais recommends having a digital platform on top of Kubernetes. And, organizations can get started by assessing the team's cognitive load, defining a digital platform, and setting clear team interactions.
-
DevOps beyond Development and Operations with Patrick Debois at QCon London
Patrick Debois talked at QCon London about thinking of DevOps beyond development and operation silos. DevOps is inherently complex, and there are other risks, challenges, and bottlenecks outside the software delivery pipeline where collaboration is vital, for instance, when collaborating with other groups like suppliers, HR, marketing, sales, finance, or legal.
-
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.
-
What Will the Next 10 Years of Continuous Delivery Look Like?
Dave Farley and Jez Humble talked at the DeliveryConf about their expectations for the next ten years of Continous Delivery (CD). For CD to succeed, the IT industry needs to focus on three performance aspects: technical, organizational, and cultural–all profoundly interrelated. DORA's report has shown that technical practices can lead the change, but they alone aren't enough.
-
Google Software Engineering Culture
Several Google engineering practices have been largely adopted across the company until today and still contribute to the company's success. In 2017, a staff software engineer published some of these practices, not limited to software development. Today, Google fosters a team culture of creativity, autonomy, and innovation.
-
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.
-
Barriers and Approaches for DevOps Evolution at 1st DevOpsDays Portugal
Ten years after the first DevOpsDays conference in Ghent, the evolution of DevOps and organizations trying to adopt it was at the forefront of the first DevOpsDays conference in Portugal. On the first day of the conference, a mix of local and international speakers addressed the barriers to DevOps adoption, shift left testing, team patterns, and more.
-
Experience Building a QA Team in a Growing Organization
Shifting the test team to the left brought the whole team closer together, enabled faster learning, and improved collaboration, claimed Neven Matas, QA team lead at Infinum. He spoke at TestCon Moscow 2019 where he shared the lessons learned from building a QA team in a growing organization.
-
Tuckman Was Wrong! Doc Norton on Reteaming Models
At Agile India 2019, Doc Norton shared why the Tuckman team formation model doesn’t work and described new reteaming models that are more applicable to current agile teams. Norton shared reteaming models that foster organizational innovation and learning and identified 4 criteria leading to better teams’ performance: autonomy, connection, excellence and diversity.
-
Effective Mob Programming Patterns
Lisi Hocke spoke at the Testing United conference in Bratislava about how she helped shape a collaborative environment through the use of mob-programming. Hocke described how her team effectively used a strong-pairing style. Maaret Pyhäjärvi and Jeff Langr have both recently written about their own patterns for maximising the benefits of mob programming. We survey their experiences.
-
Retrospective 3.0 at Ocado Technology
Toni Tassani identifies retrospective pitfalls, such as stale and repetitive activities and raises risks: the retrospective as an excuse for not solving issues on the spot, identifying an experiment but not driving the impediment to resolution, Post-it theater. He suggests looking at retrospectives radically differently, leveraging continuous improvement techniques borrowed from Kanban.
-
Boosting Team Inclusion at the Workplace Using Artificial Intelligence Technologies
Boosting Team Inclusion at the Workplace using Technologies establishes that active inclusion enables diverse teams to exceed their performance goals. Gartner suggests leveraging new artificial intelligence powered applications in three areas: sourcing inclusive-ready candidates, analyzing teams' interaction, and training team leaders.
-
A Brief History of High-Performing Teams by Jessica Kerr
If you're looking for an early example of a high-performing, agile team, then study the Florentine Camerata, a group formed in Florence, Italy, around 1580 that reformed their contemporary music with the creation of opera. The lessons of the camerata, and similar teams throughout history, were the subject of Jessica Kerr's keynote presentation at Explore DDD 2018.
-
Q&A with Jeff Smith on His DevOpsDays NZ Keynote on DevOps Transformations
InfoQ catches up with Jeff Smith on Centro transformation to a DevOps culture, which will feature in his forthcoming keynote at DevOpsDays NZ. Smith also discusses his recent DevOpsDays Indianapolis talk on the misalignment which can arise due to the different lenses through which collaborators see the world.