Seminar Lean Architecture May 18th 2010
1 like525 views
The seminar covered lean architecture principles and processes. It began with introductions and expectations. The presenters then discussed why architecture is important, focusing on connection, cohesion, and changeability. Lean principles like reducing waste and continuous improvement were explained. Interactive exercises had attendees discuss their architectural challenges. Eleven lean architecture principles were presented, such as always being involved, thinking big but acting small, and emerging architecture from projects. Finally, the presenters described lean architecture and development processes using Kanban boards to coordinate work across teams.
Seminar Lean Architecture May 18th 2010
- 1. Seminar Lean Architectuur Gerard Janssen May 18th, 2010 Denis Koelewijn Gero Vermaas
- 6. Agenda • Introduction • Why Architecture? • Lean & Kanban backgroup • Interactive part: Architectural challenges • Lean Architecture: Principles & Process • Apply Principles and Process to your challenges • Bol.com Case • Wrap up •
- 7. Introduction • Name • Role • Company • What do you expect from todays seminar?
- 9. 3 C’s of Architecture Connection Cohesion Architecture Changeability
- 10. Lean
- 11. Any use of resources for a purpose that is not adding value for the end customer is waste and should be removed
- 12. Waste • Lean is known for focus on reducing waste • muda, mura, muri • Toyota identified the following forms of waste • Overproduction • Unnecessary movement of (intermediate) products • Inventory • Unnecessary movement of production equipment • Defects • Waiting • Over-processing • Overload
- 13. Lean principes • Base your management decisions on a long-term philosophy, even at the expense of short-term financial goals. • Create a continuous process flow to bring problems to the surface • Use “pull” systems to avoid overproduction • Build a culture of stopping to fix problems, to get quality right the first time. • Standardized tasks and processes are the foundation for continuous improvement and employee empowerment. • Use visual control so no problems are hidden. • Go and see for yourself to thoroughly understand the situation (genchi genbutsu). • Make decisions slowly by consensus, thoroughly considering all options; implement decisions rapidly • Become a learning organization through relentless reflection (hansei) and continuous improvement (kaizen).
- 14. Kanban
- 15. What is Kanban? • Kan = Visual • Ban = Board • 15
- 19. Interactive part: Architectural challenges • Which Architectural challenges is your organization facing?
- 21. 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
- 23. Principle #1: Always Involved
- 24. Principle #2: Travel Light
- 25. Principle #3: Think Big, Act Small
- 26. Principle #4: All hands on deck early on
- 27. Principle #5: Just in Time, Just Enough
- 28. Principle #6: Architecture initiated by business goals
- 29. Principle #7: Focus on Value Stream
- 30. Principle #8: Comprehendible over comprehensiveness
- 31. Principle #9: Incremental development of architecture 31
- 32. Principle #10: Architecture emerging from projects
- 33. Principle #11: Freedom where possible, standardize where needed
- 34. Lean Architecture Principles 1.Always involved 2.Travel light 3.Think big, act small 4.All hands on deck early on 5.Just in time, just enough 6.Architecture initiated by business goals 7.Focus on the value stream 8.Comprehendible over comprehensiveness 9.Incremental development of architecture 10.Architecture emerging from projects 11.Freedom where possible, standards where needed
- 35. Lean Architecture Process 35
- 36. Scrum based development Daily Scrum Meeting Product Backlog 2 week sprint Potentially Shippable Product Sprint Increment planning Sprint Backlog
- 37. Kanban based Lean Architecture Architecture Kanban Board Backlog Selected Ongoing Done Architectural Deliverables Business - Vision stakeholders Operations - .... Projects 37
- 38. Architecture and Development processes Architecture Kanban Board Backlog Selected Ongoing Done Architectural Deliverables Business - Vision stakeholders Operations - .... Daily Scrum Meeting Product Backlog 2 week sprint Potentially Shippable Product Sprint Increment planning Sprint Backlog
- 39. Break 39
- 40. 40
- 41. 41
- 42. 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