Your SlideShare is downloading. ×
Seminar Lean Architecture May 18th 2010
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Seminar Lean Architecture May 18th 2010

1,427
views

Published on

Slidedeck of the Lean Architecture seminar hosted by Xebia on May 18th, 2010

Slidedeck of the Lean Architecture seminar hosted by Xebia on May 18th, 2010

Published in: Technology, News & Politics

1 Comment
1 Like
Statistics
Notes
  • This presentation was used at Xebia's Lean Architecture workshop on May 18th 2010.
    Also check out the Lean Architecture group on LinkedIn where we share knowledge about Lean Architectuur
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
1,427
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
55
Comments
1
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Seminar Lean Architectuur Gerard Janssen May 18th, 2010 Denis Koelewijn Gero Vermaas
  • 2. 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 •
  • 3. Introduction • Name • Role • Company • What do you expect from todays seminar?
  • 4. Why Architecture?
  • 5. 3 C’s of Architecture Connection Cohesion Architecture Changeability
  • 6. Lean
  • 7. Any use of resources for a purpose that is not adding value for the end customer is waste and should be removed
  • 8. 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
  • 9. 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).
  • 10. Kanban
  • 11. What is Kanban? • Kan = Visual • Ban = Board • 15
  • 12. Interactive part: Architectural challenges • Which Architectural challenges is your organization facing?
  • 13. 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
  • 14. Lean Architecture Principles
  • 15. Principle #1: Always Involved
  • 16. Principle #2: Travel Light
  • 17. Principle #3: Think Big, Act Small
  • 18. Principle #4: All hands on deck early on
  • 19. Principle #5: Just in Time, Just Enough
  • 20. Principle #6: Architecture initiated by business goals
  • 21. Principle #7: Focus on Value Stream
  • 22. Principle #8: Comprehendible over comprehensiveness
  • 23. Principle #9: Incremental development of architecture 31
  • 24. Principle #10: Architecture emerging from projects
  • 25. Principle #11: Freedom where possible, standardize where needed
  • 26. 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
  • 27. Lean Architecture Process 35
  • 28. Scrum based development Daily Scrum Meeting Product Backlog 2 week sprint Potentially Shippable Product Sprint Increment planning Sprint Backlog
  • 29. Kanban based Lean Architecture Architecture Kanban Board Backlog Selected Ongoing Done Architectural Deliverables Business - Vision stakeholders Operations - .... Projects 37
  • 30. 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
  • 31. Break 39
  • 32. 40
  • 33. 41
  • 34. 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

×