InfoQ Homepage Agile Content on InfoQ
-
So, How Do You Make Agile Successful?
It is not Agile's fault, it is your fault - Are you fed up with such statements? This article tries to provide a more constructive answer on how to make Agile successful. It first shows how Scrum can be harmful, then argues how Agile requires different skills on both product and delivery levels. It suggests to use CICD to counteract Scrum's traps and stresses the importance of systems thinking.
-
WTF requirements in Agile Product Development
The use of all-conclusive, hard-defined, non-negotiable BRDs is not appropriate in agile development. It will lead to an array of dysfunctions, including Local Optimization, deterioration of relationships between Product Owners and Feature Teams as well as loss of trust by end-customers. A refined, well-prioritized Product Backlog is the right place to store requirements in agile development.
-
Waterfall Requirements in Agile Product Development
The use of all-conclusive, hard-defined, non-negotiable BRDs is not appropriate in agile development. It will lead to an array of dysfunctions, including Local Optimization, deterioration of relationships between Product Owners and Feature Teams as well as loss of trust by end-customers. A refined, well-prioritized Product Backlog is the right place to store requirements in agile development.
-
Iterative Prototyping in the Mobile App Development Process
Mobile app development adopted an iterative, rapid development process and prototypes have a role to play in this agile approach, enabling developers to build, test, iterate, re-test and re-build rapidly and at lower cost (not to mention allowing all stakeholders in the process early on). This article guides through the essential steps of mobile app prototyping.
-
Q&A with Jason Fox on How to Lead a Quest
In the book How to Lead a Quest Jason Fox explores what can be done to develop insights for strategic decisions and innovation, and for driving progress and delivering value. The book provides approaches and rituals for asking deeper, bigger questions and slow, thorough thinking, creating options and designing experiments for dealing with complexity, ambiguity and uncertainty.
-
Growing Agile… Not Scaling!
What makes an agile team successful is not the “process” nor the “tools” but rather the way people develop an effective level of interaction with each other. Growing agile means both focusing on culture, and on co-evolution of practices and tools.
-
How to Deal with COTS Products in a DevOps World
Mirco Hering explains why we shouldn't leave COTS products (and the people working on them) left behind in a DevOps world. With creative solutions we can apply good practices from custom software. This leads to a significant effort reduction in the long term.
-
Containers Live Migration: Behind the Scenes
This article addresses a topic that is not fully covered in current IT world: live migration of containers, how it works behind the scenes, and what problems it solves. The demand for this technology is growing as it unlocks new possibilities by giving more freedom in application lifecycle management.
-
Q&A with Jurgen Appelo on Managing for Happiness
The book Managing for Happiness by Jurgen Appelo provides practices, games and tools to manage organizations and make work fun. It contains tips and suggestions for applying the practices to achieve organizational greatness and maximize learning in organizations.
-
Why ALM Is Becoming Indispensable in Safety-Critical Product Development
Integrated Application Lifecycle Management platforms are advancing product development in life and safety critical environments. The story of how Medtronic Neuromodulation were able to modernize their processes using ALM helps us understand current and future trends in the development of complex software-heavy products.
-
Don't Break Your Silos - Push Out the Silo Mentality
Organizational silos are a serious hurdle for many companies out there. They may cause a wide variety of problems if not dealt with accordingly. Silos may not need to be broken if you manage to push out the mentality that comes with them by creating ventilators. The first step towards dealing with the silos is to learn more about them and familiarize yourself with the best practices against them.
-
Writing Maintainable Configuration Code
The article discusses a catalog of configuration smells containing 13 implementation configuration smells and 11 design configuration smells. It provides a few examples of configuration smells along with corresponding refactorings, explains their impact on the quality of the project, and lists a few tools that could be used to reveal such smells.