Course Outline
Module 1: Architecture Standards that Scale
Objective: Agree on a simple, shared set of architecture standards that Principals can reference in daily decisions.
Topics
- Architecture principles: determining what to standardise versus what teams should decide
- Decomposition basics: defining boundaries and ownership
- Integration basics: API contracts, versioning, and compatibility
- Messaging overview: Kafka vs RabbitMQ and what should be standardised
- Data overview: ownership and source-of-truth thinking (Mongo + SQL Server)
- Common architectural anti-patterns in high-scale systems
- Lightweight decision documentation (ADR/RFC concepts)
Module 2: Code Architecture in Large .NET Solutions
Objective: Align on practical guidance for code architecture decisions within large solutions.
Topics
- Structuring large .NET solutions: modules, layering, and boundaries
- Dependency direction and maintaining visible architecture in code
- Shared libraries: when they help versus when they create coupling
- Integration boundaries in code: separation of concerns patterns
- Code architecture "review lenses": what to look for quickly
- Managing exceptions without breaking consistency
Module 3: Design Reviews that Drive Decisions
Objective: Establish a consistent design review approach that yields decisions and shared understanding.
Topics
- What constitutes a strong design review at the Principal level
- Review workflow: what gets reviewed and when
- Review criteria: the few things that matter most
- Facilitation: keeping senior discussions focused and productive
- Decision closure: how to end debates and move forward
- Capturing outcomes: decisions and follow-up actions
- Practice review using a short case study (system-level)
Module 4: Influence Without Authority for Principals
Objective: Strengthen mentoring, feedback, and alignment habits with ICs.
Topics
- Mentoring vs directing: coaching without taking ownership
- Giving high-level technical feedback (clear, standards-based)
- Driving alignment across ICs: practical techniques
- Handling disagreement and resistance constructively
- Simple conversation patterns and scripts Principals can reuse
Requirements
Participants are encouraged to bring 2–3 anonymised examples of recurring debates (such as system decomposition choices, integration approaches, or code structure rules). Sharing any existing internal standards is optional.
Testimonials (2)
Trainer knowledge, involvement, and rapport
Adam Kuklewski - GE Medical Systems Polska
Course - Technical Architecture and Patterns
I liked the exercises that helped to open the mind and gain new insights into software architecture.
