InfoQ Homepage Collaboration Content on InfoQ
-
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.
-
Exercises for Building Better Teams
Have you ever seen a team perform so great that you wanted to join it? If you examine the values of such a team, you may discover a perfect balance of orientation on people and results. If you are trying to discover how far away your own team is from this state, read this article and try the exercises to find your own state of perfection.
-
DevOps Lessons Learned at Microsoft Engineering
Thiago Almeida from Microsoft shares how adopting DevOps practices resulted in better engineering and happier teams, and the lessons learned in that journey.
-
The Volcano - Prioritize Work for Multiple Teams & Products
It is always a challenge to pick the correct priorities. Which one of work item A, B or C shall you do first, and why? Tomas Rybing presents the Volcano, a tool to visualize and prioritize work for multiple teams working with several products.
-
Q&A on Achieving Impact through Engagement
The book achieving impact through engagement by Si Alhir and and Peter L. Simon explores two models on employee and customer engagement: The Ownership Pyramid (TOP) and Artful Agility or Actions-Intentions-Results (AIR). Together these models can be used to achieve impact in organizations based on increasing engagement.
-
Q&A with the Authors on "Requirements: The Masterclass LiveLessons-Traditional, Agile, Outsourcing"
Suzanne and James Robertson, authors of numerous publications in the requirements field, launched a video course called "Requirements: The Masterclass LiveLessons-Traditional, Agile, Outsourcing". InfoQ interviewed them on these video lessons to get further insights into some of the topics addressed.
-
Characteristics of a Great Scrum Team
This article explores 'What makes a great Scrum team?' by offering detailed descriptions of the characteristics and skills needed in the Scrum roles of Product Owner, Scrum Master and Development Team.
-
Change from Within: Developers and Managers Working Together
InfoQ interviewed Bryan Dove from Skyscanner about the major technology developments from the last 10 years and the impact these have had on the way that we are creating software products. InfoQ also asked him what managers and developers can do to explore and find better ways of working together and how they can support each other, making themselves and the company more successful.
-
Agile Productivity: Willpower and the Neuroscience Approach
Productivity depends on the ability to concentrate and to keep that concentration long enough to advance towards your goals and get results. This article explores three strategies to save willpower energy and increase the ability to concentrate, and shows what pieces of Scrum work for which of the three strategies to increase productivity.
-
Q&A on the book Visualization Examples
The book Toolbox for the Agile Coach - Visualization Examples by Jimmy Janlén can be used by agile software development teams to visualize and improve their collaboration and communication. InfoQ interviewed Janlén about the strengths of visualizations and how teams can use them to track progress, deal with blockers, celebrate successes and improve.
-
Large Scaled-Scrum Development Does Work!
Agile Scrum development as such is nothing new and extraordinary. But when putting up to 100 professionals from all related development and product areas in the same boat to develop a product … then it becomes a challenge. This article explores how the Ericsson ICT Development Center Eurolab in Aachen has tackled this with the help of Kaizen and other adjustments to Agile practices.
-
Connect Agile Teams to Organizational Hierarchy: A Sociocratic Solution
Many agile teams suffer from the mismatch of agile and organizational leadership with the latter being reflected by the organizational hierarchy. This article suggests using sociocracy as a solution that leaves the hierarchies in place yet still allows teams to act in an agile way.