SAFe™ (The Scaled Agile Framework) uses Story Points throughout the various levels as its estimation currency. This is covered in the 'Story' article on the SAFe site. This is a pretty standard practice in organizations scaling agile these days. If you dive a bit deeper into how this is done in SAFe you will see that actually the story points used in SAFe are quite similar to 'Ideal Developer Day' as this helps the teams align to a common baseline and support a rational economic ROI discussion at the level of Features/Capabilities that require effort from more than one team or haven't even been mapped to a specific team yet.
- Planning Poker is a consensus-based technique for estimation, mostly used to estimate effort or relative size of development goals in software product development. Planning Poker is done with story points, ideal days, or any other estimating units. The Scrum Master, Product Owner, and the development team participate in Planning Poker activity.
- Planning Poker is a team building activity for achieving group consensus. It is used by agile software development teams to estimate how long a certain amount of work will take to complete.
An alternative to using Story Points at the team level that is interesting to look at especially as Kanban is becoming a first-class citizen of the SAFe world is to use NoEstimates.
Poker Planning Approach Definition
Planning poker (also known as Scrum poker) is a consensus-based, gamified technique for estimating, mostly used to estimate effort or relative size of development goals in software development. Planning Poker is an estimation technique and like all estimate providing sessions, should be held before the iteration/sprint starts. The user stories can be picked up from the backlog issues and pre- selected before the Planning poker meeting.
In essence this means not trying to estimate the size of the work just slice work into a size that we can bite on and turn around quickly. To get a quick grasp of it think of replacing your classic fibonacci planning poker cards with a set of cards saying 1, TFB (Too Frighteningly Big), NFC (No Faintest Clue). This approach is rising in popularity among Kanban/ScrumBan practitioners – We've been looking at the 'Iteration Planning' process for years trying to address some of its wastes/tensions.
Online poker freeroll schedule. This 'No Estimates' inspired approach to story estimation in PI Planning has a couple of benefits:
- It is faster – which comes in handy during PI Planning.
- It forces teams to slice into smaller stories which is better.
- It is naturally easier to baseline/align multiple teams around the same definition. (BTW a 1 here would be something like a 3 or 5 in the classic SAFe velocity calculation – a story that takes the team about 3 days to develop and 3 days to test)
Iteration Planning becomes even easier – Just understand your velocity and how many stories you can fit. New casino near albany ny. Minimal time is spent estimating.
Planning Poker Approach
Iteration Planning becomes even easier – Just understand your velocity and how many stories you can fit. New casino near albany ny. Minimal time is spent estimating.
Planning Poker Approach
There are a couple of challenges though. Forcing the team to split their whole Feature into small 1-size stories including those that are only going to be pulled in later iterations in the PI might be a waste of time.
Poker Planning Approach Strategies
Another challenge is how to make rational economic decisions at the Feature/Capability and even Epic level without estimates. #NoEstimates die-hards say it doesn't make sense to estimate even at this level, not just the stories level. I'm not convinced. What I typically do in cases where teams stop estimating story sizes is just use story counts as the currency at the higher levels. So instead of saying 'This seems to be a 20 Story Points Feature' we would say 'This Feature seems to be something around 20 stories' meaning we ESTIMATE it will map to about 20 stories when we eventually slice it. We DON'T slice it to stories in order to estimate. We reach that estimation using a classic relative estimate approach like Planning Poker / Team Estimation Game. This is actually something that helps with the first challenge as well. Knowing that we're dealing with a Feature that we think has about 20 stories and that we identified 7 stories for the first iteration and 4 stories for the second , we might say something like there are around 9 stories more for the third iteration or even better – let's look at the remaining chunk and compare that to our feature estimation scale and see how many stories we think there are there.
Of course, if we think there are dragons (a.k.a dependencies) hidden in this remaining chunk we should make the effort to slice it into smaller stories and work out the dependencies/scheduling with the other teams on the train.
Stalker shadow of chernobyl poster. I've done this with clients in the trenches. Based on this experience, I consider this alternative approach to estimation a legitimate alternative to Story Points estimation at the SAFe Team Level.
This blog post was originally posted on Yuval's personal blog back in 2016.
Card Features
- Enough cards for four estimators in each deck.
- Casino quality, linen finish, two-ply cards. The finest available.
- Each deck includes a full suit of cards (?, 0, 1/2, 1, 2, 3, 5, 8, 13, 20, 40, 100, infinity) in each of four colors.
- Professional photos on the back of all cards.
- Each deck comes in a matching box for years of use.
- Accept no imitation; use the cards used by tens of thousands of developers around the world.
How to Play
Planning Poker® combines expert opinion, analogy, and disaggregation into an enjoyable approach to estimating that results in quick but reliable estimates.
Participants in Planning Poker® estimating include all of the developers on the team. Remember that developers refers to all programmers, testers, database engineers, analysts, user interaction designers, and so on. On an agile project, this will typically not exceed ten people. If it does, it is usually best to split into two teams. Each team can then estimate independently, which will keep the size down. The product owner participates in planning poker but does not estimate.
Testimonials
Fast and friendly service. We have used the cards extensively and they are holding up well as you would expect with high quality cards. If they every wear out, we will definitely order from Mountain Goat again.
—Chad Chatfield, VP, Software Engineering, Springbok Services
