InfoQ Homepage Co-Located Teams Content on InfoQ


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

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

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

  • Researcher Recognized for Advances in Team Performance Techniques

    Eduardo Salas is recognized by the APA for his 30 years of research on team work. His implementation of team training includes defining team structure, identifying specific communication needs, clarifying roles and leadership skills, and practicing with scenarios. This technique has been used across many fields of work, and is part of the program as NASA prepares to send a team to Mars.

  • Creating an Agile Workplace

    An agile workplace is one that is constantly changing, adjusting and responding to organizational needs. How to create an Agile workplace and what are the benefits.

  • Jurgen Appelo on Better Management with Fewer Managers

    At the Dare Festival Antwerp 2014 Jurgen Appelo talked about his new book Management 3.0 Workout and showed examples how organizations can improve the way that they manage themselves.

  • Reactions to Yahoo!’s Decision to Forbid Employee Telecommuting

    Yahoo!’s recent decision to call all employees to work from company’s offices has raised some questions especially throughout the telecommuting community. Is this a disguised move to lay off people? Is it a misunderstanding of how remoting is to be managed? Is this the right move for Yahoo!?

  • Is Agile Stifling Introverts?

    For years Agile has been encouraging teams to work together collaboratively in open spaces and encouraging developers to pair program, but lately these types of practices have been coming under fire.

  • Co-location Transition, Tips and Concerns

    What are the tricks to successfully transitioning from cubicles to a team room? What are the concerns? Ideas include: make the change an experiment, make sure everyone is heard.

  • Complaint-Free Iterations

    No software project is perfect, nor is the organization in which the project takes place. When your software project goes wrong, do your team members complain, or do they take corrective action? The Complaint Free World project encourages people to take notice of how often they complain, and reduce the frequency of the complaints, aiming for a goal of twenty-one complaint-free days.

  • Well Formed Teams: Helping Teams Thrive, not just Survive

    What does it take to create a high-performing team? According to Doug Shimp and Samall Hazziez, a "Well Formed Team" exhibits the following characteristics: follow Agile and Lean principles, use an adaptive system with a feedback loop, are focused on the business vision, are passionate and hyper-productive.

  • Do Dedicated Team Rooms Make for More Productive Teams?

    Following a recent article on Science Daily, and a flurry of activity on the Lean Agile Scrum mailing list, InfoQ summarizes what factors make for an optimal team room, and in some cases influence whether a team room is effective at all.

  • Sharing What's Worked: Patterns for Adopting Agile Practices

    Organizations adopting Agile naturally ask these questions; "Where do I start?", "What specific practices should I adopt?", "How can I adopt incrementally?" and "Where can I expect pitfalls?" In this article, Amr Elssamadisy gives a glimpse into an ongoing effort to document Agile practice adoption patterns: Participants at XPday Montreal took a stab at "Simple Design" and "Pair Programming."

  • Common misconceptions about paired programming

    Paired programming is an agile practice that is the source of much debate. Martin Fowler has posted an article on common misconceptions with paired programming, suggesting that pair programming is not a requirement of XP, it does not halve productivity, and others.

  • Study: Co-Located Teams vs. the Cubicle Farm

    Many trainers agree that co-location is essential to really see the benefits of Agile, but proof of this has been largely anecdotal. On the ScrumDevelopment list recently, an interesting conversation was launched when a member pointed out a study conducted at a Fortune 50 auto maker, comparing productivity gains in collaborative workspaces versus traditional cubicle culture projects.


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:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.