Planning Poker

Agile teams often struggle to estimate product backlog items. Here are 7 ways to make solid improvements.

If you’ve estimated with Planning Poker, you may very well have used cards with either the …

Triangulating estimates happens when teams compare a current estimate against two existing …

Even though not everyone may work on a product backlog item, it’s still worth having the full team …

Planning Poker relies on relative estimating, in which the item being estimated is compared to one …

A rose by any other name may smell as sweet, but a five-point story better not go by any other …

I'm occasionally asked about the merits (and whether there are any) of putting an estimate of zero …

It is good practice to first write large user stories (commonly known as epics) and then to split …

I recommend using Planning Poker on product backlog items rather than on the tasks that make up a …

All of a Scrum team’s members should be present when playing Planning Poker. You may be tempted to …

In this session we will shatter the myth that agile teams can't plan. We'll start by looking at the …

Too many teams view planning as something to be avoided, and too many organizations view plans as …

You’ve probably heard some people say, “Agile teams don’t plan.” Nothing could be further from the …

Maybe you’ve heard about agile software development projects but aren’t sure if they allow for the …

Removing the large values from a deck of Planning Poker cards is like deciding to strike millions …

Some teams may respond to the pressure for their abstract measure of velocity to increase by …

A common criticism of story points is that the meaning of a story point will differ among teams.

While I want teams to come to agreement, I don't care how heartfelt the agreement is.