Remove about-us
article thumbnail

Sprint Estimation: A Guide to Planning in Scrum

Scrum.org

Estimating what can be delivered in a single Sprint is a question that stumps many Scrum teams. We start with a simple premise: the Scrum Guide, a compass for many, surprisingly, doesn't mention 'estimates' but talks about 'size'. It's about making educated guesses, setting targeted Sprint goals, and staying flexible.

Estimate 152
article thumbnail

Ask a PM: How to Get Proper Estimates

LiquidPlanner

We do a lot of projects that are innovative (for us), and my development colleagues always seem reluctant when it comes to project planning. They won’t give me timescales that will help me plan. How do you deal with a team that refuses to estimate how long tasks will take? I’m getting tired of hearing, “It depends.”

Estimate 602
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

How We Chose the Perfect Planning Poker Tool

Rebel’s Guide to PM

Planning poker® is a great technique for scrum teams. It is a team-based estimating approach to work out the efforts involved for achieving business goals. We use planning poker with these teams and as there are a lot of products to choose from, we spent some time testing different ones to find the perfect match.

Planning 383
article thumbnail

Rough Order of Magnitude (ROM) Estimate and How to Calculate It (with example)

Rebel’s Guide to PM

What is a ROM estimate used for? A rough order of magnitude estimate is used to give you a very high level view of potential project costs. Ideally, you’d be able to provide a definitive estimate, carefully created from loads of input from subject matter experts and plenty of research on past projects and their budgets.

Estimate 459
article thumbnail

Thinking By Sprinting: What Cognitive Science Tells Us About Why Scrum Works

Scrum.org

Listen to us read this blogpost in our podcast “The Liberators Network”. Implementing a single feature in a product is often complex because it requires many assumptions about what the users like and understand, how to best use technology to make the feature possible and how skilled the people implementing it are.

2002 192
article thumbnail

Estimates Are Useful, Just Ditch the Numbers

Scrum.org

TL; DR: Estimates Are Useful, Just Ditch the Numbers. Many people dislike estimating work items as estimates supposedly open the path to the misuse of velocity by the managers, reintroducing Taylorism, micro-management, and excessive reporting through the backdoor. Shall I notify you about articles like this one?

Estimate 204
article thumbnail

The False Sense of Security of Release Plans

Scrum.org

I have spent a lot of my and the team's time creating release plans. Release plans that: Show dates around when features will be done Show dates we plan on iteratively releasing through the course of the next month, quarter, and/or year. All the while, I knew these release plans to be entirely made up.

Planning 162