InfoQ Homepage Agile 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.
-
Product Development Mechanisms
Steve Andrews discuses the need to empower self-managing teams to stay focused on delivering high-quality solutions using mechanisms like tenets and exit criteria.
-
A Letter to the Manager: Release the Power of Your Agile Teams
Agile is both simple and hard – and success depends on managers creating a suitable environment for their teams. Here a coach’s experiences from several agile transformations are made into concrete recommendations for strengthening agile teams. To create and sustain high-performing agile teams, these points are fundamental.
-
Johanna Rothman on Agile and Lean Program Management
Johanna Rothman explores how to scale lean and agile processes to work in large programs in her book - Agile and Lean Program Management: Scaling Collaboration Across the Organization. It explains how to collaborate across the organization to create and steer an adaptive, resilient program.
-
Q&A with Roman Pichler about Strategize
The book Strategize by Roman Pichler provides practices, advice, and examples for product strategy and roadmapping that you can use to create successful products. InfoQ interviewed Pichler about applying product strategy and roadmapping with agile, innovation in product strategy, eliminating features when defining products, different kinds of roadmaps, and measurements for product management.
-
Configure Once, Run Everywhere: Decoupling Configuration and Runtime
Configuration is one of the most widely used cross-cutting concerns in application development. Apache Tamaya is a new incubator project that brings standardized property management to Java.
-
Q&A with Johanna Rothman and Jutta Eckstein on Cost of Delay
The book Diving For Hidden Treasures - Uncovering the Cost of Delay in Your Project Portfolio by Johanna Rothman and Jutta Eckstein explores how projects become delayed and provides tools and methods to analyze and limit the costs of delay in projects.
-
An Organization Development(OD) Approach to Agile Adoption
Is there an approach that can make Agile adoption successful at a systemic level, and not remain just an engineering practice? Organization Development (OD) is an interdisciplinary field of research, theory and practices. It has the right methods for organizations to become organic entities, to implement learning systems, empower teams to become self-organized and reduce resistance to change.
-
Pair Programming Is No Panacea
Is pair programming all that it's cracked up to be? Contrary to popular belief, pairing can lead to a decrease in creativity, groupthink, inappropriate feedback, and can be demoralizing. Wes Higbee explores why it definitely shouldn't be mandated, and why you should consider other options where it could be beneficial.
-
User Stories Are Placeholders for Requirements
It can be difficult to change from a Waterfall approach where ‘business analysts write big requirements up front’ to the Agile practice in which requirements are prepared ‘just in time’, and are the responsibility of the entire team. The secret to success in Agile is ruthless management of scope.
-
Using SEMAT and Essence at Fujitsu UK
Fujitsu UK is using a large number of processes and methods which have developed over the period of many years. Looking for a way of combining agile and traditional methods, they became aware of SEMAT and the Essence Kernel. This article explores how they applied SEMAT and Essence to systems engineering, and used it to look at the whole programme of work across all disciplines.