This webinar chronicles one organization’s trial-and-error approach in discovering how to achieve technical alignment across multiple teams while preserving team empowerment.
Presenter: Chris Edwards, P.Eng. Chris is a software manager with IHS Inc.
Original copy for details at https://www.synerzip.com/webinar/role-of-architect-in-agile/
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:
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
Anecdote: “Transaction manager”
Anecdote: Repository replicated many times over
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
Anecdote: Melvin: Should I mock this. Me: NO! don’t do that…..
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.
Anecdote: Production aggregation -> I just want to hand them the solution! I already have it!
Anecdote: GIS Team -> Interface between the components was horrendous
Note: Note used to inter-team collaboration because of component based teams.
Anecdote: Reminder back to the “SRP” example
Anecdote: We all know him. The guy who has to be right. Well we all have some of this inside.
Pull you out of the argument mode. Physically separate from the design options.