Lean Architecture

I used this presentation to kick off an interactive workshop on the topic.

See http://shishkin.org/slides/lean-architecture.html for an HTML version.

Transcript

1. LEAN ARCHITECTURE LEARN FAST, LEARN OFTEN
2. WHAT IS ARCHITECTURE? high-level structure of a system decisions which are hard to change
3. WE DON’T NEED ARCHITECTURE only working software counts all decisions should be revertable (easily) vague decisions at large (blueprints) lost in details
4. WE DO NEED ARCHITECTURE shorten the feedback loop shared understanding make decisions explicit
5. ARCHITECTURE IS “WHATEVER THE IMPORTANT STUFF IS”
6. OK, BUT HOW?
7. IT HURTS, SO WE DO IT OFTEN
8. ARCHITECTURE IS EVERYONE’S JOB
9. LEVERAGE THE DOMAIN POSTPONE TECHNOLOGY
10. FOCUS ON LEARNING (known unknowns)
11. PRACTICE PRACTICE PRACTICE PRACTICE
12. ONE OF MANY WAYS
13. 1. IDENTIFY ACTORS human users, components and external systems derive actors from the functional domain
14. 2. DRAW DATA FLOWS derive interfaces from data, not the other way around split heterogeneous data be specific
15. 3. GET FEEDBACK biz and tech risks data volumes security and privacy validate assumptions infrastructure operations costs estimation technology choice and … and … and …
16. 4. ZOOM IN AND REPEAT
17. LET’S TRY IT!
18. BUT IN THE REAL WORLD… aim for smaller increments work from priorities know when to stop! YMMV our job is to create the “real world” — Ron Jeffries
19. SUMMARY 1. functional components are more stable 2. maximize learning over effort 3. practice often
20. THANK YOU! shishkin.org @sshishkin