Download - Seminar Lean Architectuur June 17th, 2010
Seminar Lean Architecture
May 18th, 2010
Sander van den BergGerard JanssenDenis KoelewijnGero Vermaas
Waste
Walls
Locked down
No Architecture at all
5
Architecture can be beautifull
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•
Introduction
• Name• Role• Company• What do you expect from todays seminar?
• And all of this in 30 seconds
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
• 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
Lean principes
Base your management decisions on a long-term philosophy, even at the
expense of short-term financial goals
15
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.
Use visual control so no problems are hidden
Grow leaders who thoroughly understand the work, live the
philosophy, and teach it to others
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
25
What is Kanban?
•Kan = Visual
•Ban = Board•
Make Work Visible
Limit Work in Progress
Make the work flow
Interactive part: Architectural challenges
• Which Architectural challenges are 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
Architecture initiated by business goals
Architecture emerging from projects
36
Incremental development of
Focus on Value Stream
Travel Light
Just in Time, Just Enough
Think Big, Act Small
All hands on deck early on
Always Involved
Comprehensible over comprehensiveness
Freedom where possible, standardize where needed
Lean Architecture Principles
1.Architecture initiated by business goals2.Architecture emerging from projects3.Incremental development of architecture4.Focus on the value stream5.Travel light6.Just in time, just enough7.Think big, act small8.All hands on deck early on9.Always involved10.Comprehensible over comprehensiveness11.Freedom where possible, standards where needed
Lean Architecture Process
46
Product Backlog
SprintBacklog
PotentiallyShippableProduct
Increment
2 week sprint
Daily ScrumMeeting
Sprintplanning
Demo
Retrospective
Scrum based development: basic Scrum
Product Backlog
SprintplanningNursery
New card Elementary School
Jr. highSchool
HighSchool
Definition ofReady
Scrum based development:
Architecture Kanban Board
- Vision - ....
ArchitecturalDeliverables
stakeholdersBusiness
OperationsProjects
Backlog Selected Ongoing Done
49
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
Demo
Retrospective
Nursery
New card Elementary School
Jr. highSchool
HighSchool
Definition ofReady
Architecture and Development processes
Break
51
52
53
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