Read Article at https://www.linkedin.com/pulse/ltp4scrum-goal-tree-based-scrum-planning-moving-release-max-börebäck/ Are you an Agile Product Owner, or a scrum master I think you should try Goal Tree based planning

1. LTP4Scrum or Goal Tree based planning
Max Börebäck 1
Release Train
Product Goal
Critical Success
Factor
Critical Success
Factor
Critical Success
Factor
Release 1 Release2 Sprint
Necessary
condition
Consumer
Critical Success
Factor
Critical Success
Factor
Critical Success
Factor
Necessary
condition
Necessary
condition
Necessary
condition
Necessary
condition
Consumer
Critical Success
Factor
Critical Success
Factor
Critical Success
Factor
Necessary
condition
Necessary
condition
Necessary
condition
Necessary
condition
Issues etc
story story
Necessary
condition
Necessary
condition
Release 1 Release 2 Sprint
ToDo Doing Done
Create
a
scrum
team
Estima
te
stories
Leading
retrospectiv
e
Scrum in
Srum
cooperat
ion
Key
takeaw
ays
Key
takeaw
ays
done

2. LTP4Scrum
Or Goal Tree planning
Planning with success
Utilize the Logical Thinking Process with Scrum to secure that you reach
your Goal
Max Börebäck 2

3. Product owner Release Train contains
Max Börebäck 3
Product
Planned
Stories
Product
Consumption
Stories
Product
Issues &
maintenance
Done
Done Done Done

4. Release Tree contains all
Necessary Condition to complete the release
Max Börebäck 4
Release Train
Product Goal
Critical Success
Factor
Critical Success
Factor
Critical Success
Factor
Release 1 Release2 Sprint
Necessary
condition
Consumer
Critical Success
Factor
Critical Success
Factor
Critical Success
Factor
Necessary
condition
Necessary
condition
Necessary
condition
Necessary
condition
Consumer
Critical Success
Factor
Critical Success
Factor
Critical Success
Factor
Necessary
condition
Necessary
condition
Necessary
condition
Necessary
condition
Issues etc
story story
Necessary
condition
Necessary
condition
Release 1 Release 2 Sprint
ToDo Doing Done
Create
a
scrum
team
Estima
te
stories
Leading
retrospectiv
e
Scrum in
Srum
cooperat
ion
Key
takeaw
ays
Key
takeaw
ays
done

5. DEMING GOLDRATT
SYSTEMS THINKING, CONSTRAINT BASED THINKING
• WHY change?
• WHAT to change?
• What to change TO?
• HOW to cause the change?
• Where to change?
• When to Change?
Max Börebäck 5
1984
1984

6. Lean, TOC, LTP, DevOps
Max Börebäck 6
The Devops Handbook
by Gene Kim, Jez Humble,
Patrick Debois
The Phoenix Project
by Gene Kim, Kevin Behr,
George Spafford
The Goal: A Process of
Ongoing Improvement
av Eliyahu M. Goldratt,
Jeff Cox, David Whitford
1984
The Logical Thinking Process:
A Systems Approach
to Complex Problem
Solving
by H. William Dettmer

7. Logical thinking types
• Necessary or need based thinking
• Top down, by identifying the necessary things you need to fulfil the objective
• In Order to have this I must have/do this and I must have/do this
• Sufficient or consequent based thinking
• Bottom up, identifying what you need to make the parent happen
• If I do this and I do this then this will happen
• Most people usually prefer Sufficient logic as it feels easier
• Plotting
Max Börebäck 7

8. Goal I am eating pancakes (sufficient logic)
Max Börebäck 8

9. Goal I am eating pancakes (sufficient logic)
Max Börebäck 9

10. Goal I am eating pancakes (necessity logic)
Max Börebäck 10

11. Goal I am eating pancakes (necessity logic)
11

12. What was the difference?
• And why did you make the the trees differently?
Max Börebäck 12

13. Planning a sprint
Max Börebäck 13
Release Train
Product Goal
Critical Success
Factor
Critical Success
Factor
Critical Success
Factor
Release 1 Release2 Done
Necessary
condition
Consumer
Critical Success
Factor
Critical Success
Factor
Critical Success
Factor
Necessary
condition
Necessary
condition
Necessary
condition
Necessary
condition
Consumer
Critical Success
Factor
Critical Success
Factor
Critical Success
Factor
Necessary
condition
Necessary
condition
Necessary
condition
Necessary
condition
Issues etc
story story
Necessary
condition
Necessary
condition
Release 1 Release 2 Sprint
ToDo Doing Done
Create
a
scrum
team
Estima
te
stories
Leading
retrospectiv
e
Scrum in
Srum
cooperat
ion
Key
takeaw
ays
Key
takeaw
ays
done

14. Planning a sprint
Max Börebäck 14
Release Train
Product Goal
Critical Success
Factor
Critical Success
Factor
Critical Success
Factor
Sprint Release2 Done
Necessary
condition
Consumer
Critical Success
Factor
Critical Success
Factor
Critical Success
Factor
Necessary
condition
Necessary
condition
Necessary
condition
Necessary
condition
Consumer
Critical Success
Factor
Critical Success
Factor
Critical Success
Factor
Necessary
condition
Necessary
condition
Necessary
condition
Necessary
condition
Issues etc
story story
Necessary
condition
Necessary
condition
Release 1 Release 2 Sprint
ToDo Doing Done
Create
a
scrum
team
Estima
te
stories
Leading
retrospectiv
e
Scrum in
Srum
cooperat
ion
Key
takeaw
ays
Key
takeaw
ays
done

15. Create Sprint Plan
Max Börebäck 15
• Break down the stories
into tasks
• In order to <item> I/we
must <item>
• Clearly identify any
dependencies
• Especially external
Execute
Plan

16. Sprint plan with time simulation
Max Börebäck 16
Execute
Day
7
Day
14
Day
3
Day
10

17. Sprint plan
Max Börebäck 17
xxx
Automation
Manual
installation on
one node
Done
Ongoing
To Do
Solve all
dependencies,
obstacles
Get familiar with
all steps and
understand
dependencies to
parallel the effort
Pre installation
role
Installation
role
Post
installatio
n role
kerberization
Integration of
playbook
Code base cleanup, create new playbook to
uninstall xxx and other management tasks
Get all nodes
information for
xxx server
Manual
installation on
another node
Create ansible
role skeleton to
work
Send to xxx to get
updated info for
yyy server
Retrieving key
from key server
not working
Blocking
Rerun playbooks in node1 & node2 nodes
And validate everything is working
Get keytab for
ToDo Doing Done
Create a
scrum
team
Estimate
stories
Leading
retrospective
Scrum in
Srum
cooperation
Key
takeaways
Key
takeaways
Description of why we are
blocked and mitigation actions

18. Do we have the right things
in backlog?
Max Börebäck 18
Sprint
Release
Next Release
Backlog
Next sprint

19. Where are
we heading?
What is the Goal?
Max Börebäck 19

20. What is our Goal?
• A Goal is the end of the journey and shall be stated in present form
• We earn money now and in the future
• SMART goal (use smart as a guideline for defining the goal)
• Specific (simple, sensible, significant).
• Measurable (meaningful, motivating).
• Achievable (agreed, attainable).
• Relevant (reasonable, realistic and resourced, results-based).
• Time bound (time-based, time limited, time/cost limited, timely, time-
sensitive).
• What is our Goal, What do you think?
Max Börebäck 20

21. The System
• Things you can control
• My apartment/living
• Things you can influence
• My neighbours
• Things you have to accept
• Weather
• The Goal should be set on
what you control
• Can include what you can
influence
Max Börebäck 21

22. What is your Goal?
Max Börebäck 22

23. System outcome
• The Goal is the end of the journey
• Critical Success Factors are a break
down of the Goal
• The last things that has to happen
before the goal can be meet
• Goal and Critical Success Factors
defines the system and its purpose
• The Goal together with the Critical
Success Factors provides the
project definition.
Max Börebäck 23
Goal
The ultimate
objective
Critical Success Factor
Critical requirement that
has to be meet for the goal
to be meet
Critical Success Factor
Critical requirement that
has to be meet for the goal
to be meet

24. System outcome
• The Goal is the end of the journey
• Critical Success Factors are a break
down of the Goal
• The last things that has to happen
before the goal can be meet
• Goal and Critical Success Factors
defines the system and its purpose
• The Goal together with the Critical
Success Factors provides the
project definition.
Max Börebäck 24
Earn money
now and in the
future
Maximize
throughput
Minimize
Operational
Expense
Minimize
Inventory

25. What is your Critical Success Factors?
Max Börebäck 25
We earn money now and in the future
? ? ? ? ? ?

26. Create the Goal Tree
Break down our Critical Success Factors in all Necessary Conditions we
need to make the the Critical Success Factors happen.
Max Börebäck 26

27. Use necessary based logic
Watch out for conflicts
Max Börebäck 27
GOAL
N1
N2W2
W1
CONFLICT
N3
N4
W5
W6
W7
W4
W3

28. Focus and plan
Goal Tree
Max Börebäck 28
Product Goal
Critical Success
Factor
Critical Success
Factor
Critical Success
Factor
Necessary
condition
Necessary
condition
Necessary
condition
Necessary
condition
Want/tactical (necessary)
need (necessary)
objective
In order to <item>
I/we must <item>

29. Max Börebäck 29
Product Goal
Critical Success
Factor
Critical Success
Factor
Critical Success
Factor
Necessary
condition
Necessary
condition
Necessary
condition
Necessary
condition
Necessary
condition
Necessary
condition
Necessary
condition Necessary
condition
Want/tactical (necessary)
need (necessary)
objective
In order to <item>
I/we must <item>

30. Measurement
Max Börebäck 30
Product Goal
Critical Success
Factor
Critical Success
Factor
Critical Success
Factor
Necessary
condition
Necessary
condition
Necessary
condition
Necessary
condition
Measurements
Is helping you
Behave in a way
That takes you
To the Goal
Quote from Goldratt
Tell me how you measure me,
and I will tell you how I will behave.
If you measure me in an illogical way…
do not complain about illogical behaviour…
Mssure
Measure
Measure
Measure

31. O, did you get a conflict
while planning!
How do you plan to solve it?
Max Börebäck 31

32. How do you usually solve a conflict today?
• One side gives up because they don’t want to deal with the
problem?
• One side forces the other side to give up?
• One or both sides ignore the problem?
• The sides negotiate a compromise?
In all of this cases at least one side loses!
Compromising means both side loses!
Max Börebäck 32
GOAL
N1
N2
W2
W1
CONFLICT
N3
N4
W5
W6
W7
W4
W3

33. Max Börebäck 33
Conflict solve it with Win - Win
Common
Objective
Q: What is the
common objective
for what N1 & N2 is
needed
Need (N1)
Q: What need of
objective will W1
satisfy?
Need (N2)
Q: What need of
objective will W2
satisfy?
Want (W2)
Q: What
action/decision do
I want to take?
Want (W1)
Q: What
action/decision do
I want to take?Conflict
If W1
prevent N2
or W3
prevents
N1
Assumption Assumption
Assumption
Assumption
Assumption

34. Max Börebäck 34
In order to have an apartment in Spain
Apartment in Spain
N1
Easy access to the
beach
N2
Calm and relaxing
surrounding
W2
Apartment NOT at
the beach
W1
Apartment at the
beach
Conflict
We can
not do
both
G
O
A
L
N
1
N
2
W
2
W
1
C
O
NF
LI
CT
N
3
N
4
W
5
W
6
W
7
W
4
W
3

35. Finalising the Goal Tree Design,
with 2 level Necessary Conditions
Max Börebäck 35
Goal
? ? ? ? ? ?
? ?
? ?
?
In order to “GOAL”
I/we must <item> and I/we must <item> and I/we must <item>

36. Max Börebäck 36

37. Product owner Release Train contains
Max Börebäck 37
Product
Planned
Stories
Product
Consumption
Stories
Product
Issues &
maintenance

38. Agile steps to get there and keep staying
there
• A release is a way to communicate to stakeholders what we offer in the future
• A release make the goal realistic by focusing on small steps (reachable, here now)
• A release shall deliver value and be fixed in time
• Both the value and the time shall be communicated in advance
• However, we are still agile and scope will change
• Sprints are sub deliveries in a release
• But a sprint is not only release work
• Consumption stories
• Deliveries to other agile teams
• Issues, Operational and maintenance tasks
• Bug fixes
• Support to our users
Max Börebäck 38

39. Planning the with the Goal Tree
• New demands are coming in all the time
• Separate consumption demands from extension demands of platform
• Extensions has to go into the Goal Tree
• Goal Tree is helping you say no
• You can analyse a request against what is in the Goal Tree and prioritise it against
other necessary condition
• Goal Tree should drive the priority of the backlog
• Backlog will contain things not in the Goal Tree like
• Operational tasks
• Issues etc
• Consumption stories
Max Börebäck 39

40. Release Tree contains all
Necessary Condition to complete the release
Max Börebäck 40
Release Tree
Product Goal
Critical Success
Factor
Critical Success
Factor
Critical Success
Factor
Release 1 Release2 Sprint
Necessary
condition
Consumer
Critical Success
Factor
Critical Success
Factor
Critical Success
Factor
Necessary
condition
Necessary
condition
Necessary
condition
Necessary
condition
Consumer
Critical Success
Factor
Critical Success
Factor
Critical Success
Factor
Necessary
condition
Necessary
condition
Necessary
condition
Necessary
condition
Issues etc
story story
Necessary
condition
Necessary
condition
Release 1 Release 2 Sprint
ToDo Doing Done
Create
a
scrum
team
Estima
te
stories
Leading
retrospectiv
e
Scrum in
Srum
cooperat
ion
Key
takeaw
ays
Key
takeaw
ays
done

41. Plan ahead
Max Börebäck 41
Sprint
Release
Next Release
Backlog
Goal Tree’s
Release Tree
Next sprint
Draft plan
Catch
dependencies
Draft design
Detailed plan
Move
dependencies
Release Tree
Product Goal
Critical Success Factor Critical Success Factor Critical Success Factor
Release 1
Release2 Sprint
Necessary condition
Consumer
C
r
i
t
i
c
a
l
S
u
c
c
e
s
s
F
a
c
t
o
r
C
r
i
t
i
c
a
l
S
u
c
c
e
s
s
F
a
c
t
o
r
C
r
i
t
i
c
a
l
S
u
c
c
e
s
s
F
a
c
t
o
r
N
e
c
e
s
s
a
r
y
c
o
n
d
i
t
i
o
n
N
e
c
e
s
s
a
r
y
c
o
n
d
i
t
i
o
n
N
e
c
e
s
s
a
r
y
c
o
n
d
i
t
i
o
n
N
e
c
e
s
s
a
r
y
c
o
n
d
i
t
i
o
n
Consumer
C
r
i
t
i
c
a
l
S
u
c
c
e
s
s
F
a
c
t
o
r
C
r
i
t
i
c
a
l
S
u
c
c
e
s
s
F
a
c
t
o
r
C
r
i
t
i
c
a
l
S
u
c
c
e
s
s
F
a
c
t
o
r
N
e
c
e
s
s
a
r
y
c
o
n
d
i
t
i
o
n
N
e
c
e
s
s
a
r
y
c
o
n
d
i
t
i
o
n
N
e
c
e
s
s
a
r
y
c
o
n
d
i
t
i
o
n
N
e
c
e
s
s
a
r
y
c
o
n
d
i
t
i
o
n
Issues etc
s
t
o
r
y
s
t
o
r
y
N
e
c
e
s
s
a
r
y
c
o
n
d
i
t
i
o
n
N
e
c
e
s
s
a
r
y
c
o
n
d
i
t
i
o
n

42. Remove constraints
• Plan ahead for next release and next sprint
• Make draft design to identify any dependencies especially external
• Service accounts, access to data source, firewall etc
• Any external dependency
• Optimize the sprint based on
• Moving the release train
• Enabling throughput (consumption of platform)
• Resource dependency/competence
• Identify and remove constrains
Max Börebäck 42
1. Identify the system constraint.
2. Decide how to exploit the system constraint.
3. Subordinate everything else to the system constraint.
4. If necessary, elevate the system constraint.
5. Return to Step 1

43. Type of Constraints
1. Resource/Capacity Constraints
2. Market Constraints
3. Material Constraints
4. Supplier/Vendor Constraints
5. Financial Constraints
6. Knowledge/Competence Constraints
7. Policy Constraints
Max Börebäck 43
Product Goal
Critical Success
Factor
Critical Success
Factor
Critical Success
Factor
Necessary
condition
Necessary
condition
Necessary
condition
Necessary
condition
Necessary
condition
Necessary
condition
Necessary
condition Necessary
condition

44. Constraint based thinking
Max Börebäck 44
1. Identify the system constraint.
2. Decide how to exploit the system
constraint.
3. Subordinate everything else to
the system constraint.
4. If necessary, elevate the system
constraint.
5. Return to Step 1.
The picture is borrowed from a Bob Sproull’s latest book.

45. Good Luck
Max Börebäck 45

46. Release and sprint planning
• Always have 2 releases planned
• Always design next sprint in the beginning of current sprint
• Make “draft/good enough” design of key things
• Identify constraints that needs to be resolved
• Identify and order FW opening needs
• Identify and order access
• All external dependencies will be constrains
• Focus on things you do not own
• Plan when detailed design has to be done
• Agile
• Your plan will change, next release will be changed
• Plan the work weekly to secure that you adopt to the agility need
• Release planning
• Sprint planning
Max Börebäck 46

47. Planning circle
Use need based thinking
Max Börebäck 47
Want/tactical (necessary)
need (necessary)
objective

48. Max Börebäck 48
Want/tactical (necessary)
need (necessary)
objective