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

A/B testing is a way to compare two versions of something to figure out which performs better. While it’s most often associated with websites and apps, the method is almost 100 years old and it’s one of the simplest forms of a randomized controlled experiment. This testing method has risen in popularity over the last couple of decades as companies have realized that the online environment is well-suited to help managers, especially marketers, answer questions like, “What is most likely to make people click? Or buy our product? Or register with our site?”. It’s now used to evaluate everything from website design to online offers to headlines to product descriptions. The test works by showing two sets of users (assigned at random when they visit the site) different versions of a product or site and then determining which influenced your success metric the most. While it’s an often-used method, there are several mistakes that managers make when doing A/B testing: reacting to early data without letting the test run its full course; looking at too many metrics instead of focusing on the ones they most care about; and not doing enough retesting to be sure they didn’t get false positive results.

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

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.

Scrum teams estimate both product backlog items and sprint user stories--but in distinct units and at separate times.

Become a Cucumber expert at your own pace with free online courses. Attend interactive in-person training, tailored for your needs. Learn more and get started.

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.

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...

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

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

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

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

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.

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

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.

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

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.

Disclaimer: The content in this article is a mix from the references linked below and my personal experience. It is not meant to be an…