InfoQ Homepage Agile Content on InfoQ
-
Implementing Agile Delivery for Non-Software IT Projects
Most organizations avoid using Agile for IT projects that do not involve software delivery (e.g. roadmap planning and architecture development). These projects deliver high value, but are often the most risky of all projects - and high risk demands Agile delivery. This paper discusses how Agile can be successfully adopted to deliver these projects by going back to the basics of Agile philosophy.
-
Lessons Learned Adopting Microservices at Gilt, Hailo and nearForm
This article contains an extensive interview on the microservices adoption process, the technologies used, the benefits and difficulties of implementing microservices, with representatives from Gilt, Hailo and nearForm.
-
Q&A with Ron Jeffries on The Nature of Software Development.
The book "the nature of software development" intents to help people to organize their thoughts about value and find ways to deliver value in software development. It's a book of questions, not of answers, says author Ron Jeffries, for readers to discover the natural way to develop software, the simple way, inside themselves.
-
Business, Design and Technology: Joining Forces for a Truly Competitive Advantage
The list of industries being disrupted by digital technologies is growing. To embrace this new digital world, companies need to change their practices and the way they use technology.
-
User Story Driven Docs
At OutSystems we stopped trying to document the UI and started doing user story driven documentation. In this article I'll tell you why you should avoid document the UI, and how to check if you're already doing it. I'll also tell you how focusing on user stories changed our team's culture, and the process we're currently using to create documentation for OutSystems Platform.
-
From a Project to a Product Approach Using LeSS at Agfa Healthcare
By changing the inner workings from a project perspective to a product perspective Agfa Healthcare established a less complicated process using a single backlog for the entire organisation. Main advice is to try to avoid setting up silos where they do not belong. When applying LeSS it is important to stick to its basic rules even though they are, in most organisations, very disruptive.
-
An Agile Input Management Process Framework - The Agile IMP
Agile methods and processes such as Scrum give us conceptual tools to implement our innovative ideas. But that toolset seems to miss a crucial part: A well-structured ideas development process. The Agile IMP (Input Management Process) proposes a conceptual framework for managing input from multiple sources, for maturing input and for basing product decisions on soundly evaluated propositions.
-
DevOps & Product Teams - Win or Fail?
Peter Neumark found a new world when he moved from a DevOps infrastructure team to a Lean product team.How to experiment frequently while keeping operational performance? Platform teams to the rescue!
-
The Pitfalls that You Should Always Avoid when Implementing Agile
Moving from traditional project management to agile is a paradigm shift. From push to pull systems from a control-and-command culture to a trust culture where authority is delegated. A good structure with some control mechanisms will most likely help you get the wanted results quicker. This article discusses the role that management plays in organizations that have decided to adopt agile.
-
Q&A with Paul Swartout on the Evolution of Continuous Delivery and DevOps
InfoQ reached out to "Continuous Delivery and DevOps: A Quickstart Guide" book author Paul Swartout in order to find out what have been the major changes in this space (and in the book) in the last couple of years. Swartout shares his view on cultural challenges to DevOps adoption and how the rise of mobile and microservices impacts Continuous Delivery approaches, among other topics.
-
Q&A on Fifty Quick Ideas to Improve Your Tests
An interview with Gojko Adzic, David Evans and Tom Roden on why they wrote this book, how quantifying quality can support testing, balancing trust levels when testing large and complex systems, why automating manual tests is almost always a bad idea, on using production metrics in testing, how to reduce or prevent duplication in test code, and on upcoming books in the fifty quick ideas series.
-
Probabilistic Project Planning Using Little’s Law
When working on projects, it is most of the time necessary to forecast the project delivery time up front. Little’s Law can help any team that uses user stories for planning and tracking project execution no matter what development process it uses. We use a project buffer to manage the inherent uncertainty associated with planning and executing a fixed-bid project and protect its delivery date.