Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Collaborative Technologies Content on InfoQ


RSS Feed
  • Working Remotely: Good Practices and Useful Resources

    As the impact of COVID-19 continues around the world, many people will be experiencing a sustained period of remote working for the first time. To help you, we’ve collated good remote working practices and resources and will continue to do so as more emerge. While remote working may appear straightforward, there are common issues that come up as you shift to this way of working.

  • Q&A on the Book Build a Next-Generation Digital Workplace

    The book Build a Next-Generation Digital Workplace by Shailesh Shivakumar explains what employee experience platforms (EXP) are and how digital technologies can be used to improve employee productivity, increase employee engagement, and support collaboration.

  • 10 Tools to Help Remote Web Developers Collaborate with Their Team

    Working remotely presents a unique set of challenges for web developers. However, by using the right tools and taking a ‘remote first’ attitude, you’ll find yourself being more productive than teams working face-to-face. Here are 10 tools for bug tracking, collaborative coding and knowledge management.

  • Collaborative Software Development Platforms for Crowdsourcing

    In this IEEE article, authors provide an overview of current technologies for crowdsourcing in software development. They talk about the requirements, current practice and trends in collaborative platforms.

  • Breaking Down Walls, Building Bridges, and Takin’ Out the Trash

    Agile Team Rooms can help double the productivity of an Agile Team. Most people are familiar with the Caves and Commons approach where the team has a common area on the inside of the room and private desks on the outside. Some teams dispense with the private spaces in the room, but few go as far as Menlo dispensing with the rooms altogether.

  • Choose Feature Teams over Component Teams for Agility

    Feature teams, common enough in small groups, are all too rare in large product development - but they can be a key to scaling with agility. This article analyses how feature teams resolve weaknesses of component teams, and points out key issues to address when transitioning. It is an excerpt from "Scaling Lean and Agile Development," by Craig Larman and Bas Vodde, to be published later this year.

  • Help Your Teams Trade Cubicles for Communication Skills

    The Agile “self organising team” paradigm demands new skills of team members – including the people skills for which they may once have depended upon their Project Managers. Far from being redundant, management can now play an important role in helping teams learn new ways to communicate and collaborate. This article proposes some strategies for imparting new skills and suggests some resources.

  • Offer People Reasons to Love Your Remote Meetings

    With an increasingly global workforce, face-to-face meetings are becoming rarer these days. In their place, we more frequently conduct business with a very different experience using a teleconference line supported by desktop sharing tools. Tips and tricks effectively facilitating these interactions, an emerging and important skill, are covered in this article.

  • Designing Collaborative Spaces for Productivity

    The typical Agile team may work in a common "teamroom", but personal space is also needed. Teams find out fast enough that some of the creature comforts left behind in their former traditional spaces were there for good reasons. This article shares the collected wisdom of dozens of teams who created their own work spaces, as collected by several experienced Agile coaches.

  • Agile Business Rules

    James Taylor looks at the challenge that arises when the new requirements are not really requirements at all, but new or changed business rules. Aren't business rules the same as requirements? Taylor says: no, not really; and looks at how to make an agile development processes work just as well for business rules as they do for other kinds of requirements.

  • Book Excerpt: Agile Retrospectives: Making Good Teams Great

    Project retrospectives help teams examine what went right and what went wrong on a project. Traditionally held at the end of a project, they're actually too late to help - no wonder we call them "post-mortems". Agile teams need retrospectives that are iterative and incremental, to find problems and design solutions to help teams improve early on, when improvement yields the most benefit.