Product Backlog Management

Within systems engineering, quality attributes are realized non-functional requirements used to evaluate the performance of a system. These are sometimes named architecture characteristics, or "ilities" after the suffix many of the words share. They are usually architecturally significant requirements that require architects' attention.[1]

The MoSCoW method is a prioritization framework used to help key stakeholders understand the significance of initiatives in a release.

Having a Definition of Ready means that stories must be immediately actionable. The Team must be able to determine what needs to be done and the amount of work required to complete the User Story or PBI.

When I recently asked a room full of people “What is the difference between Acceptance Criteria and Conditions of Satisfaction?”, I expected definitions

Good acceptance criteria will help get your agile development project from “It Works as Coded” to “It Works as Intended.”

This is RonJeffries.com, the combination of new articles, XProgramming, SameElephant, and perhaps even some new items never before contemplated. Copyright © 1998-forever Ronald E Jeffries

Writing good user stories can be hard, however these ten tips will help you create powerful stories that direct product delivery.

XP teams have to manage stories and tasks. The INVEST and SMART acronyms can remind teams of the good characteristics of each.

In Scrum, the Prioritized Product Backlog is a single requirements document that defines the project scope by providing a prioritized list of features of t...

In the past, the Scrum Guide consistently used the word "priority" for the Product Backlog or noted that the Product Backlog was “prioritized.” While the Product Backlog must be ordered, ordering by priority is only one many techniques — and rarely the best one at that.

The Scrum Guide talks about an ordered backlog, not a prioritized one. While order and priority are related, they are not the same, and understanding the difference and why people focus on one over the other can help your team be more effective at delivering business value.

The planning fallacy leads us to underestimate how much time it will take us to complete tasks. To avoid the problem, adopt one of these estimation techniques.

Poker planning is an agile estimating and planning exercise that uses Planning Poker cards for consensus-based estimating in Scrum.

Some agile teams estimate using a fixed set of values based on the Fibonacci sequence. Learn the science behind this approach and why it works so well.

Estimate inflation is when the estimate assigned to a product backlog item (usually a user story) increases over time. Triangulating prevents this.