How to use story-points, velocity, and the cone of uncertainty to deliver in time

Estimating a story in hours is common practice. But often, estimations in hours prove not to be accurate. How much time it takes to complete a task depends on a lot of variables. There’s a better way. Estimating stories by size rather than the time needed to complete it, results in more reliable planning, and allows the team to respond when their pace slows down.

It’s easy to estimate the number of hours it takes to complete a task. Everybody can do it. It might even be the easiest way to…

--

--

--

software developer / consultant @ vxcompany.com

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Firebase Crashlytics in Android

Extension Integrations Create Better Process Flow

Static website using AWS S3 — Easy & Affordable

Static Website using AWS S3–6 Steps Simple Guide

A brief info on Threads in Linux

Using MFA with AWS using Python and boto3

Vector Application Icon for Android — A Complete Guide.

[LeetCode]#824. Goat Latin

[LeetCode]#1470. Shuffle the Array

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Albert Starreveld

Albert Starreveld

software developer / consultant @ vxcompany.com

More from Medium

Scrum vs. Kanban = ScrumBan?

Scrum: Adaptive Software Development

What is Zombie Scrum?

How to Pass the Professional Scrum Master II Certification the First Time Around