Issue Summary

Path: JA > Admin > Settings > Platform > Team "Velocity Range (+ or -):"

Current description in "i" box and JA Help is: "This setting controls a built in metric to show teams what the desired velocity variability should be to drive better predictability."

Matt Magee and I reviewed this definition and determined that it is incorrect. It was submitted as an enhancement for 2Chainz's sprint planning, but I was asked to submit it as a defect.

We recommend this language: "This number is a percentage of total points. It directly affects the distribution/range of the pessimistic, predicted, and optimistic forecast lines users see in Program Increment Progress reports under <bold>Drill Down</bold>. These lines help portfolio and program leaders create a high-level forecast based upon teams' velocity variability."

Why this matters: This functionality drives users' ability to accurately forecast work completion, as well as planning using either a) empirical knowledge; i.e. a range based upon collected, and/or b) hypothetical scenarios; i.e. range is a risk mgmt tool for planning contingencies.

Reminder: The definition needs to be changed in both the system and the JA Help material.

Steps to Reproduce

1. Step 1 - This is a documentation update approved by prod management and the SA team

Expected Results

We recommend this language: "This number is a percentage of total points. It directly affects the distribution/range of the pessimistic, predicted, and optimistic forecast lines users see in Program Increment Progress reports under <bold>Drill Down</bold>. These lines help portfolio and program leaders create a high-level forecast based upon teams' velocity variability."

Why this matters: This functionality drives users' ability to accurately forecast work completion, as well as planning using either a) empirical knowledge; i.e. a range based upon collected, and/or b) hypothetical scenarios; i.e. range is a risk mgmt tool for planning contingencies.

Reminder: The definition needs to be changed in both the system and the JA Help material.

Actual Results

See screenshot 

Workaround

None