Presentation by Morgan Ahlström from Meetup Stockholm Go Agile on Nov 12th 2014. On the importance of, and difficulties with slicing an organization to create well defined agile teams with few dependencies.

1. O
Product,
Where
Art
Thou?
Se2ng
the
stage
for
Enterprise
Scrum
Morgan
Ahlström
@morgsterious
072-­‐726
33
03

2. MORGAN

3. Make
it
a
project!

4. “...
a
temporary
endeavor
undertaken
to
create
a
unique
product,
service,
or
result.”
-­‐
PMI

5. Make
it
a
product!

6. What’s
a
“product”?
It
might
not
be
a
“product”?

7. Requirements
on
the
“product”
1. It’s
about
the
work
2. It’s
about
our
business
3. Few
dependencies

8. Pugh-­‐Roberts
Model
Doing
Correctly
Work
to
Do
Work
Done
Doing
Incorrectly
Undiscovered
Rework
Discovered
Rework
Discovering
Rework
Adding
to
Backlog

9. What
happened?
Work
remaining
IniZal
amount
of
work
Time

10. What
happened?
Work
remaining
IniZal
amount
of
work
Unknown
rework
Time

11. IniZal
amount
of
work
What
happened?
Work
remaining
Unknown
rework
IntegraZon
tesZng
Time

12. IniZal
amount
of
work
What
happened?
Work
remaining
Unknown
rework
IntegraZon
tesZng
Time

13. Pugh-­‐Roberts
Model
Doing
Correctly
Work
to
Do
Work
Done
Doing
Incorrectly
Undiscovered
Rework
Discovered
Rework
Discovering
Rework
Adding
to
Backlog

14. Organic
Growth
Created
the
Mess
APPLICATION
Front
End
Middle-­‐
ware
Back
End

15. Organic
Growth
APPLICATION
Front
End
Middle-­‐
ware
Back
End

16. Organic
Growth
Front
End
Middle
-­‐ware
Back
End

17. Conway’s
Law
OrganizaZons
which
design
systems
...
are
constrained
to
produce
designs
which
are
copies
of
the
communicaZon
structures
of
these
organizaZons.

18. Formal
vs
Informal
Structures
Front
End
Middle
-­‐ware
Back
End

19. Upstream
design
Back
End
Back
End
Back
End
Need
Part
SoluZon
Part
SoluZon
Part
SoluZon
Customer

20. APPLICATION
Front
End
Middle-­‐
ware
Back
End
Downstream
design
Need
Customer
SoluZon
+
=>

21. Requirements
on
the
product
1. It’s
about
the
work
2. It’s
about
our
business
3. Few
dependencies

22. So
where’s
our
product?
• The
system
• The
process
• The
value
stream
• The
capability
• ?

23. The
System
...
is
no
longer
the
system
Front
End
Middleware
Back
End
TEAM
TEAM
TEAM

24. The
Process
Changes
Front
End
Middleware
Back
End

25. The
Value
Stream
is
too
large
Value
adding
step
1
Value
adding
step
2
Value
adding
step
3
Front
End
Middleware
Back
End
Front
End
Middleware
Back
End
Front
End
Middleware
Back
End

26. A
Capability
A
business
capability
defines
what
a
business
does.
The
business
capability
is
"a
parZcular
ability
or
capacity
that
a
business
may
possess
or
exchange
to
achieve
a
specific
purpose
or
outcome."

27. CapabiliZes
have
mulZple
relaZons

28. CapabiliZes
X
Value
Stream
• Customer
needs
• Investment
focus
Value
adding
step
1
Value
adding
step
2
Value
adding
step
3

29. CapabiliZes
X
Value
Stream
Claim
registering
Document
handling
Postal
handling
Assessment
Payment
Postal
handling
AccounZng
Customer
interacZon
Customer
interacZon
Register
claim
Process
claim
Process
payment

30. What
do
you
think?