SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Successfully reported this slideshow.
Activate your 14 day free trial to unlock unlimited reading.
This beginner's gude to agile release planning helps you go beyond the sprint. You will understand how to plan a larger deliverable over multiple sprints, how to track progress, and how to forecast using data
I help technology organizations improve performance
This beginner's gude to agile release planning helps you go beyond the sprint. You will understand how to plan a larger deliverable over multiple sprints, how to track progress, and how to forecast using data
3.
Most information about agile is focused on the sprint
@tirrellpayton
http://www.payton-consulting.com
Why?
4.
Most information about agile is focused on the sprint
This leads to the false assumption that you can’t do any long
term/release/strategic planning if your teams are agile
@tirrellpayton
http://www.payton-consulting.com
Why?
5.
@tirrellpayton
http://www.payton-consulting.com
Why?
Most of the focus is here
6.
@tirrellpayton
http://www.payton-consulting.com
Why?
Most of the focus is here
I’ll be explaining this
7.
Release = any number of sprints that combine to form a larger
deliverable
@tirrellpayton
http://www.payton-consulting.com
Release Definition
8.
Release = any number of sprints that combine to form a larger
deliverable
@tirrellpayton
http://www.payton-consulting.com
Release Definition
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6
Release 1 Release 2
9.
Step 1: Start with a goal
@tirrellpayton
http://www.payton-consulting.com
Where to Start?
10.
Step 1: Start with a goal
Step 2: Create a feature list
@tirrellpayton
http://www.payton-consulting.com
Where to Start?
11.
Step 1: Start with a goal
Step 2: Create a feature list
Step 3: Prioritize the features
@tirrellpayton
http://www.payton-consulting.com
Where to Start?
12.
Step 1: Start with a goal
Step 2: Create a feature list
Step 3: Prioritize the features
Why is prioritization important?
@tirrellpayton
http://www.payton-consulting.com
Where to Start?
13.
Why is prioritization important?
No matter the delivery method, the triple constraint does not change
@tirrellpayton
http://www.payton-consulting.com
Where to Start?
14.
Why is prioritization important?
No matter the delivery method, the triple constraint does not change
@tirrellpayton
http://www.payton-consulting.com
Where to Start?
15.
Why is prioritization important?
We want to understand the features most critical to reaching the goal
@tirrellpayton
http://www.payton-consulting.com
Where to Start?
16.
Why is prioritization important?
This is why we started with the goal
@tirrellpayton
http://www.payton-consulting.com
Where to Start?
17.
Step 1: Start with a goal
Step 2: Create a feature list
Step 3: Prioritize the features
Why is prioritization important?
@tirrellpayton
http://www.payton-consulting.com
Where to Start?
‘Memba this?
22.
Must Have
@tirrellpayton
http://www.payton-consulting.com
MoSCoW
23.
Must Have
Should Have
@tirrellpayton
http://www.payton-consulting.com
MoSCoW
24.
Must Have
Should Have
Could Have
@tirrellpayton
http://www.payton-consulting.com
MoSCoW
25.
Must Have
Should Have
Could Have
Wont Have
@tirrellpayton
http://www.payton-consulting.com
MoSCoW
26.
Must Have
Should Have
Could Have
Wont Have
@tirrellpayton
http://www.payton-consulting.com
MoSCoW
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
27.
Must Have
Should Have
Could Have
Wont Have
@tirrellpayton
http://www.payton-consulting.com
MoSCoW
Feature
Feature
Feature What’s in here?
28.
Must Have
Should Have
Could Have
Wont Have
@tirrellpayton
http://www.payton-consulting.com
MoSCoW
Feature
Feature
Feature What’s in here?
Feature
Requirements
Acceptance Criteria
Design
Build
Test
UAT
Enough to be
“potentially shippable”
29.
Must Have
Should Have
Could Have
Wont Have
@tirrellpayton
http://www.payton-consulting.com
MoSCoW
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Must Have
30.
Must Have
Should Have
Could Have
Wont Have
@tirrellpayton
http://www.payton-consulting.com
MoSCoW
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Must Have
Should Have
31.
Must Have
Should Have
Could Have
Wont Have
@tirrellpayton
http://www.payton-consulting.com
MoSCoW
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Must Have
Should Have
Could Have
32.
Must Have
Should Have
Could Have
Wont Have
@tirrellpayton
http://www.payton-consulting.com
MoSCoW
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Must Have
Should Have
Could Have
Won’t Have
33.
No matter the delivery method, the triple constraint does not change
@tirrellpayton
http://www.payton-consulting.com
Triple Constraint
34.
Bonus Question: What if you fixed time, fixed scope, fixed budget?
@tirrellpayton
http://www.payton-consulting.com
Triple Constraint
35.
Bonus Question: What if you fixed time, fixed scope, fixed budget?
@tirrellpayton
http://www.payton-consulting.com
Triple Constraint
36.
You end up flexing on the “hidden constraint”, which is quality. But
you can only hide it for so long.
@tirrellpayton
http://www.payton-consulting.com
Triple Constraint
37.
This is part of why we deliver in short cycles, even with our longer
term plan
@tirrellpayton
http://www.payton-consulting.com
Triple Constraint
38.
It enables us to more closely monitor quality, which tends to be a
hidden constraint
@tirrellpayton
http://www.payton-consulting.com
Triple Constraint
39.
Release
Triple Constraint
Shorter increments are
@tirrellpayton
http://www.payton-consulting.com
40.
Release
Triple Constraint
Shorter increments are
- Easier to estimate
Sprint 1 Sprint 2
@tirrellpayton
http://www.payton-consulting.com
41.
Release
Triple Constraint
Shorter increments are
- Easier to estimate
- Faster to deliver
Sprint 1 Sprint 2 Sprint 3 Sprint 4
@tirrellpayton
http://www.payton-consulting.com
42.
Release
Triple Constraint
Shorter increments are
- Easier to estimate
- Faster to deliver
- Easier to measure
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6
@tirrellpayton
http://www.payton-consulting.com
43.
Release
Triple Constraint
Shorter increments are
- Easier to estimate
- Faster to deliver
- Easier to measure
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6
@tirrellpayton
http://www.payton-consulting.com
Also, you can revalidate after
every increment
44.
Hypothesis
Honesty time
@tirrellpayton
http://www.payton-consulting.com
45.
Hypothesis
Honesty time
At the beginning of our project, what are our estimates (time, people,
budget)?
@tirrellpayton
http://www.payton-consulting.com
48.
Hypothesis
Honesty time
At the beginning of our project, what are our estimates (time, people,
budget)?
It’s a hypothesis
@tirrellpayton
http://www.payton-consulting.com
49.
Hypothesis
What we’re saying is, “Based on what we know at this time, this is
what we think this project needs in order to reach its goal.”
@tirrellpayton
http://www.payton-consulting.com
50.
Hypothesis
What we’re saying is, “Based on what we know at this time, this is
what we think this project needs in order to reach its goal.”
The problem is we make the biggest decisions about a project when
we have the least information
@tirrellpayton
http://www.payton-consulting.com
51.
Hypothesis
What we’re saying is, “Based on what we know at this time, this is
what we think this project needs in order to reach its goal.”
The problem is we make the biggest decisions about a project when
we have the least information.
How many times during a project have you said, “If we only knew
then what we know now…”
@tirrellpayton
http://www.payton-consulting.com
52.
Release
Hypothesis
Shorter increments are
- Easier to estimate
- Faster to deliver
- Easier to measure
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6
@tirrellpayton
http://www.payton-consulting.com
Also, you can revalidate after
every increment
53.
Release
Hypothesis
Shorter increments are
- Easier to estimate
- Faster to deliver
- Easier to measure
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6
@tirrellpayton
http://www.payton-consulting.com
Also, you can revalidate after
every increment
That’s what this does!
54.
Hypothesis
If we treat our initial estimate as a hypothesis, it allows us the courage
to validate it with real data
@tirrellpayton
http://www.payton-consulting.com
59.
Planned Release
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
Hypothesis: We think we can get this done by mid-October with 5
people and $300k
60.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
How quickly can we validate this hypothesis?
61.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
How quickly can we validate this hypothesis?
About 10 days
62.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
How quickly can we validate this hypothesis?
About 10 daysJune 15
63.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
How do we validate this hypothesis?
64.
Validation
@tirrellpayton
http://www.payton-consulting.com
How do we validate this hypothesis?
65.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
How do we validate this hypothesis?
66.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
How do we validate this hypothesis?
Time Spent: 12.5%
Features Accepted: 12.5%
Budget aSpent: 12.5%
67.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
How do we validate this hypothesis?
Time Spent: 12.5%
Features Accepted: 12.5%
Budget Spent: 12.5%
68.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
What if this happens?
Time Spent: 12.5%
Features Accepted: 6.5%
Budget Spent: 12.5%
69.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
Bad News: We’re off track
Time Spent: 12.5%
Features Accepted: 6.5%
Budget Spent: 12.5%
70.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
Bad News: We’re off track
Good News: It only took us 10 days to find out
Time Spent: 12.5%
Features Accepted: 6.5%
Budget Spent: 12.5%
71.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
Use that information to re-plan going forward
Time Spent: 12.5%
Features Accepted: 6.5%
Budget Spent: 12.5%
72.
June October
Requirements
Design
Build
QA
UAT
@tirrellpayton
http://www.payton-consulting.com
Release Planning
Hypothesis: We think we can get this work done by mid-October with
5 people and $300k
73.
June October
Requirements
Design
Build
QA
UAT
@tirrellpayton
http://www.payton-consulting.com
Release Planning
How quickly can we validate this hypothesis?
74.
June October
Requirements
Design
Build
QA
UAT
@tirrellpayton
http://www.payton-consulting.com
Release Planning
How quickly can we validate this hypothesis?
Usually about here
75.
June October
Requirements
Design
Build
QA
UAT
@tirrellpayton
http://www.payton-consulting.com
Release Planning
How quickly can we validate this hypothesis?
Usually about here
September 15
76.
June October
Requirements
Design
Build
QA
UAT
@tirrellpayton
http://www.payton-consulting.com
Makes People Sad
September 15
77.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
What if this happens?
Time Spent: 87.5%
Features Accepted: 74%
Budget Spent: 100%
78.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
This is why priority is important
Time Spent: 87.5%
Features Accepted: 74%
Budget Spent: 100%
79.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
This is why priority is important
Bad News: We’re Broke
Time Spent: 87.5%
Features Accepted: 74%
Budget Spent: 100%
80.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
This is why priority is important
Good News: The highest priority features are done
Time Spent: 87.5%
Features Accepted: 74%
Budget Spent: 100%
81.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
This is why priority is important
The project can still be a success
Time Spent: 87.5%
Features Accepted: 74%
Budget Spent: 100%
82.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
This is why priority is important
We can choose to fund more, or not
Time Spent: 87.5%
Features Accepted: 74%
Budget Spent: 100%
83.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
We create a plan (hypothesis), then we validate it with actual
performance data
84.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
This helps us answer questions like:
85.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
How long will it take?
86.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
The data says we will finish around mid-October
Time Spent: 87.5%
Features Accepted: 74%
Budget Spent: 100%
87.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
The data says we will finish around mid-October
We have spent 2 of 16 weeks (12.5%)
Time Spent: 12.5%
Features Accepted: 12.5%
Budget Spent: 12.5%
88.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
How much will it cost?
89.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
How much will it cost?
Based on the data, about $300k
Time Spent: 12.5%
Features Accepted: 12.5%
Budget Spent: 12.5%
90.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
How much will it cost?
We have spent $37.5k (12.5%)
Time Spent: 12.5%
Features Accepted: 12.5%
Budget Spent: 12.5%
91.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
How much will it cost?
And we have finished 12.5% of the features
Time Spent: 12.5%
Features Accepted: 12.5%
Budget Spent: 12.5%
92.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
What % complete are you?
Time Spent: 12.5%
Features Accepted: 12.5%
Budget Spent: 12.5%
93.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
What % complete are you?
The data says 12.5%
Time Spent: 12.5%
Features Accepted: 12.5%
Budget Spent: 12.5%
94.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
What % complete are you?
We have completed 12.5% of the features
Time Spent: 12.5%
Features Accepted: 12.5%
Budget Spent: 12.5%
95.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
How do you really know its done?
Time Spent: 12.5%
Features Accepted: 12.5%
Budget Spent: 12.5%
96.
Validation
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
How do you really know its done?
Its running in the stage environment and the PO signed off
Time Spent: 12.5%
Features Accepted: 12.5%
Budget Spent: 12.5%
97.
Forecasting
@tirrellpayton
http://www.payton-consulting.com
How do you really know its done?
Its running in the stage environment and the PO signed off
Feature
Requirements
Acceptance Criteria
Design
Build
Test
UAT
“Potentially
Shippable”
98.
Forecasting
@tirrellpayton
http://www.payton-consulting.com
Bonus Question: What % complete are you?
June October
Requirements
Design
Build
QA
UAT
99.
Forecasting
@tirrellpayton
http://www.payton-consulting.com
Bonus Question: What % complete are you?
How do you know its done?
June October
Requirements
Design
Build
QA
UAT
100.
Forecasting
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
How much will be done by September 1?
Time Spent: 12.5%
Features Accepted: 12.5%
Budget Spent: 12.5%
101.
Forecasting
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
How much will be done by September 1?
The data says we will be here by September 1
Time Spent: 12.5%
Features Accepted: 12.5%
Budget Spent: 12.5%
102.
Forecasting
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
When will all the must haves be completed?
Time Spent: 12.5%
Features Accepted: 12.5%
Budget Spent: 12.5%
103.
Forecasting
@tirrellpayton
http://www.payton-consulting.com
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Feature
S1 S4S2 S3 S5 S8S6 S7
June October
When will all the must haves be completed?
The data says “in the next week”
Time Spent: 12.5%
Features Accepted: 12.5%
Budget Spent: 12.5%
104.
Forecasting is not an exact science, but you can use science to get
better forecasts
Start by creating preliminary assumptions based on the data you have
Relentlessly exploit your most current data to validate or refute your
assumptions
Repeat
@tirrellpayton
http://www.payton-consulting.com
Summary
105.
Payton Companies like yours achieve higher performance through
coaching, consulting, and training
@tirrellpayton
http://www.payton-consulting.com
Thanks!