Capacity Planning and Estimation Units in Jira Alignment
Enterprise
Portfolio
Program
Team
Individual
Points
Hours (->MW)
Plan
Budgets
Identify
Epics
Build
3-PI
Roadmap
Plan the next
Quarter (PI)
Plan the
Sprint(s)
Plan
Tasks
Identify
Features
Estimation Units for demand from work items (and for capacity constraints)
Capacity Planning can occur at
each of these steps, performed by
the leadership at that level
Identify
Stories
Run:
Walk:
Crawl:
MW
MW
Hours (->MW)
Points
Points
Points
Points
Estimation System =
“MW/TW”
Estimation System =
“MW/TW”
Estimation System
= “Points”
Portfolio Configuration
Portfolio Epic
(Project)
Feature
(JIRA Epic)
Story
Task
To help portfolio
leadership to create
realistic roadmaps
To help program
leadership steer a
“reasonable”
amount of work to
the next PI (as
features)
To help team
leadership to plan
the sprints with a
consistent velocity
target
To help developers
show incremental
progress with hour-
based tasks
Member-Weeks per
Program per PI
(converted from
hours
estimates collected
outside JA)
Story points
Hours
After epic has been
accepted into
portfolio backlog
After feature has
been identified,
usually as part of a
Big Design Up Front
Epic owners, system
architects, and
program architects
Product managers,
working with
product architects
After story has been
placed into sprint
backlog
Product owners,
working with
developers
After sprint has
started
Developers
Forecast tab of the
epic
(or the Forecast
page directly)
Member Weeks field
on Detail tab of the
feature
N/A
– Points should be
entered in JIRA and
viewed as read-only in
Points field on the Story
in JA
N/A
– Hours should be
entered in JIRA and
viewed as read-only in
Hours field on the Task
in JA
From “Plan Capacity” button in Forecast
page
Team Velocity in points (per sprint) is
calculated automatically but can be
overridden from “Override” button in
Backlog->Viewing Stories> Kanban
Board:Column View
Team Velocity in Hours (per sprint) is
entered for the individual members of
the team from the Sprint object
Forecast
page
Backlog-
>Viewing
Stories>Kanban
Board: Column View)
Capacity Planning
page
To help portfolio
leadership to
anticipate cost and set
a target budget
Member Weeks
(converted from
hours
estimates, collected
outside JA)
After epic has been
pulled from the
funnel, with epic in
“Intake PI”
Epic owners
Member Weeks field
on Detail tab of the
epic
Portfolio Room:
Resources View
From “Plan Capacity” button in
Forecast page (against an Intake
program and Intake PI for the Portfolio)
Member Weeks
(converted from
hours
estimates, collected
outside JA)
MW->Pts is driven by Estimation
Conversions for Fibanocci settings [e.g. if 1
MW = 2.5 story points, then set 1 Fibonacci
FP = 0.067 TW
“Override” button in Backlog-> Viewing
Features-> Kanban Board:Column View
Program Room-
>
Program Increment
Load-> <gear>
Estimated
Estimation
Purpose
Estimation
Units
When
Estimate is
Captured
Who
Enters the
Estimate
Where to Enter
Demand
in Jira
Align
Where to Enter
Capacity
in Jira Align
Where Capacity
Planning is done
in Jira Align
Crawl
Work Item Level
To help portfolio
leadership to create
realistic roadmaps
To help program
leadership steer a
“reasonable”
amount of work to
the next PI (as
features)
To help team
leadership to plan
the sprints with a
consistent velocity
target
To help developers
show incremental
progress with hour
based tasks
Story points
Hours
After epic has been
accepted into
portfolio backlog
After feature has
been accepted into
program backlog
Epic owners, system
architects, and
program architects
Product managers,
working with
product architects
After story has been
accepted into sprint
backlog
Product owners,
working with
developers
After sprint has
started
Developers
Forecast tab of the
epic
(or the Forecast
page directly)
Member Weeks field
on Detail tab of the
feature
N/A
– Points should be
entered in JIRA and
viewed as read-only in
Points field on the Story
in JA
N/A
– Hours should be
entered in JIRA and
viewed as read-only in
Hours field on the Task
in JA
From “Plan Capacity” button in Forecast
page
Team Velocity in points (per sprint) is
calculated automatically but can be
overridden from “Override” button in
Backlog->Viewing Stories> Kanban
Board:Column View
Forecast
page
Backlog-
>Viewing
Stories>Kanban
Board: Column View
Capacity Planning
page
To help portfolio
leadership to
anticipate cost and set
a target budget
After epic has been
pulled from the
funnel, with epic in
“Intake PI”
Epic owners
Member Weeks field
on Detail tab of the
epic
Portfolio Room:
Resources View
– View
the sum of sizes
From “Plan Capacity” button in
Forecast page (against an Intake
program and Intake PI for the Portfolio)
Member Weeks
(converted from
team-
sprints
estimates,
collected outside JA)
Member-Weeks per
Program per PI
(converted from
team-
sprints
estimates
collected outside JA)
Member Weeks
(converted from
team-
sprints
estimates,
collected outside JA)
Program Room-
>
Program Increment
Load-> <gear>
Estimated
MW->Pts is driven by Estimation
Conversions for Fibanocci settings [e.g.
if 1 MW = 2.5 story points, then set 1
Fibonacci FP = 0.067 TW
“Override” button in Backlog-> Viewing
Features-> Kanban Board:Column View
To enable points-to-$ conversions,
Team Allocations in Hours (per sprint)
is entered for the individual members
of the team from the Sprint object
Estimation
Purpose
Estimation
Units
When
Estimate is
Captured
Who
Enters the
Estimate
Where to Enter
Demand
in Jira
Align
Where to Enter
Capacity
in Jira Align
Where Capacity
Planning is done
in Jira Align
Walk
Work Item Level
Portfolio Epic
Feature
(JIRA Epic)
Story
Task
Estimation
Purpose
Estimation
Units
When
Estimate is
Captured
Who
Enters the
Estimate
Where to Enter
Demand
in Jira
Align
Where to Enter
Capacity
in Jira Align
Where Capacity
Planning is done
in Jira Align
To help portfolio
leadership to
create realistic
roadmaps
To help program
leadership steer
a “reasonable”
amount of work
to the next PI (as
features)
To help team
leadership to
plan the sprints
with a consistent
velocity target
(Anticipated)
story points
per
Program
per PI
(Anticipated)
Story Points
Story points
After epic has
been accepted
into portfolio
backlog
After feature has
been accepted
into program
backlog
Epic owners,
system
architects, and
program
architects
Product
managers,
working with
product
architects
After story has
been accepted
into sprint
backlog
Product owners,
working with
developers
Forecast tab of
the epic
(or the Forecast
page directly)
Points field on
Detail tab of the
feature
N/A
– Points should
be entered in JIRA
and viewed as read-
only in Points field
on the Story in JA
Average Program Velocity (per PI)
is calculated automatically but
can be overridden from
“Override” button in Backlog-
>Viewing Features-> Kanban
Board:Column View
Team Velocity in points (per
sprint) is calculated automatically
but can be overridden from
“Override” button in Backlog-
>Viewing Stories> Kanban
Board:Column View
To enable points-to-$
conversions, Team Allocations in
Hours (per sprint) is entered for
the individual members of the
team from the Sprint object
Backlog-
>Viewing
Epics->Kanban
Board: Column View
Backlog-
>Viewing
Features>Kanban
Board: Column
View
Backlog-
>Viewing
Stories>Kanban
Board: Column
View)
Run
To help portfolio
leadership to
anticipate cost and
set a target budget
(Anticipated)
Story Points
After epic has
been pulled from
the funnel, with
epic in “Intake PI”
Epic owners
Points field on
Detail tab of the
epic
Portfolio Room:
Resources View
Average Program Velocity (per PI) is
calculated automatically but can be
overridden from “Override” button
in Backlog->Viewing Features->
Kanban Board:Column View
Average Program Velocity (per PI) is
calculated automatically but can be
overridden from “Override” button
in Backlog->Viewing Features->
Kanban Board:Column View
Work Item Level
N/A
N/A
N/A
N/A
N/A
N/A
Portfolio Epic
Feature
(JIRA Epic)
Story
Task
This detailed guide outlines the process of capacity planning and estimation units in Jira alignment, covering steps from entering demand to capturing estimates and planning sprints. It explains where and how to enter capacity and demand, who captures estimates, and the purpose of different estimation units. Additionally, it highlights how portfolio and program leadership can use these tools to anticipate costs, set budgets, and create realistic roadmaps.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
Estimation Units for demand from work items (and for capacity constraints) Portfolio Configuration Estimation System = MW/TW Points Crawl: Hours (->MW) Hours (->MW) Estimation System = MW/TW Points MW MW Walk: Estimation System = Points Points Points Points Run: Plan Budgets Enterprise Capacity Planning can occur at each of these steps, performed by the leadership at that level Identify Epics Portfolio Build 3-PI Roadmap Identify Features Plan the next Quarter (PI) Program Identify Stories Plan the Sprint(s) Team Plan Tasks Individual
Where Capacity Planning is done in Jira Align Where to Enter Demand in Jira Align Who When Estimate is Captured Crawl Where to Enter Capacity in Jira Align Estimation Purpose Estimation Units Enters the Estimate Work Item Level Member Weeks field on Detail tab of the epic Member Weeks (converted from hours estimates, collected outside JA) To help portfolio leadership to anticipate cost and set a target budget From Plan Capacity button in Forecast page (against an Intake program and Intake PI for the Portfolio) After epic has been pulled from the funnel, with epic in Intake PI Portfolio Room: Resources View Epic owners Portfolio Epic (Project) Member-Weeks per Program per PI (converted from hours estimates collected outside JA) Epic owners, system architects, and program architects After epic has been accepted into portfolio backlog From Plan Capacity button in Forecast page Forecast page To help portfolio leadership to create realistic roadmaps Forecast tab of the epic (or the Forecast page directly) To help program leadership steer a reasonable amount of work to the next PI (as features) Product managers, working with product architects Override button in Backlog-> Viewing Features-> Kanban Board:Column View Member Weeks field on Detail tab of the feature After feature has been identified, usually as part of a Big Design Up Front (JIRA Epic) Program Room-> Program Increment Load-> <gear> Estimated Member Weeks (converted from hours estimates, collected outside JA) Feature MW->Pts is driven by Estimation Conversions for Fibanocci settings [e.g. if 1 MW = 2.5 story points, then set 1 Fibonacci FP = 0.067 TW Team Velocity in points (per sprint) is calculated automatically but can be overridden from Override button in Backlog->Viewing Stories> Kanban Board:Column View To help team leadership to plan the sprints with a consistent velocity target Backlog->Viewing Stories>Kanban Board: Column View) After story has been placed into sprint backlog N/A Points should be entered in JIRA and viewed as read-only in Points field on the Story in JA Product owners, working with developers Story Story points N/A Hours should be entered in JIRA and viewed as read-only in Hours field on the Task in JA Team Velocity in Hours (per sprint) is entered for the individual members of the team from the Sprint object To help developers show incremental progress with hour- based tasks Task Capacity Planning page After sprint has started Developers Hours
Where Capacity Planning is done in Jira Align Where to Enter Demand in Jira Align Who When Estimate is Captured Walk Where to Enter Capacity in Jira Align Estimation Purpose Estimation Units Enters the Estimate Work Item Level Member Weeks field on Detail tab of the epic Member Weeks (converted from team- sprints estimates, collected outside JA) To help portfolio leadership to anticipate cost and set a target budget From Plan Capacity button in Forecast page (against an Intake program and Intake PI for the Portfolio) After epic has been pulled from the funnel, with epic in Intake PI Portfolio Room: Resources View View the sum of sizes Epic owners Portfolio Epic From Plan Capacity button in Forecast page Member-Weeks per Program per PI (converted from team- sprints estimates collected outside JA) Epic owners, system architects, and program architects After epic has been accepted into portfolio backlog Forecast page To help portfolio leadership to create realistic roadmaps Forecast tab of the epic (or the Forecast page directly) To help program leadership steer a reasonable amount of work to the next PI (as features) Product managers, working with product architects Override button in Backlog-> Viewing Features-> Kanban Board:Column View Member Weeks field on Detail tab of the feature After feature has been accepted into program backlog (JIRA Epic) Program Room-> Program Increment Load-> <gear> Estimated Member Weeks (converted from team- sprints estimates, collected outside JA) Feature MW->Pts is driven by Estimation Conversions for Fibanocci settings [e.g. if 1 MW = 2.5 story points, then set 1 Fibonacci FP = 0.067 TW To help team leadership to plan the sprints with a consistent velocity target After story has been accepted into sprint backlog N/A Points should be entered in JIRA and viewed as read-only in Points field on the Story in JA Product owners, working with developers Team Velocity in points (per sprint) is calculated automatically but can be overridden from Override button in Backlog->Viewing Stories> Kanban Board:Column View Backlog->Viewing Stories>Kanban Board: Column View Story Story points To enable points-to-$ conversions, Team Allocations in Hours (per sprint) is entered for the individual members of the team from the Sprint object N/A Hours should be entered in JIRA and viewed as read-only in Hours field on the Task in JA To help developers show incremental progress with hour based tasks Task Capacity Planning page After sprint has started Developers Hours
Where Capacity Planning is done in Jira Align Where to Enter Demand in Jira Align Who When Estimate is Captured Run Where to Enter Capacity in Jira Align Estimation Purpose Estimation Units Enters the Estimate Work Item Level Average Program Velocity (per PI) is calculated automatically but can be overridden from Override button in Backlog->Viewing Features-> Kanban Board:Column View Points field on Detail tab of the epic To help portfolio leadership to anticipate cost and set a target budget After epic has been pulled from the funnel, with epic in Intake PI Portfolio Room: Resources View (Anticipated) Story Points Epic owners Portfolio Epic Average Program Velocity (per PI) is calculated automatically but can be overridden from Override button in Backlog->Viewing Features-> Kanban Board:Column View Epic owners, system architects, and program architects After epic has been accepted into portfolio backlog Backlog->Viewing Epics->Kanban Board: Column View To help portfolio leadership to create realistic roadmaps Forecast tab of the epic (or the Forecast page directly) (Anticipated) story pointsper Programper PI Average Program Velocity (per PI) is calculated automatically but can be overridden from Override button in Backlog- >Viewing Features-> Kanban Board:Column View To help program leadership steer a reasonable amount of work to the next PI (as features) Backlog->Viewing Features>Kanban Board: Column View Product managers, working with product architects After feature has been accepted into program backlog (JIRA Epic) Points field on Detail tab of the feature Feature (Anticipated) Story Points Team Velocity in points (per sprint) is calculated automatically but can be overridden from Override button in Backlog- >Viewing Stories> Kanban Board:Column View To help team leadership to plan the sprints with a consistent velocity target Backlog->Viewing Stories>Kanban Board: Column View) After story has been accepted into sprint backlog N/A Points should be entered in JIRA and viewed as read- only in Points field on the Story in JA Product owners, working with developers Story Story points To enable points-to-$ conversions, Team Allocations in Hours (per sprint) is entered for the individual members of the team from the Sprint object Task N/A N/A N/A N/A N/A N/A
