seminar lean architecture may 18th 2010
DESCRIPTION
Slidedeck of the Lean Architecture seminar hosted by Xebia on May 18th, 2010TRANSCRIPT
Seminar Lean Architectuur
May 18th, 2010Gerard JanssenDenis KoelewijnGero Vermaas
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•
Introduction
• Name• Role• Company• What do you expect from todays seminar?
Why Architecture?
3 C’s of Architecture
Connection Cohesion
Changeability
Architecture
Lean
Any use of resources for a purpose that is not adding value for the end customer is waste and should be
removed
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
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).
Kanban
15
What is Kanban?
•Kan = Visual
•Ban = Board•
Interactive part: Architectural challenges
• Which Architectural challenges is your organization facing?
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
Lean Architecture Principles
Principle #1: Always Involved
Principle #2: Travel Light
Principle #3: Think Big, Act Small
Principle #4: All hands on deck early on
Principle #5: Just in Time, Just Enough
Principle #6: Architecture initiated by business goals
Principle #7: Focus on Value Stream
Principle #8: Comprehendible over comprehensiveness
31
Principle #9: Incremental development of architecture
Principle #10: Architecture emerging from projects
Principle #11: Freedom where possible, standardize where needed
Lean Architecture Principles
1.Always involved2.Travel light3.Think big, act small4.All hands on deck early on5.Just in time, just enough6.Architecture initiated by business goals7.Focus on the value stream8.Comprehendible over comprehensiveness9.Incremental development of architecture10.Architecture emerging from projects11.Freedom where possible, standards where needed
Lean Architecture Process
35
Product Backlog
SprintBacklog
PotentiallyShippableProduct
Increment
2 week sprint
Daily ScrumMeeting
Sprintplanning
Scrum based development
Architecture Kanban Board
- Vision - ....
ArchitecturalDeliverables
stakeholdersBusiness
OperationsProjects
Backlog Selected Ongoing Done
37
Kanban based Lean Architecture
Product Backlog
SprintBacklog
PotentiallyShippableProduct
Increment
2 week sprint
Daily ScrumMeeting
Sprintplanning
Architecture Kanban Board
- Vision - ....
ArchitecturalDeliverables
stakeholdersBusiness
Operations
Backlog Selected Ongoing Done
Architecture and Development processes
Break
39
40
41
References
• Xebia Bloghttp://blog.xebia.com/category/lean-architecture/
• “Lean Architecture” Linked In Grouphttp://www.linkedin.com/groups?home=&gid=2891065
• September 2010: Lean Architecture Open Space Conference