InfoQ Homepage Agile Content on InfoQ
-
/articles/flow-debt/en/smallimage/Flow-Debt-InfoQ.jpg)
Proper Usage of Metrics with Flow Debt as an Example
Flow Debt is a leading indicator that provides a view of what is happening inside a delivery system; an important metric for improving software development. This article provides an example how a metric like Flow Debt can be used improperly, i.e. out of their domain, or properly, i.e. context aware usage of Flow Debt with an IT operations team.
-
/articles/feature-flags-gone-wrong/en/smallimage/devops-logo.jpg)
When Feature Flags Go Wrong
Feature flags can superpower development, allowing faster features. But they can also be the worst kind of technical debt if misused or mismanaged. This article walks us through some horror stories of feature flags gone bad, and lessons learned.
-
/articles/standardize-requirements-scrum/en/smallimage/logo-agile.jpg)
Standardizing Requirements Descriptions on Scrum Projects for Better Development and Testing Quality
Standardizing requirements descriptions on Scrum projects benefit development and testing quality. Without standardizing, the project may suffer. Standardizing requirements descriptions provides a minimum of eight benefits from requirements descriptions unification, which in turn positively affects testing and makes management of ongoing changes in requirements easier with the help of tools.
-
/articles/agile-UK-government/en/smallimage/654711575.jpg)
Agile in the UK Government - An Insider Reveals All
The Government Digital Service (GDS) aims to transform the relationship between citizen and state, moving the UK towards becoming a world-leading digital-by-default government. Nick Tune explores what GDS has achieved with assessments, sharing agile practices and experiences, and open source software, and shares what isn’t working so well in government IT.
-
/articles/top5-problems-distributed/en/smallimage/logo-remote.jpg)
The Top 5 Problems with Distributed Teams and How to Solve Them
In this article, Hugo Messer shares the top 5 challenges distributed teams face along with practical solutions. They are based on his 6 books, many workshops and a decade of hands on experience. The top 5 challenges: 1. We're thinking 'us versus them'; 2. Keeping the team in the dark; 3. Culture is a mystery; 4. We stop communicating; 5. The black box.
-
/articles/communities-of-practice-agile-organisation/en/smallimage/logo.jpg)
Communities of Practice: The Missing Piece of Your Agile Organisation
Communities of practice bring together people who share areas of interest or concerns. They have specific applications in agile organisations: scaling agile development and allowing individuals to connect with others who share similar concerns. Communities of practice bring people together to regain the benefits of regular contact while keeping the value of multidisciplinary agile teams.
-
/articles/book-review-liftoff-second-edition/en/smallimage/logo.jpg)
Q&A and Book Review on Liftoff, Second Edition
The book Liftoff, Second Edition by Diana Larsen and Ainsley Nies, provides practices and insights for chartering teams by understanding their needs, building trust, and defining how they will interact in the team and align with other parts of the organization. It's a book for Agile coaches, Scrum masters or agile product and project managers to help teams to understand the why behind the work.
-
/articles/sql-server-containers/en/smallimage/stanton-logo.jpg)
Introduction to SQL Server Containers
Containers are just around the corner for the Windows community, and this article takes a closer look at using SQL Server containers. The author discusses the value, use cases, and means for taking advantage of SQL Server containers today.
-
/articles/predictably-adaptable/en/smallimage/dimitar-logo.jpg)
Adaptable or Predictable? Strive for Both – Be Predictably Adaptable!
Our efforts to improve software development face the question of what to focus on. Should we govern for predictability without concern of value, maximizing cost-efficiency without concern for end-to-end responsiveness? Or maybe do the opposite and govern for value over predictability, focus on responsiveness over cost efficiency? What we really need is to be predictably adaptable.
-
/articles/agile2016-icagile-growth/en/smallimage/icagile-logo.jpg)
Agile 2016: Interview with ICAgile on Certification, Growth and Expert Tracks
At the recent Agile 2016 conference, ICAgile announced a number of milestones – more Certified Experts qualified, some additional certification pathways, and substantive growth in certified participants and member training organisations. Ahmed Sidky and Shannon Ewan discuss all of this with InfoQ and why the agile mindset is more important than any set of practices or techniques.
-
/articles/continuous-delivery-coding-patterns/en/smallimage/logo.jpg)
Continuous Delivery Coding Patterns: Latent-to-Live Code & Forward Compatible Interim Versions
This article describes two novel practices for continuous delivery: Latent-to-live code pattern and Forward compatible interim versions. You can use these practices to simultaneously increase speed and reliability of software development and reduce risks. These practices are built on top of two other essential continuous delivery practices: trunk-based-development and feature toggles.
-
/articles/technical-hack-conciousness/en/smallimage/logo.jpg)
Technical Practices as a Hack on Consciousness: Why to Hack Yourself
Software technical practices are usually adopted as a means of creating better products. These practices can create and maintain a healthy human system. Technical practices raise the consciousness of individuals and the team as a whole. Technical practices hack consciousness giving us a quick, deep chute into depths of connection that improve our selves, our products, and our world.