BT

InfoQ Homepage Team Collaboration Content on InfoQ

  • 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.

  • How to Grow Teams That Can Fail without Fear: QCon London Q&A

    Blameless failure starts with building a culture where failure is acknowledged, shared, investigated, remedied, and prevented, said Emma Button, a DevOps and cloud consultant, at QCon London 2019. Visualising the health and state of your system with CI/CD practices can increase trust and ownership and invite people to help out when things fail.

  • 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.

  • Reflections on Technical Leading: Q&A with Julia Hayward at Agile in the City Bristol

    Employers need to adopt fluid structures for people to find balance in their role, technical and managerial paths should lie side by side, you can’t have genuine effective growth without psychological safety, and a good mentor to talk about problems and scenarios is invaluable; these are some of the reflections on technical leading brought up by Julia Hayward, technical lead at Redgate Software.

  • 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.

  • How Continuous Delivery Impacts Testing

    With continuous delivery we need to focus on quality as we write the code. Not every team will have testers, but if there are testers then they will work closely with developers, writing code to automate the small number of tests that cannot be covered by unit tests while helping developers creating unit tests.

  • Psychological Safety in Post-Mortems

    Emotions often come to the fore when there is an incident; psychological safety in blameless post-mortems is essential for the learning process to happen. The post-mortem session must be fairly moderated, preferably by an outsider, giving everyone a turn to speak without criticism. Don’t start the analysis of the incident before there is a clear and common understanding of what actually happened.

  • Spark the Change: Unleashing People’s Talent

    Make curiosity our priority, fundamentally question how and when work should happen, enable fragmentation with technology to become a task-based society, maximize the possibility of authentic human connection in recruiting, ask questions to spark the change, and look for ways to integrate refugees into the workforce: These are some of the conclusions and suggestions to unleash people’s talent.

  • Breaking Codes, Designing Jets and Building Teams: Randy Shoup Discusses High Performing Teams

    At QCon NY, Randy Shoup, VP Engineering at WeWork, presented “Breaking Codes, Designing Jets and Building Teams”. He began the talk by quoting Mark Twain, “History doesn’t repeat itself, but it often rhymes”, and stated that throughout history he believes the most effective teams have focused on purpose, organisational culture, people, and engineering excellence.

  • Making Games for High Performing Teams

    The gamestorming model describes a process to create games. It provides concepts like game space, boundaries, rules, artifacts and goals, for creating compelling learning experiences in an organizational setting. Such games can be used by teams to experiment, focus on outcomes, and try out disruptive patterns.

  • From Darwin to DevOps: John Willis and Gene Kim Talk about Life after The Phoenix Project

    IT Revolution recently published an audiobook with nearly eight hours of conversation between Gene Kim and John Willis; Beyond the Phoenix Project – the Origins and Evolution of DevOps.

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.