SlideShare a Scribd company logo
Information | Analytics | Expertise
© 2016 IHS @AGILECHRISYYC
Chris Edwards P.Eng., Senior Manager
Chris.Edwards@ihs.com
@AgileChrisYYC
THE AGILE ARCHITECT
A Case Study in Transformational Leadership
MARCH 2016
© 2016 IHS @AGILECHRISYYC
disclaimer:
this is not a talk about
architecture
2
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC
what is the role of an
architect in an agile
organization?
3
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC
your mileage
may vary
4
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC
Setting the Stage • 5 teams, 5-9 each (including QA)
• Mix of Scrum/Kanban/Scrumban
• Thick Client
• C++
• Mature Codebase
• Recently Adopted Agile
• Major Project – Client / Server
5
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC
The best architectures,
requirements, and designs
emerge from self-organizing
teams.
6
The Agile Architect / March 2016
Agile Manifesto
© 2016 IHS @AGILECHRISYYC
Architecture
Approach 1:
Laissez Faire
7
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC 8
The Agile Architect / March 2016
HELP!!!
© 2016 IHS @AGILECHRISYYC
Build projects around motivated
individuals. Give them the
environment and support they need,
and trust them to get the job done.
9
The Agile Architect / March 2016
Agile Manifesto
© 2016 IHS @AGILECHRISYYC
empowerment is more
than just taking your
hands off the wheel
10
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC
how do we incorporate
an architect…
without sacrificing
agile values?
11
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC
Wanted to avoid this:
12
The Agile Architect / March 2016
Requirements
Design
Code
Test
Deploy
© 2016 IHS @AGILECHRISYYC
And this:
13
The Agile Architect / March 2016
cliparthut.com
© 2016 IHS @AGILECHRISYYC
Architecture
Approach 2:
The Architecture
Scout
14
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC 17
The Agile Architect / March 2016
Architecture by Example
”“
© 2016 IHS @AGILECHRISYYC 18
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC 19
The Agile Architect / March 2016
Too many classes makes
the system too complex!
Big classes make the
system unmaintainable!
© 2016 IHS @AGILECHRISYYC 20
The Agile Architect / March 2016
WORK HARDER!
© 2016 IHS @AGILECHRISYYC
what if the
architect is
WRONG?
21
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC
how do you know
if the architect
is WRONG?
22
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC 23
The Agile Architect / March 2016
I thought you knew
something I didn’t
”
“
© 2016 IHS @AGILECHRISYYC
architect is a
leadership role
24
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC
The Agile Architect / March 2016
xkcd.com
25
© 2016 IHS @AGILECHRISYYC 27
The Agile Architect / March 2016
Image Source: worklifematters.net
Spotify Engineering Videos
© 2016 IHS @AGILECHRISYYC
how do I serve the
teams without telling
them what to do?
28
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC
Intent Based
Leadership
29
The Agile Architect / March 2016
Rob van Hilten, Flickr
© 2016 IHS @AGILECHRISYYC 30
The Agile Architect / March 2016
Don’t move information to authority,
move authority to the information
”
“ David Marquet
© 2016 IHS @AGILECHRISYYC 31
The Agile Architect / March 2016
Image Source: worklifematters.net
© 2016 IHS @AGILECHRISYYC 32
The Agile Architect / March 2016
two pillars that need to be in place:
the technical competence …. and organization clarity.
… put those things in place
and then you can give control.
”
“
David Marquet
© 2016 IHS @AGILECHRISYYC
i intend to…
33
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC 34
The Agile Architect / March 2016
Image Source: worklifematters.net
Spotify Engineering Videos
© 2016 IHS @AGILECHRISYYC
Architecture
Approach 3:
The Architecture
Coach
35
The Agile Architect / March 2016
Rob van Hilten, Flickr
© 2016 IHS @AGILECHRISYYC
Daily Design Meeting • 30 minutes
• Technical lead from each team
• Discuss challenges that being encountered
• Exercise is repeated on the team that brought
the challenge
36
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC 37
The Agile Architect / March 2016
Resist the urge to provide solutions.
”
“ David Marquet
© 2016 IHS @AGILECHRISYYC
questions
communicate
values
38
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC
letting go is hard
39
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC
Design Meeting
Challenges
• Jealousy from those who cannot attend
• Conflict remains between teams
• Design group seen as new design authority
40
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC 41
The Agile Architect / March 2016
organizations which design systems ... are constrained to
produce designs which are copies of the communication
structures of these organizations
”
“
M. Conway
© 2016 IHS @AGILECHRISYYC 42
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC
Architecture
Approach 3:
The Architecture
Coach
44
The Agile Architect / March 2016
Rob van Hilten, FlickrCoaching Agile Teams, Lyssa Adkins
© 2016 IHS @AGILECHRISYYC
Design Steps • What is the problem you’re trying to solve?
• What solutions should we consider?
• What are the pros/cons of each solution?
46
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC 47
The Agile Architect / March 2016
Sources: Edward de Bono,
retrospectivewiki.org
© 2016 IHS @AGILECHRISYYC
create a common framework
for resolving conflict
48
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC
disagreement is a
mechanism for
organizational clarity
49
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC
the end?
50
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC
something interesting
happened
51
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC 52
The Agile Architect / March 2016
?
© 2016 IHS @AGILECHRISYYC
do we still need an
architect?
53
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC
Final Architecture
Approach:
Architecting as a
Team
54
The Agile Architect / March 2016
Steve Jurvetson, Flickr
© 2016 IHS @AGILECHRISYYC 55
The Agile Architect / March 2016
Image Source: worklifematters.netSpotify Engineering Videos
© 2016 IHS @AGILECHRISYYC
approach must evolve
over time
57
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC
Summary • Empowerment is more than standing back
• Lead through intent
• Resist the urge to provide solutions
• Create a framework for disagreement
• Disagreement is a mechanism for
organizational clarity
58
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC
Chris Edwards
Chris.Edwards@ihs.com
@AgileChrisYYC
59
The Agile Architect / March 2016
Questions?

More Related Content

PPTX
The Agile Architect - CAMUG - Oct 1, 2015
PPTX
The Agile Architect
PPTX
Role of Architect In Agile
PDF
InVision - Portfolio Website Design
PPTX
Agile service delivery In the UK’s public sector
PPTX
Agile Project Management - a Coronavirus Perspective 2019
PDF
Sub decree no77 on the duties and general structure of the royal gendarmerie ...
PPTX
#Spscalgary 2016 Setting up your release pipeline for SharePoint in Azure
The Agile Architect - CAMUG - Oct 1, 2015
The Agile Architect
Role of Architect In Agile
InVision - Portfolio Website Design
Agile service delivery In the UK’s public sector
Agile Project Management - a Coronavirus Perspective 2019
Sub decree no77 on the duties and general structure of the royal gendarmerie ...
#Spscalgary 2016 Setting up your release pipeline for SharePoint in Azure

What's hot (12)

PPTX
#Spscalgary 2016 Make Graph Data useful for you company
PDF
An introduction to chaos engineering as part of DevOps at XP2019
PDF
An introduction to agile and beyond
PDF
O365Engage17 - SharePoint Migration Tips from a Superhero
PDF
Agile governance, 19th February 2015
PDF
APM Thames Valley - The new (slim) APM guide on 'Agile Governance' from GovSIG
PDF
2109 apb-micas-2015
PDF
ImmobilienScout24 - Introduction and use of agile methods for software develo...
PPTX
GRUG 2.0 7 August Opening presentation 20180809
PPTX
GRUG 11 AU2012 gunslinger presentation 20130220
PPTX
Ignite Talk: Continuous Delivery: Why Everyone Should Do It
#Spscalgary 2016 Make Graph Data useful for you company
An introduction to chaos engineering as part of DevOps at XP2019
An introduction to agile and beyond
O365Engage17 - SharePoint Migration Tips from a Superhero
Agile governance, 19th February 2015
APM Thames Valley - The new (slim) APM guide on 'Agile Governance' from GovSIG
2109 apb-micas-2015
ImmobilienScout24 - Introduction and use of agile methods for software develo...
GRUG 2.0 7 August Opening presentation 20180809
GRUG 11 AU2012 gunslinger presentation 20130220
Ignite Talk: Continuous Delivery: Why Everyone Should Do It
Ad

Viewers also liked (18)

PPTX
Agile software development and UML
PPT
Introduction to Agile & Scrum
PDF
Introduction to Agile & Scrum
PPT
Introduction to Agile & Scrum
PDF
Introduction to Agile & Scrum
PPT
Introduction to Agile & Scrum
PDF
Flexidata profile EN software
PDF
BizDevOps - Necessity or Just Nice?
PDF
Less is More!
PDF
Its Organizational, Not Individual Intelligence that matters!
PPT
Introduction to Agile & Scrum
PDF
Art of agile coaching
PDF
Beyond the Scrum Master - Becoming an Agile Coach
PPTX
Becoming an Agile Coach
PDF
Great ScrumMaster
PPTX
New Lean-Agile Coach self-assessment - levels description v3.2
PDF
Agile Coaching Workshop
PPTX
New Lean-Agile Coach self-assessment radars v3.2
Agile software development and UML
Introduction to Agile & Scrum
Introduction to Agile & Scrum
Introduction to Agile & Scrum
Introduction to Agile & Scrum
Introduction to Agile & Scrum
Flexidata profile EN software
BizDevOps - Necessity or Just Nice?
Less is More!
Its Organizational, Not Individual Intelligence that matters!
Introduction to Agile & Scrum
Art of agile coaching
Beyond the Scrum Master - Becoming an Agile Coach
Becoming an Agile Coach
Great ScrumMaster
New Lean-Agile Coach self-assessment - levels description v3.2
Agile Coaching Workshop
New Lean-Agile Coach self-assessment radars v3.2
Ad

Similar to The Agile Architect - Agile India 2016 (19)

PPTX
Agile Architect - Turning Followers into Leaders
PDF
Delivery Mindsets from Stone Age to devops
PDF
Project management from stone age to dev ops developerweek - ny 2017
PDF
Hackathon a new addition to the agile toolbox @Dailymotion - Ilaria Fazio, Ma...
PPTX
Making Faster UX in an Agile World - HOAPitt 2017
PDF
2017 12-01 aOS Aachen - Biggest fails and best practices using Office 365
PDF
Presentation scrum agile methodology
PPTX
aOS Day Brussels December 2016
PDF
Design for perfect scrum day kiev 2017
PDF
SharePoint Branding - Kevin Riahi & Preetee HURCHAND-BEEFEYA
PPTX
aOS 2017 Mauritius SharePoint Branding
PDF
The GIS Capability Maturity Model Maximize Benefits from Enterprise GIS Opera...
PPTX
Working with legacy content (UA Europe 2016)
PDF
The Value of Content Design: CSForum 2016
PDF
SPUnite17 Transforming your Organisation into a Digital Workplace
PPTX
We (don't) need a software architect!?!
PDF
2016 12-05 aOS Brussels - Latest wonders of SharePoint and Office 365
PPTX
The Numbers Game
PDF
A Holistic BIM Framework for Structural Engineering Practices in Hong Kong - ...
Agile Architect - Turning Followers into Leaders
Delivery Mindsets from Stone Age to devops
Project management from stone age to dev ops developerweek - ny 2017
Hackathon a new addition to the agile toolbox @Dailymotion - Ilaria Fazio, Ma...
Making Faster UX in an Agile World - HOAPitt 2017
2017 12-01 aOS Aachen - Biggest fails and best practices using Office 365
Presentation scrum agile methodology
aOS Day Brussels December 2016
Design for perfect scrum day kiev 2017
SharePoint Branding - Kevin Riahi & Preetee HURCHAND-BEEFEYA
aOS 2017 Mauritius SharePoint Branding
The GIS Capability Maturity Model Maximize Benefits from Enterprise GIS Opera...
Working with legacy content (UA Europe 2016)
The Value of Content Design: CSForum 2016
SPUnite17 Transforming your Organisation into a Digital Workplace
We (don't) need a software architect!?!
2016 12-05 aOS Brussels - Latest wonders of SharePoint and Office 365
The Numbers Game
A Holistic BIM Framework for Structural Engineering Practices in Hong Kong - ...

Recently uploaded (20)

PDF
Adobe Premiere Pro 2025 (v24.5.0.057) Crack free
PDF
Wondershare Filmora 15 Crack With Activation Key [2025
PPTX
Oracle E-Business Suite: A Comprehensive Guide for Modern Enterprises
PDF
Digital Strategies for Manufacturing Companies
PDF
Audit Checklist Design Aligning with ISO, IATF, and Industry Standards — Omne...
PDF
Which alternative to Crystal Reports is best for small or large businesses.pdf
PDF
SAP S4 Hana Brochure 3 (PTS SYSTEMS AND SOLUTIONS)
PDF
2025 Textile ERP Trends: SAP, Odoo & Oracle
PPTX
Agentic AI Use Case- Contract Lifecycle Management (CLM).pptx
PDF
Upgrade and Innovation Strategies for SAP ERP Customers
PDF
EN-Survey-Report-SAP-LeanIX-EA-Insights-2025.pdf
PDF
System and Network Administration Chapter 2
PDF
Nekopoi APK 2025 free lastest update
PPTX
VVF-Customer-Presentation2025-Ver1.9.pptx
PDF
Softaken Excel to vCard Converter Software.pdf
PDF
medical staffing services at VALiNTRY
PPTX
Transform Your Business with a Software ERP System
PPTX
Reimagine Home Health with the Power of Agentic AI​
PDF
Navsoft: AI-Powered Business Solutions & Custom Software Development
PDF
How to Migrate SBCGlobal Email to Yahoo Easily
Adobe Premiere Pro 2025 (v24.5.0.057) Crack free
Wondershare Filmora 15 Crack With Activation Key [2025
Oracle E-Business Suite: A Comprehensive Guide for Modern Enterprises
Digital Strategies for Manufacturing Companies
Audit Checklist Design Aligning with ISO, IATF, and Industry Standards — Omne...
Which alternative to Crystal Reports is best for small or large businesses.pdf
SAP S4 Hana Brochure 3 (PTS SYSTEMS AND SOLUTIONS)
2025 Textile ERP Trends: SAP, Odoo & Oracle
Agentic AI Use Case- Contract Lifecycle Management (CLM).pptx
Upgrade and Innovation Strategies for SAP ERP Customers
EN-Survey-Report-SAP-LeanIX-EA-Insights-2025.pdf
System and Network Administration Chapter 2
Nekopoi APK 2025 free lastest update
VVF-Customer-Presentation2025-Ver1.9.pptx
Softaken Excel to vCard Converter Software.pdf
medical staffing services at VALiNTRY
Transform Your Business with a Software ERP System
Reimagine Home Health with the Power of Agentic AI​
Navsoft: AI-Powered Business Solutions & Custom Software Development
How to Migrate SBCGlobal Email to Yahoo Easily

The Agile Architect - Agile India 2016

  • 1. Information | Analytics | Expertise © 2016 IHS @AGILECHRISYYC Chris Edwards P.Eng., Senior Manager Chris.Edwards@ihs.com @AgileChrisYYC THE AGILE ARCHITECT A Case Study in Transformational Leadership MARCH 2016
  • 2. © 2016 IHS @AGILECHRISYYC disclaimer: this is not a talk about architecture 2 The Agile Architect / March 2016
  • 3. © 2016 IHS @AGILECHRISYYC what is the role of an architect in an agile organization? 3 The Agile Architect / March 2016
  • 4. © 2016 IHS @AGILECHRISYYC your mileage may vary 4 The Agile Architect / March 2016
  • 5. © 2016 IHS @AGILECHRISYYC Setting the Stage • 5 teams, 5-9 each (including QA) • Mix of Scrum/Kanban/Scrumban • Thick Client • C++ • Mature Codebase • Recently Adopted Agile • Major Project – Client / Server 5 The Agile Architect / March 2016
  • 6. © 2016 IHS @AGILECHRISYYC The best architectures, requirements, and designs emerge from self-organizing teams. 6 The Agile Architect / March 2016 Agile Manifesto
  • 7. © 2016 IHS @AGILECHRISYYC Architecture Approach 1: Laissez Faire 7 The Agile Architect / March 2016
  • 8. © 2016 IHS @AGILECHRISYYC 8 The Agile Architect / March 2016 HELP!!!
  • 9. © 2016 IHS @AGILECHRISYYC Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 9 The Agile Architect / March 2016 Agile Manifesto
  • 10. © 2016 IHS @AGILECHRISYYC empowerment is more than just taking your hands off the wheel 10 The Agile Architect / March 2016
  • 11. © 2016 IHS @AGILECHRISYYC how do we incorporate an architect… without sacrificing agile values? 11 The Agile Architect / March 2016
  • 12. © 2016 IHS @AGILECHRISYYC Wanted to avoid this: 12 The Agile Architect / March 2016 Requirements Design Code Test Deploy
  • 13. © 2016 IHS @AGILECHRISYYC And this: 13 The Agile Architect / March 2016 cliparthut.com
  • 14. © 2016 IHS @AGILECHRISYYC Architecture Approach 2: The Architecture Scout 14 The Agile Architect / March 2016
  • 15. © 2016 IHS @AGILECHRISYYC 17 The Agile Architect / March 2016 Architecture by Example ”“
  • 16. © 2016 IHS @AGILECHRISYYC 18 The Agile Architect / March 2016
  • 17. © 2016 IHS @AGILECHRISYYC 19 The Agile Architect / March 2016 Too many classes makes the system too complex! Big classes make the system unmaintainable!
  • 18. © 2016 IHS @AGILECHRISYYC 20 The Agile Architect / March 2016 WORK HARDER!
  • 19. © 2016 IHS @AGILECHRISYYC what if the architect is WRONG? 21 The Agile Architect / March 2016
  • 20. © 2016 IHS @AGILECHRISYYC how do you know if the architect is WRONG? 22 The Agile Architect / March 2016
  • 21. © 2016 IHS @AGILECHRISYYC 23 The Agile Architect / March 2016 I thought you knew something I didn’t ” “
  • 22. © 2016 IHS @AGILECHRISYYC architect is a leadership role 24 The Agile Architect / March 2016
  • 23. © 2016 IHS @AGILECHRISYYC The Agile Architect / March 2016 xkcd.com 25
  • 24. © 2016 IHS @AGILECHRISYYC 27 The Agile Architect / March 2016 Image Source: worklifematters.net Spotify Engineering Videos
  • 25. © 2016 IHS @AGILECHRISYYC how do I serve the teams without telling them what to do? 28 The Agile Architect / March 2016
  • 26. © 2016 IHS @AGILECHRISYYC Intent Based Leadership 29 The Agile Architect / March 2016 Rob van Hilten, Flickr
  • 27. © 2016 IHS @AGILECHRISYYC 30 The Agile Architect / March 2016 Don’t move information to authority, move authority to the information ” “ David Marquet
  • 28. © 2016 IHS @AGILECHRISYYC 31 The Agile Architect / March 2016 Image Source: worklifematters.net
  • 29. © 2016 IHS @AGILECHRISYYC 32 The Agile Architect / March 2016 two pillars that need to be in place: the technical competence …. and organization clarity. … put those things in place and then you can give control. ” “ David Marquet
  • 30. © 2016 IHS @AGILECHRISYYC i intend to… 33 The Agile Architect / March 2016
  • 31. © 2016 IHS @AGILECHRISYYC 34 The Agile Architect / March 2016 Image Source: worklifematters.net Spotify Engineering Videos
  • 32. © 2016 IHS @AGILECHRISYYC Architecture Approach 3: The Architecture Coach 35 The Agile Architect / March 2016 Rob van Hilten, Flickr
  • 33. © 2016 IHS @AGILECHRISYYC Daily Design Meeting • 30 minutes • Technical lead from each team • Discuss challenges that being encountered • Exercise is repeated on the team that brought the challenge 36 The Agile Architect / March 2016
  • 34. © 2016 IHS @AGILECHRISYYC 37 The Agile Architect / March 2016 Resist the urge to provide solutions. ” “ David Marquet
  • 35. © 2016 IHS @AGILECHRISYYC questions communicate values 38 The Agile Architect / March 2016
  • 36. © 2016 IHS @AGILECHRISYYC letting go is hard 39 The Agile Architect / March 2016
  • 37. © 2016 IHS @AGILECHRISYYC Design Meeting Challenges • Jealousy from those who cannot attend • Conflict remains between teams • Design group seen as new design authority 40 The Agile Architect / March 2016
  • 38. © 2016 IHS @AGILECHRISYYC 41 The Agile Architect / March 2016 organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations ” “ M. Conway
  • 39. © 2016 IHS @AGILECHRISYYC 42 The Agile Architect / March 2016
  • 40. © 2016 IHS @AGILECHRISYYC Architecture Approach 3: The Architecture Coach 44 The Agile Architect / March 2016 Rob van Hilten, FlickrCoaching Agile Teams, Lyssa Adkins
  • 41. © 2016 IHS @AGILECHRISYYC Design Steps • What is the problem you’re trying to solve? • What solutions should we consider? • What are the pros/cons of each solution? 46 The Agile Architect / March 2016
  • 42. © 2016 IHS @AGILECHRISYYC 47 The Agile Architect / March 2016 Sources: Edward de Bono, retrospectivewiki.org
  • 43. © 2016 IHS @AGILECHRISYYC create a common framework for resolving conflict 48 The Agile Architect / March 2016
  • 44. © 2016 IHS @AGILECHRISYYC disagreement is a mechanism for organizational clarity 49 The Agile Architect / March 2016
  • 45. © 2016 IHS @AGILECHRISYYC the end? 50 The Agile Architect / March 2016
  • 46. © 2016 IHS @AGILECHRISYYC something interesting happened 51 The Agile Architect / March 2016
  • 47. © 2016 IHS @AGILECHRISYYC 52 The Agile Architect / March 2016 ?
  • 48. © 2016 IHS @AGILECHRISYYC do we still need an architect? 53 The Agile Architect / March 2016
  • 49. © 2016 IHS @AGILECHRISYYC Final Architecture Approach: Architecting as a Team 54 The Agile Architect / March 2016 Steve Jurvetson, Flickr
  • 50. © 2016 IHS @AGILECHRISYYC 55 The Agile Architect / March 2016 Image Source: worklifematters.netSpotify Engineering Videos
  • 51. © 2016 IHS @AGILECHRISYYC approach must evolve over time 57 The Agile Architect / March 2016
  • 52. © 2016 IHS @AGILECHRISYYC Summary • Empowerment is more than standing back • Lead through intent • Resist the urge to provide solutions • Create a framework for disagreement • Disagreement is a mechanism for organizational clarity 58 The Agile Architect / March 2016
  • 53. © 2016 IHS @AGILECHRISYYC Chris Edwards Chris.Edwards@ihs.com @AgileChrisYYC 59 The Agile Architect / March 2016 Questions?

Editor's Notes

  • #8: Anecdote: First feature we worked on. PSS Model. Usually 1 person. Leap of faith and got a whole team to work on the same feature. New project:
  • #16: Anecdote – Create an example that exercises all layers in the system, from the presentation layer interacting with our services, to managing a transaction, to interacting with the database
  • #21: Anecdote: “Transaction manager”
  • #24: Anecdote: Repository replicated many times over
  • #33: Design Skills, Knowledge of DDD, Enterprise architectuer patterns, Organizational Clarity -> Conceptual integrity on architecture approach, understanding of client’s needs, assumptions of current approach. The context. The WHY
  • #38: Anecdote: Melvin: Should I mock this. Me: NO! don’t do that…..
  • #39: Anecdote: Team was trying to decide between two different API designs for our domain layer. I could see that one of the designs would be problematic if we ever had to make changes, because there was some sequence coupling. Each caller would be required to call a set of methods in a specific order or else a part of the underlying system wouldn’t behave properly. Option 1: “This design is better, because bl……” Option 2: “If we changed the underlying mechanism, which design would require the fewest changes?” The question communicated to them that I wanted them to be considering maintainbility, but it also engaged their thinking. The question itself communicated a value, but without handing them an answer.
  • #40: Anecdote: Production aggregation -> I just want to hand them the solution! I already have it!
  • #42: Anecdote: GIS Team -> Interface between the components was horrendous Note: Note used to inter-team collaboration because of component based teams.
  • #45: Anecdote: Reminder back to the “SRP” example
  • #46: Anecdote: We all know him. The guy who has to be right. Well we all have some of this inside.
  • #47: Pull you out of the argument mode. Physically separate from the design options.
  • #48: Pull you out of the argument mode. Physically separate from the design options.
  • #50: Anecdote: Database or domain layer?