This document discusses lean architecture principles for software development. It addresses stakeholders' needs including end users, business analysts, product owners, and deployment teams. The lean approach advocates for just-in-time delivery, starting development early, and communicating through APIs and domain-specific languages. This lean architecture aims to avoid risks and delays associated with traditional "80s style" development practices.

1. Lean Architecture
Christophe Marchal | Software architect

2. A couple of links
christophe.marchal@ilegra.com
@toff63
http://github.com/toff63
http://francesbagual.net

3. Who knows what is Lean?

4. Architecture
versus
Design?

5. Form

6. Requirement
Stakeholders
● end user
● business analyst
● product owner
● deployment team
● developers

8. Flat needs to be mobile

9. Risks

10. The 80s way

11. Development waiting ...

12. The Agile way

14. The lean way

15. Just in time delivery

16. Valuable documentation

17. Valuable documentation

18. Valuable documentation

19. Development start early

20. Communicate through API

21. Communicate through DSL

22. Thank You
Christophe Marchal | Software architect