InfoQ Homepage Teamwork Content on InfoQ
-
The Things I Learnt about DevOps When My Car Was Engulfed by Flames
Framed in the story of the author's car catching fire, this article describes five ways of thinking to help understand DevOps culture, and behaviours necessary to create an effective DevOps team. A central theme is that DevOps challenges us to think differently about our approach to collaboration and learning, in ways often contrary to our instincts and how we’ve been encouraged to behave before.
-
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.
-
Organizing the Test Team
The tester/programmer ratio continues to have more programmers than software testers. There simply are not enough testers to specialize as thoroughly as the programmers, which leads managers and executives scrambling to find a support, or rather an enablement model for the testing group. Learn how to effectively organize your test teams and how to determine the right model for your organization.
-
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 Dave Snowden on Leadership and Using Cynefin for Capturing Requirements
Dave Snowden gave a talk titled "Context is Everything" at the Scaling Agile for the Enterprise 2016 congress in Brussels, Belgium. InfoQ interviewed him about applying leadership models, the Cynefin model and how it can be used for capturing requirements, scaling agile, and sustainable change.
-
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.
-
Build Your Own Offshore Development Team - or Not?
When you absolutely positively MUST build your own offshore dev team to get the quality you need, consider NOT. There is an argument for ‘owning’ vs ‘renting’ when it comes to leveraging an offshore dev team, the author disagrees with the idea that building one’s own team is better than outsourcing the job. He knows what it takes to do it right, and it isn't easy.
-
Test Management Revisited
The concept of test management sits awkwardly in agile, mostly because it’s a construct derived from the time when testing was a post-development phase, performed by independent testing teams. Agile, with its focus on cross functional teams, has sounded the death knell for many test managers. While test management is largely irrelevant in agile, there is still a desperate need for test leadership.