You’ve been there before. You know better, you have a good idea to support your agile transition. Work starts, things work well at first, but then you bump against organizational barriers. Sales, Marketing, Support all have a different language and a different view into the value stream. How can we start an organizational change without a shared model of how the company should be organized? Those are all symptoms of a gap in our Agile community: we lack a organizational model for company-wide Agile adoption and company-wide continuous improvement. Examples of this include: no company-wide flow-model (kanban) from idea to sales to idea and so on; we have no way to evaluate where the bottlenecks are the moment they are not in “our silo”. We lack a theoretical model for designing software organizations. A theory is something that informs day-to-day decisions and experiments (e.g. PDCA). In this talk we will explain an organizational design concept developed over several years, and use concrete examples to describe a model that you can use in support of - not only your agile adoption - but your company improvement process and your new organizational design.

1. @duarte_vasco and @lasseziegler
Visualize the work – Kanban
for the whole value stream

2. Tambako @ flickr

3. V-Model
Spiral MOdel
Rapid Software Development Chaotic development
DSDM
• Add buzzwords of failed models
Rational Unified Process
FDD
Danisarda @ flickr

4. Ericcastro @ flickr

5. Ken Schwaber: 75% of
organizations fail to benefit
from Agile/Scrum as expected
http://www.agilecollab.com/interview-with-ken-schwaber

6. Cayusa @ flickr

7. Would you go back to the old way of working?
Large hardware + software company in nordics

8. NSN, presentation at JAOO/2010

9. Matley0 @ flickr

10. Act II – developing the action

11. Louish @ flickr

12. What is the biggest problem in
your organization?

13. Zenera @ flickr

14. • Overburdden or Muri
Topgold @ flickr

15. Skuds @ flickr

16. It is hard
There’s a
and slow to
bottleneck
hire good
in R&D
Hire more people Salaries
people here are
too high!
Need to And then we get faster
spend time
Travel and wait...
R&D!!! Oh Work with
with off-
communication off-shore
shore
costs increase and near-
teams
shore
Communication
problems emerge

19. Market
Market
Here be You are here Here be
dragons dragons
(R&D / IT)

20. 1. Why do we have so many
features in the backlog?
2. What are the value stream
steps that we don’t know
about yet? Or don’t even
understand?

21. Market
Market
Here be You are here Here be
dragons dragons
(R&D / IT)
Pre- Revenue
idea experiment valid To do Doing Done prodcution Production generated

22. Market
Market
Here be You are here Here be
dragons dragons
(R&D / IT)

23. Features left to complete
Likely progress at current pace
Likely release date some
where there...
Time
Release date ...

24. Company
acquired
Lack of scrutiny
by Product
Need to add Manager or
more features other
<exercise for
the audience>
All new
Increase features are
pressure on added
teams

25. Make information about the
system visibile
... And that’s just the start...

26. End of
Features in the Backlog Roadmap
cycle End of
End of strategy
strategy cycle
cycle
Time

27. Stay tuned for an example...

28. Jduty @ flickr

29. <PDCA Concentric circles>
Papalars @ flickr

30. Gertcha @ flickr

31. Example 1: Why do we have so
little througput?

32. Stuff that is going on

33. Development
Stuff in
Stuff that is production
going on

34. Where are all these projects
coming from?

35. Development
Stuff in
Stuff that is production
going on

36. Project
evaluation Development
Stuff in
Stuff that is production
going on

37. Wish Project Production
List evaluation Life-cycle
Development
Stuff in
production

38. Wish Project Production
List evaluation Life-cycle
Development
Production
Stuff in
production
Live Maintenance

39. Example 2: The Feature Team

40. Component A Component B
Queue Development Testing Development Testing

41. Component A Component B
Queue Development Testing Development Testing

42. Feature Team
(A + B)
Queue Development Testing

43. Feature Team
(A + B)
Queue Development Testing Post-production
Localization
Documentation

44. Example 3: What happens on the
Product Management part of the
chain?

45. Feature Team
(A + B)
Queue Development Testing Post-production
Localization
Documentation

46. This *was* the queue!
MVP Validated Development
Filtering ideas
The CTO pool
/ Integration
Acquisition
Customer
Requests

47. Example 5: Why do we get such a
big queue at specific intervals?

48. Queue Development Testing

49. Roadmap
Process
Output Development Testing
Happens in Spring and Autumn

50. Strategy Roadmap
Process Process
Output Development Testing
Happens in Spring and is
”reviewed” in Autumn

51. One more thing...

52. Newfrontiersmedia @ flickr

53. Act III – Turning point

54. Bazzadarambler @ flickr

55. Normanbleventhalmapcenter @ flickr

56. Zeptonn @ flickr