Lean Architecture University Session for NLJUG at Xebia on July 8th, 2010

859 views

Published on

Slidedeck of the Lean Architecture University Session for the Dutch Java User Group (NLJUG) that was hosted at Xebia.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
859
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
15
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Lean Architecture University Session for NLJUG at Xebia on July 8th, 2010

  1. 1. NLJUG University Lean Architectuur Sander van den Berg Gerard Janssen July, 8th, 2010 Denis Koelewijn Gero Vermaas
  2. 2. Waste
  3. 3. Walls
  4. 4. Locked down
  5. 5. Architecture? Where? 5
  6. 6. Architecture can be beautifull
  7. 7. Agenda • Introduction • Lean Architecture - part 1 • Business and process principles • Mobile Food Finder case • Lean Architecture - part 2 • Artifact priciples • Workshop • Lean Architecture - part 3 • Communication principles • Workshop • Wrap up
  8. 8. Introduction • Name • Role • Company • What do you expect from todays seminar? • And all of this in 30 seconds
  9. 9. Why Architecture?
  10. 10. 3 C’s of Architecture Connection Cohesion Architecture Changeability
  11. 11. Lean
  12. 12. Lean Manufacturing Essence Any use of resources for a purpose that is not adding value for the end customer is waste and should be removed
  13. 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. 14. 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
  15. 15. 11 Lean Architecture Principles 1. Business 2. Process 3. Artifacts 4. Communication 15
  16. 16. Business Principles 16
  17. 17. Business Principle: Architecture initiated by business goals
  18. 18. Business Principle: Focus on Value Stream
  19. 19. Process Principles 19
  20. 20. Process Principle Think Big, Act Small
  21. 21. Process Principle: Just in Time, Just Enough
  22. 22. Process Principle: Incremental development of architecture 22
  23. 23. Kanban Board
  24. 24. 24
  25. 25. The Mobile Food Finder A Case in two Acts
  26. 26. Achtergrond
  27. 27. We are ByrdCo, a joint venture of Yellow Pages and Cornucopia Yellow Pages Co. Cornucopia Investors Parent Investor ByrdCo
  28. 28. Our company vision Freedom through information
  29. 29. We have a Product Vision for our initial product: Mobile Food Finder For people on the road who need to find a restaurant the Mobile Food Finder is a mobile application that finds a nearby restaurant. Unlike other food finders our product is backed by a marketplace that brings restaurants and guests together.
  30. 30. Long term: CEO’s Plan for World Domination 1: Grab market share 2: Advertising 3: Reservation outsourcing
  31. 31. Short term: we need to prove we are a viable business • Will host anything • 3 months initial investment necessary on their • Go/No Go for further infrastructure investment 3 months after live 1 May 15 Jan Go Live Now 1 Feb 1 July Start development Go/No Go
  32. 32. These are the stakeholders for our Mobile Food Finder Restaurant Guest Restaurant Owner Parent Reviewer Corporation Mobile Food Finder Investor Party Organizer
  33. 33. These are the requirements for Restaurant Guests Requirement Navigation & Location based filtering Filtering on restaurant details (menu, opening times, ambiance...) Ratings & Reviews Dietary needs (vegetarian, halal, lactose free...) Support making reservations Organize party Save money Photo and Video in restaurant recommendations
  34. 34. These are the requirements for Restaurant Owners Pimp my restaurant details (Menu) promotions Insight in hit/click-through statistics for my restaurant Identify user Sponsored promotion Reservation system Pay subscription
  35. 35. Architectural Context - iPhone client for Restaurant Guests - Web Client for Restaurant Owners - Contract for data updates: basic restaurant info and location info (batchfiles) - For now, need to integrate into mother company IT (corp security constraints are an issue)
  36. 36. Existing Infrastructure
  37. 37. Artifact Principles 38
  38. 38. Artifacts Principle: Comprehensible over comprehensiveness
  39. 39. Artifacts Princpiple: Freedom where possible, standardize where needed
  40. 40. Artifacts Principle: Travel Light
  41. 41. 42
  42. 42. Act 1
  43. 43. Assignment: create vision (and arch backlog?)
  44. 44. Architecture Vision Constraints A3 This goes on:
  45. 45. Architecture Backlog
  46. 46. Communication Principles 48
  47. 47. Architecture emerging from projects
  48. 48. Always Involved
  49. 49. All hands on deck early on
  50. 50. 52
  51. 51. Act 2
  52. 52. We have found that we are ahead in the dietary needs space Intolerances Dieting Ideological / Religious
  53. 53. We have revised our Product Vision For people on the road who need to find a restaurant the Mobile Food Finder is a mobile application that finds a nearby restaurant. Unlike other food finders our product will support people in their dietary needs.
  54. 54. These are the stakeholders for our Mobile Food Finder Restaurant Guest Restaurant Owner Parent Corporation Mobile Food Finder Investor
  55. 55. Architectural Context 2 - Need to integrate with Weight Watchers IT - Need to decouple from mother company IT infrastructure

×