Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Great Technical Architects Must Be Great Organisation Architects

750 Aufrufe

Veröffentlicht am

When we make software architecture decisions we are implicitly making choices about the design of our organisations. It's time to realise that software architecture is sociotechnical architecture.

Veröffentlicht in: Technologie
  • Als Erste(r) kommentieren

Great Technical Architects Must Be Great Organisation Architects

  1. 1. ntcoding 
 GREAT TECHNICAL ARCHITECTS MUST BE GREAT ORGANISATION ARCHITECTS Nick Tune @ntcoding
  2. 2. ntcoding
  3. 3. ntcoding Software architects are being forced to adapt by evolutionary pressures in digital product development
  4. 4. ntcoding 1. Customer Inspired
  5. 5. ntcoding TOP SOURCES OF PRODUCT IDEAS DIRECT CUSTOMER FEEDBACK 80 % TEAM BRAINSTORMING 64 % SALES TEAM 53 % EXECUTIVE ORDER 51 % * % respondents who agreed. Source: Alpha UX Product Management Insights 2017
  6. 6. ntcoding CONTINUOUS DISCOVERY & DELIVERY Discovery Track Delivery TrackCross-functional Product Team
  7. 7. ntcoding 2. Infrastructure Commoditisation
  8. 8. ntcoding “Time spent on infrastructure tasks [by devs] is time taken away from feature work — James Wen SRE at Spotify
  9. 9. ntcoding SPEED SERIOUSLY WINS High performance organisations deploy to production 46x more frequently than low performers Source: Puppet 2017 State of DevOps Report
  10. 10. ntcoding SPEED NOT ENOUGH …but it was 200x in 2016 - commoditisation of infrastructure is creating a level playing field. Value is moving up the chain.
  11. 11. ntcoding 3. Connected Experiences
  12. 12. ntcoding Seamless UX across many devices is a differentiator because the barrier to entry is at an unprecedented low
  13. 13. #1 THE ROLE OF THE ARCHITECT IN THE NEW WORLD?
  14. 14. ntcoding Website Website Website Digital Enterprise IT Business APIs Data APIs DATA Back Office Apps
  15. 15. ntcoding “The web server we will use on this project is probably older than you. — Senior Architect
  16. 16. ntcoding “Programmers are too slow. The industry is moving towards generic rules engines and BPM tools [that don’t need programmers]. — Chief Architect
  17. 17. ntcoding Website Website Website Digital Enterprise IT Business APIs Data APIs DATA Rules, BPM, ESB Back Office Apps
  18. 18. ntcoding LESSONS LEARNED • Dependencies make continuous discovery and delivery almost impossible • Functional silos result in backend teams who are not incentivised to solve user problems • Architects exacerbated the problems
  19. 19. ntcoding This new era of digital product development is a tremendous opportunity to rejuvenate the perception of architects
  20. 20. ntcoding “ ” Most horror stories in IT begin with the words “The Architect” Dan Barua @danbarua
  21. 21. ntcoding “ [Architects] have outdated programming knowledge, tend to complex solutions, reduce quality of decisions, secure their job and ‘justify’ their high salary. — Andriy Solovey @AndriySolovey
  22. 22. ntcoding “The architect role often becomes a dictator. I think the problem is terminal now - even using the term architect is so tainted it needs to be given a different name.
 — Mat McLoughlin @mat_mcloughlin
  23. 23. ntcoding Software Architect Sociotechnical Architect
  24. 24. #2 SOCIOTECHNICAL ARCHITECTURE PATTERNS
  25. 25. ntcoding BOUNDED CONTEXTS & DDD Problem domains can be broken down into cohesive contexts that encapsulate things that change together for business reasons.
  26. 26. ntcoding BOUNDED CONTEXTS & DDD Align teams with bounded contexts, and teams will have the autonomy to continuously discover and deliver.
  27. 27. ntcoding Website Website Website Digital Enterprise IT Business APIs Data APIs DATA Rules, BPM, ESB Back Office Apps
  28. 28. ntcoding BOUNDED CONTEXT HEURISTICS • Linguistic patterns • Domain expert localisation • Data cohesion
  29. 29. ntcoding UI Review API UI Case Management API UI Resubmit API UI Renegotiate API
  30. 30. ntcoding UI Review API UI Resubmit API UI Renegotiate API Case ManagementBack Office UI
  31. 31. ntcoding Bounded contexts are too low level - you need to understand bounded context types and patterns
  32. 32. ntcoding PATTERN: STABLE SEQUENTIAL PROCESS Review Resubmit Renegotiate
  33. 33. ntcoding Bounded context patterns show which teams need to be more closely aligned & with common goals
  34. 34. ntcoding PATTERN: PARTNERSHIP CONTEXT DownloadsSearch Catalogue Discovery
  35. 35. ntcoding OTHER SOCIOTECHNICAL PATTERNS • Octopus context • Centralised expertise • Bubble context • Discovery context • Lots more…
  36. 36. ntcoding Architects can lead the discovery and documentation of sociotechnical architecture patterns - especially at scale
  37. 37. #3 ARCHITECTING THE SYSTEM OF WORK
  38. 38. ntcoding Architects design for compile time and runtime - flow (of work) is not even on our radar
  39. 39. ntcoding THEORY OF CONSTRAINTS The performance of an organisation is limited by constraints. Remove the constraints to improve performance of the organisation.
  40. 40. ntcoding Website Website Website Digital Enterprise IT Business APIs Data APIs DATA Rules, BPM, ESB Back Office Apps
  41. 41. ntcoding
  42. 42. ntcoding Find boundaries that eliminate constraints (the most costly bottlenecks)
  43. 43. ntcoding SITUATIONAL AWARENESS Use different sociotechnical architecture patterns at different stages of the product innovation lifecycle
  44. 44. ntcoding INNOVATION PORTFOLIO
  45. 45. #5 THE SOCIOTECHNICAL ARCHITECT’S TOOLBOX
  46. 46. ntcoding EVENT STORMING • Discover bounded contexts • Identify bounded context patterns • Discover bottlenecks • Coach teams & execs
  47. 47. ntcoding VALUE STREAM MAPPING • Discover bottlenecks • Quantify cost of bottlenecks • Coach teams & execs
  48. 48. ntcoding CONTEXT MAPPING • Visualise sociotechnical architecture patterns • Explore multiple models • Coach teams & execs
  49. 49. ntcoding LEAN UX • Master continuous discovery • Champion user needs • Coach teams & execs
  50. 50. #5 BECOMING A SOCIOTECHNICAL ARCHITECT…
  51. 51. ntcoding Value is moving up the chain. Architecting software systems in isolation is harmful. We must adapt.
  52. 52. ntcoding HOW TO ADAPT • Software architect -> sociotechnical architect • Discover and share patterns • Dictator -> 
 advisor/facilitator/coach
  53. 53. ntcoding LETS REPAIR THE IMAGE OF ARCHITECTS…
  54. 54. ntcoding MORE… ntcoding.co.uk/workshops ntcoding.co.uk/blog ntcoding.co.uk/speaking @ntcoding /in/ntcoding

×