Slidedeck of the 3rd Lean Architecture seminar at Xebia.

1. Seminar Lean Architectuur
Gerard Janssen
Denis Koelewijn
June 24th, 2010 Gero Vermaas

2. Waste

3. Walls

4. Locked down

5. Architecture? Where?
5

6. Architecture can be beautifull

7. Agenda
• Introduction
• Why Architecture?
• Lean & Kanban background
• Interactive part: Architectural challenges
• Lean Architecture: Principles & Process
• Apply Principles and Process to your challenges
• Bol.com Case
• Wrap up
•

8. Introduction
• Name
• Role
• Company
• What do you expect from todays seminar?
• And all of this in 30 seconds

9. Why Architecture?

10. 3 C’s of Architecture
Connection Cohesion
Architecture
Changeability

11. Lean

12. Any use of resources for a purpose
that is not adding value for the end
customer is waste and should be
removed

13. Waste
• Toyota identified the following forms of wasteful activities (Muda)
• Overproduction
• Unnecessary movement of (intermediate) products
• Inventory
• Unnecessary movement of production equipment
• Defects
• Waiting
• Over-processing
• Overload

14. Lean principes

15. Base your management decisions on a
long-term philosophy, even at the
expense of short-term financial goals
15

16. Create a continuous process flow to
bring problems to the surface

17. Use “pull” systems to avoid
overproduction

18. Build a culture of stopping to fix
problems, to get quality right the first
time

19. Use visual control so no problems are
hidden

20. Grow leaders who thoroughly
understand the work, live the
philosophy, and teach it to others

21. Go and see for yourself to thoroughly
understand the situation (genchi
genbutsu)

22. Make decisions slowly by consensus,
thoroughly considering all options;
implement decisions rapidly

23. Become a learning organization
through relentless reflection (hansei)
and continuous improvement (kaizen)

24. Kanban

25. What is Kanban?
• Kan = Visual
• Ban = Board
•
25

26. Make Work Visible

27. Limit Work in Progress

28. Make the work flow

30. Interactive part: Architectural challenges
• Which Architectural challenges are your organization
facing?

32. Lean Architecture
Lean Architecture enforces value creation by
Balancing business and technical values/priorities and
Converging focus of all stakeholders on the required actions, at the
right time, at the correct level of detail

33. Lean Architecture Principles

34. Architecture initiated by business goals

35. Architecture emerging from projects

36. Incremental
development of
36

37. Focus on Value Stream

38. Travel Light

39. Just in Time, Just Enough

40. Think Big, Act Small

41. All hands on deck early on

42. Always Involved

43. Comprehensible over comprehensiveness

44. Freedom where possible, standardize
where needed

45. Lean Architecture Principles
1.Architecture initiated by business goals
2.Architecture emerging from projects
3.Incremental development of architecture
4.Focus on the value stream
5.Travel light
6.Just in time, just enough
7.Think big, act small
8.All hands on deck early on
9.Always involved
10.Comprehensible over comprehensiveness
11.Freedom where possible, standards where needed

46. Break
46

47. Lean Architecture Process
47

48. Scrum based development: basic Scrum
Daily Scrum
Meeting
2 week
sprint Potentially
Demo
Shippable
Product
Retrospective
Increment
Sprint
Sprint Backlog
planning
Product
Backlog

49. User stories

50. Kanban based Lean Architecture
50

51. Architecture and Development
processes

52. 52

53. 53

54. References
• Xebia Blog
http://blog.xebia.com/category/lean-architecture/
• “Lean Architecture” Linked In Group
http://www.linkedin.com/groups?home=&gid=2891065
• September 2010: Lean Architecture Open Space Conference