---
# System prepended metadata

title: Noter til Advanced topics in agile planning - BSUP
tags: [Advanced topics in agile planning, BSUP]

---

# Noter til Advanced topics in agile planning - BSUP
###### tags: `BSUP`, `Advanced topics in agile planning`

## The planning onion
![](https://i.imgur.com/LPxCRZE.png)

## Release and sprint planning 
![](https://i.imgur.com/ITFAeMk.png)

## What is a good plan?
![](https://i.imgur.com/Ybu2LWH.png)

## Velocity
![](https://i.imgur.com/5a3TQWa.png)

![](https://i.imgur.com/RL0IcO5.png)

- A useful long-term measure of the amount of work completed per iteration
- Most useful over at least a handful of iterations

## Five planning scenarios 
### A team with historical data
#### Calculate a confidence interval form historical data
![](https://i.imgur.com/YYZONhW.png)

#### Extrapolate from the velocity range
![](https://i.imgur.com/2MzUDxU.png)

![](https://i.imgur.com/RFtkxcO.png)

Use the online velocity calculator at
- mountaingoatsoftware.com/tools

### Fixed-date plans
#### Fixed-date planning
![](https://i.imgur.com/YxKeMS2.png)

#### Count the sprints
![](https://i.imgur.com/jRpJC0B.png)

#### Determine a velocity range
![](https://i.imgur.com/r3VJGnT.png)

![](https://i.imgur.com/ZMw9tlu.png)

#### Determine what to commit to
![](https://i.imgur.com/5z8sHcS.png)

#### Balacing risk
![](https://i.imgur.com/aVzK6wq.png)

### Fixed-scope plans
#### Fixed-scope planning
![](https://i.imgur.com/tftZ7L3.png)

![](https://i.imgur.com/EGTVzOW.jpg)

![](https://i.imgur.com/KuV6vj7.png)

#### Ranges
- Notice in both cases we had a range
- For a **fixed-date project**, use a scope range:
    - “By that date you will have all of these features and some of these.”
- For a **fixed-scope project**, use a date range:
    - “It will take use between 6 and 8 sprints to deliver all those features.”

#### Past velocities
![](https://i.imgur.com/lzmaYof.png)

![](https://i.imgur.com/VAtCiRw.png)


### A team with no velocity data
#### Forecast an initial velocity
* Get the team together as though there were going to plan a real sprint (2–4 weeks)
* Sprint planning involves
    * Breaking product backlog items (features) into tasks
    * Estimating the hours for each task
    * Repeating until the sprint feels full
* See how many points are represented by the work they selected
* Consider planning a second iteration in this way

#### Consider this team
![](https://i.imgur.com/ScN4r7z.png)

#### Establishing their velocity 
![](https://i.imgur.com/hsSj1Bc.png)

#### Turn the point estimaste into a range
* If you do not have historical data
    * Take a wild guess, perhaps:
        * +/- 10% for a known team working together in a known application domain with known technologies
        * +/- 50% if all that is unknown
* If you have historical data from other teams
    * Calculate the relative standard deviation of those teams

#### Using data from other teams
![](https://i.imgur.com/ekZeMKl.png)

![](https://i.imgur.com/NxEVIQI.png)


### A team changing size
#### Track velocity when size changes
![](https://i.imgur.com/lChhHA1.png)

#### Impact of going from 6 to 7 people
![](https://i.imgur.com/qBmOG7Y.png)
