BT

InfoQ Homepage Teamwork Content on InfoQ

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

  • Organizational Refactoring at Mango

    To increase agility, companies can descale themselves into value centers in charge of a business strategic initiative, with end-to-end responsibility and with full access to the information regarding customer needs. You need to create spaces where people can cross-collaborate and learn, using for instance self-organized improvement circles, Communities of Practice or an internal Open Source model.

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

  • Recognitions of 2018 World Agility Announced

    The 2018 world agility recognitions have been announced by the World Agility Forum. Next to regional recognitions for companies in Europe, Africa, and America, there are also recognitions for creativity agility, agile in defense, team agility, personal agility, and lifetime agility.

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

  • Readable Code - Why, How and When You Should Write It

    Most people would say they want readable code, and may even prefer readability over functionality. But when it comes down to asking people to define readability, opinions will start to diverge. At Explore DDD 2018 , Laura Savino covered why we want readable code, what it really means to be readable, and when readability absolutely must take priority over other considerations.

  • Lessons from the UK Government's Digital Transformation Journey

    Citizens can get the information and services they need more quickly because users' needs are considered in government service design, and suppliers can work with the government in modern agile ways: these are two benefits resulting from the UK Government's digital transformation. Having teams exposed directly to users motivates teams to make their products better.

  • Creating a Multi-Team Test Automation Solution

    A solid test framework with automated tests can increase the confidence to release. Cross-team pairing on the framework made it possible for a team to build quality in from the start; it also brought the teams together and upskilled the testers in test automation.

  • Atlassian Announces Solutions for Incident Management

    Atlassian announced on September 4 that they have launched a new product called Jira Ops and that they will acquire OpsGenie. Organizations can use Jira Ops for resolving incidents and doing post-mortems to learn from them. OpsGenie adds prompt and reliable alerting to Jira Ops.

  • Leading within: Evolving into Agility

    Adaptive organizations rely on horizontal leadership where awareness is a fundamental quality for leadership. When we are able to really listen with curiosity, empathy and courage, then our listening changes our perceptions, our relationships, and therefore, our environment.

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

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

  • Heroes Are Expensive - Extinguishing the Firefighting Culture

    Sue Johnston gave a talk at the recent Agile2018 Conference in San Diego titled "Heroes Are Expensive - Extinguishing The Firefighting Culture". She identified how to spot a hero, what leads team members and leaders to heroics, what the impact is, what we can do about it, and how we can redefine what a Hero is.

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

  • Strategies for Microservices Communication

    When moving from a monolith to a microservices architecture, complexity implicitly hidden within the monolith becomes explicitly visible and the challenges for communication will grow exponentially, Michael Plöd explained in a presentation at GeeCON 2018, describing different strategies for communicating between microservices.

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.