Growing IT products over building them. Cornel FATULESCU CTO Pentalog, Manager Pentalog Institute

Size: px

Start display at page:

Download "Growing IT products over building them. Cornel FATULESCU CTO Pentalog, Manager Pentalog Institute"

Emil Parrish
8 years ago
Views:

1 Growing IT products over building them Cornel FATULESCU CTO Pentalog, Manager Pentalog Institute

2 Why this topic? The vast majority of problems in business (including development) are so basic that a key solution is education in and consistent use of simple and enjoyable thinking action tools 2

3 Why this topic? Several agile practices are easier to understand: continuous integration, iterations but completely changing the mindset is difficult 3

4 Why this topic? we solve our problems with the same way of thinking we used when we created them? Albert Einstein 4

5 Why this topic? Design patterns are reusable solutions to commonly occurring problems in software design. 5

6 Why this topic? Fred Brooks - No Silver Bullet : 1986 The building metaphor has outlived its usefulness. It is time to change again. If, as I believe, the conceptual structures we construct today are too complicated to be specified accurately in advance, and too complex to be built faultlessly, then we must take a radically different approach. Let us turn nature and study complexity in living things, instead of just the dead works of man. Here we find constructs whose complexities thrill us with awe. The brain alone is intricate beyond mapping, powerful beyond imitation, rich in diversity, self-protecting, and selfrenewing. The secret is that it is grown, not built. So it must be with our software systems. Some years ago Harlan Mills proposed that any software system should be grown by incremental development. 6

different approach. Let us turn nature and study complexity in living things, instead of just the dead works of man. Here we find constructs whose complexities thrill us with awe.

7 Why this topic? Gardening over architecting 7

8 Several things you must know!

9 Galbraith s Star Model 9

10 Theory X VS Theory Y Douglas McGregor

11 Theory X Theory X 11

12 Theory Y Theory Y 12

13 Douglas McGregor, in The Human Side of Enterprise (1960) The effectiveness of organizations could be at least doubled if managers could discover how to tap into the unrealized potential present in their workforces. 13

least doubled if managers could discover how to tap

14 Sequential VS Parallel 14

15 Sequential 15

16 Parallel 16

17 Feedback & Adaptability Agile Manifesto Lean wastes checklist 17

18 Batch size 18

19 Gardening over Architecting 19

20 Gardening over Architecting What is the architecture of the product? We always have: An intended architecture Real architecture 20

21 Real Architecture The only software documentation that actually seems to satisfy the criteria of an engineering design is the source code 21

22 Tools for Gardening over Architecting Le mieux est l'ennemi du bien. (The best is the enemy of the good) Voltaire The first law of diagramming: model to have a conversation The best modeling tool? White board! Design workshops JIT Modeling Coaching 22

23 Must be considered The sum of all the source code is the true design blueprint of software architecture The real software architecture evolves (better or worse) every day of the product, as people do programming The real living architecture needs to be grown every day through acts of programming by master programmers A software architect who is not in touch with the evolving source code of the product is out of touch with reality Every programmer is some kind of architect whether wanted or not. Every act of programming is some kind of architectural act good or bad, small or large, intended or not. 23

24 Gardening over architecting Avoid: Architecture astronauts Conformance to outdated architectural decisions Don't model advice for extremists Approval reviews by experts at the end of a step Create 'design' and then send them for offshore implementation 24

25 Gardening over architecting Try: Very early, prototype technical solution with tracer code Incrementally build 'vertical' architectural slices of customer-centric features Do customer-centric features with major architectural impact first Architects hand off to 'coders' Test on old and featured platforms as soon as possible 25

26 Gardening over architecting Try: Design review workshops Technical leaders teach during code reviews Design/architecture community of practices Show-and-tell during workshops 26

27 Gardening over architecting Try: Component guardians for architectural integrity when shared code ownership Component mailing lists Internal open source with teachers Configurable design for customization Architectural and design practices Promote a shared pattern vocabulary 27

28 Gardening over architecting Avoid: Using stubs to delay integration Big upfront interface design Freezing interfaces 28

29 Gardening over architecting Try: HTML-ize and hyperlink your entire source code, daily Lots of stubs, plus dependency injection Test-driven development for a better architecture Dependency injection framework Use an OS abstraction layer 29

30 Gardening over architecting Try: Create a low-level hardware abstraction layer API Create simulation layer for hardware,etc Start with some weakly-typed interfaces, then strengthen 30

31 Q&A? 31

Chapter Thinking About Design 282 Behavior-Oriented Tips 289 Technically Oriented Tips 317 Introduction to Interfaces and Interactions Tips 323

Chapter Thinking About Design 282 Behavior-Oriented Tips 289 Technically Oriented Tips 317 Introduction to Interfaces and Interactions Tips 323 Scaling Lean & Agile Development Thinking and Organizational