InfoQ Homepage Product Backlog Content on InfoQ
Articles
RSS Feed-
/articles/book-review-risk-free-software-development/en/smallimage/infoq-risk-first-software-development-cover-1560550499019.jpg)
Q&A on the Book Risk-First Software Development
The book Risk-First Software Development by Rob Moffat views all of the activities on a software project through the lens of managing risk. It introduces a pattern language to classify different risks, provides suggestions for balancing risks, and explores how software methodologies view risks.
-
/articles/book-business-analysis-agility/en/smallimage/business-agility-cover-small-1550401830756.jpg)
Author Q&A on the Book Business Analysis Agility
James and Suzanne Robertson have written a book titled Business Analysis Agility - Solve the Real Problem, Deliver Real Value. They address the fact that despite the adoption of agile approaches a lot of time, effort and money is wasted building the wrong product. They explore the challenges faced undertaking analysis in agile environments and address some of the common mistakes.
-
/articles/product-roadmap-meeting-needs/en/smallimage/map-1528700845386.jpeg)
Is Your Product Roadmap Still Meeting Customer Needs?
It’s difficult to overestimate the importance of having a strong vision for the product. However, that vision must be frequently and consistently kept in line with the needs of the customer. In this article, Justin explores how to tell if your product roadmap still meets your customers' needs.
-
/articles/strategy-handling-defects/en/smallimage/agile-logo.jpg)
Now or Never: the Ultimate Strategy for Handling Defects
How do you handle a long list of defects in your project? You don't. If it is not worth fixing a defect right now, it’s not likely that we will find the time to do it later. Also, it becomes more and more difficult over time to correct the defect, so it is cheaper to solve it now. Kirill Klimov explains why you should solve defects right away, or state that you will not solve them.
-
/articles/use-case-20-slices-Dutch-Railways/en/smallimage/logo-agile.jpg)
Keeping Development ‘On Track’ with Use-Case Slices at Dutch Railways
How can you get from high level system requirements (features/epics) to the right level of specification to enable agile development? This article describes how Dutch Railways made the transition from large use cases which were completely written before development, to “Use Case 2.0” and why this helps them to deliver apps faster and with the right business value.
-
/articles/downscaling-SAFe/en/smallimage/logo2.jpg)
Downscaling SAFe
The Scaled Agile Framework (SAFe) with custom modifications to it in accordance with Agile and Lean values helped Seamless Payments to go through a period of organizational growth and prepare for further growth. This article describes the change that was done using a slimmed down version of SAFe that still maintained its core ideas.
-
/articles/quality-hierarchy-needs/en/smallimage/logo-agile.jpg)
The Hierarchy of Needs
What may be valuable to customers whom you do not even know in an unstructured and completely individualized market? This article suggests prioritizing your backlog using an enhanced quality model based on Maslow’s hierarchy of human needs. Search for most valuable features using the Need-Feature-Capability matrix and give those features highest priority in your backlog.
-
/articles/project-to-product-agfa-less/en/smallimage/logo3.jpg)
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.