Sections. ! Introduction. ! Development Activities. ! Dealing with Technical Debt. ! Bonus: How to become an Agile Architect

Transcription

1

2

3 Me

4 Sections! Introduction! Development Activities! Dealing with Technical Debt! Bonus: How to become an Agile Architect

5

6 Agile! Lean! Value Stream! Discipline! Embrace Change

7 Architecture! Everything that is expensive to change, Fowler! Three basic elements! Responsibility, Dependency, Interaction! CRC Class-Responsibility-Collaboration

8 Design! Domain analysis! [Domain-Driven Design]! Or how to find the responsibilities? [POSA 5]! Optimizations for Qualities shape the design! Merge & split responsibilities! Deployment of responsibilities! New dependencies new interactions! Aligning the design with technology

9 Architect! Technical Leadership 1. Communication 2. Consistency 3. Coaching 4. Coding

10 Complexity / Simplicity! Dependencies! Constraints! Coupling & Cohesion! Terms are relative

11 Change! The only constant is change! Requirements change! Technology changes! Business changes! People change! Ability to react on Change depends on the Architecture

12 Mindset! Embrace change Embrace uncertainty [North]! YAGNI! Fail fast learn fast! Systems live longer than we expect! Example Millennium bug! Introduction of SW products well planed, but Removal/de-installation not planed

13 Managing Change! Control complexity! Look ahead! Isolate! Do not prepare! Do not prohibit! Trade-off: Cost, time, benefit

14 Can you plan?! what you know! Vision vs. Debt! Mobile devices are a fact.! what you guess! Cloud relevance for your product?! what you hope! Technology bets: Will Windows Phone 8 catch on?

15 Size Matters! From: Small Local Team! To: Dispersed Global Teams

16

17 Vision! Demand a product vision or! Write one and ask for confirmation! Align all stakeholders! Say what it is! Say what it is NOT! Baseline on where you are incl. your technical debt

18 Requirements! Remember: Fail fast. This is your first chance!! Domain language! Feature model! Complete! Hierarchical! Domain knowledge! Managing Variability

19 Backlog! Contains! Customer features! Refactoring & Redesigns! Governance! Everything that makes a team busy! Prioritized by Product Owner and Architect

20 Governance! In general: Protect your Qualities! Developmental! Operational! In this talk: Flexibility, Extensibility, Maintainability! You can only plan with what you control

21 Governance Example Rules & Guidelines Variability Management " Framework usage " Commonality/Variability analysis " Extension points " Consistency " Complexity " Extensibility Preventive Reference Architecture Concept Reviews " Component types " Allowed dependencies " Consistency " Maintainability " Peer review of critical changes " Sustainability " Performance, etc. Static Code Checkers " Coding guidelines " Dependencies, API violations " Stability " Performance Preventive Tests " Unit tests " Integration &Smoke Tests " Stability Corrective Corrective Tests Architecture Review " Integration Tests " Staged multi-client-multi-modality tests " Performance Tests " ATAM review " Plan big picture course corrections " Stability " Performance " Update-ability " Sustainability " Extensibility " Maintainability Guiding principle: Fail fast! Always running system, Continuous Integration, Gated Check-in, Staged testing, Continuous System Test

22 Technology! One of the hardest things to change! Isolation recommended! Check out Quasar [sd&m, J. Siedersleben]

23 Coupling & Cohesion! Decouple only where you expect change! Inversion of control! Dependency injection! Protocols, Standards, etc.

24 Patterns! Structure! Initial Context! Problem with Forces! Solution with Consequences! Resulting Context! Careful usage: Resulting context should be positive!! Pattern-Oriented-Software Architecture [POSA]

25 Test! No Test = No Change! Interplay of test layers! Unit Tests incl. Mock! Smoke Tests! Automated System Tests

26 Quality! What you do not measure, you do not know.! Quality is relative! Define your quality model! Base is the product quality tree! Align the rules with the qualities! Derive your Code Checker Rules and their Criticality

27 Performance! No Test, No Trending = No Protection! Worry about it later is typically the wrong strategy! Instead define it up front: Quality Model/Tree! Continuously trend it

28 Documentation! Design decisions as first class citizen [Jan Bosch]! Minimum:! Assumptions / Constraints! Alternatives! Rationale! Decision! Architects use also written words to lead [Writing with Style]

29 Examples! Example: Sync via Dropbox vs. icloud! Staying in control! Example: System Integration! Decoupling release lifecycles

30

31 Technical Debt! Identification! Explicit business drivers! Quality tree incl. scenarios! Assessment [ATAM]! Mapping risks to business drivers & scenarios

32 Arguing for Big Change! Impact & Consequences! Big Picture Vision! Business Case! Difficult but sometimes necessary

33 Introducing Big Change! Plan! Communicate broadly esp. upwards! Step-wise! Limit risk! Gain confidence! Celebrate successes

34 Examples! Example: Re-implementation! Workflow module! Example: Changing paradigms! Data loading strategy

35

36 How to become an Agile Architect! Know how! Easy to gather! Experience! Time will teach! Capabilities! Hard to change Identify the need for each individual architect.

37 Know How! Agile / Lean! Test Driven Development! Architecture! Technologies

38 Experiences! Architecture Reviews! Code Reading! Patterns! Great frameworks [Cocoa]! Communities

39 Capabilities! Communication! Feedback! Leadership (Styles)! Coaching (Peer-to-Peer)

40