InfoQ Homepage Distributed Team Content on InfoQ
-
InfoQ at 10
We know that software is changing the world, and we’ve come to see our impact as accelerating the software side of that change. With that passion, we started InfoQ 10 years ago, in the context of some unusual beliefs and concerns.
-
A Reference Architecture for the Internet of Things (Part 2)
This is the second article of a two article series in which we try to work from the abstract level of IoT reference architectures towards the concrete architecture and implementation for selected use cases. This second article will show how to apply this architecture to real world use cases - one being in the field of smart homes, one in the field of insurance.
-
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 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.
-
A Focus on Agile Principles over Agile Rituals
When scaling agile principles through rituals it's important to constantly evaluate and evolve those rituals. This article provides examples of experiments that focus on the original intent when developing team behaviors. It shows how you can be aware of triggers that mean your team is not finding value in a ritual and what you can do to make things more visible.
-
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.
-
A Reference Architecture for the Internet of Things
This is the first article of a two article series in which we try to work from the abstract level of IoT reference architectures towards the concrete architecture and implementation for selected use cases. This first article will cover the definition of a more concrete and comprehensible architecture whereas the second part will then apply this architecture to actual use cases.