# Noter til Agile estimating - BSUP ###### tags: `BSUP`, `Agile estimating` ## What is agile planning? ![](https://i.imgur.com/9ZYk6pc.png) #### Estimate size; derive duration ![](https://i.imgur.com/tvUyBDX.png) #### Measures of size ![](https://i.imgur.com/GDg8Nin.png) ### Story points * How long a user story will take (effort) * Influenced by complexity, uncertainty, risk, volume of work, etc. * Relative values are what is important: * A login screen is a 2. * A search feature is an 8. * Basic math properties should hold * 5+5 = 10 ### Ideal time How long something will take if: * it’s all you work on * no one interrupts you * and everything you need is available #### Elapsed time versus ideal time ![](https://i.imgur.com/9i2wUjI.png) #### Two big advantages to story points 1. Story points are additive; time-based estimate may not be 2. Story points help avoid problems with unit confusion #### Confusing units ![](https://i.imgur.com/hxagRfV.png) ![](https://i.imgur.com/ErpBDLy.png) ## Estimating with Planning Poker * An iterative approach to estimating * Steps * Each estimator is given a deck of cards, each card has a valid estimate written on it * Customer/Product owner reads a story and it is discussed briefly * Each estimator selects a card that is his or her estimate * Cards are turned at the same time * Discuss differences (especially outliers) * Re-estimate until estimates converge ### Planning Poker - an example ![](https://i.imgur.com/v9RFlQ4.png)