Engineering the Future of Software
29–31 Oct 2018: Tutorials & Conference
31 Oct–1 Nov 2018: Training
London, UK

Beyond the Technical - Succeed at Leading a Software Architecture Team

Maggie Carroll (
15:5016:40 Monday, 29 October 2018
Business solutions, Enterprise architecture, Integration architecture, Leadership skills
Location: Park Suite (St. James / Regents) Level: Advanced
Secondary topics:  Best Practice, Overview

Who is this presentation for?

Software Architecture Leads, Enterprise Architecture Leads, Experienced Architects

Prerequisite knowledge

Software development background Software Architecture background or exposure Some experience working in a business environment

What you'll learn

Start an Architecture Team from scratch Techniques to ensure Success in the organization Skills and tactics to pass along to your team


Software Architects and Enterprise Architects work with a variety of roles. Often the deep technical work is performed by other application architects or solutions architects. This talk focuses on skills and actionable techniques I found useful when creating a new architecture function and leading other architects in developing a system of systems.

This talk also compares two diverse architecture challenges by storying the solutions, and with an honest look at the level of success and pivoting.

Challenge 1: start up a new EA function in an IT team comprised of solution architects leading agile scrum teams.

Challenge 2: integrate large and small vendors in a highly technical real-time proprietary system, and meet a faster-than-before schedule.

Each topic below was a key element of meeting both challenges. Each topic below is presented with story examples from my experience, and show what lead to success and what lead to pivot (fail then adapt).

Starting with the End in Mind: What is the goal?

  • Align with Corporate Strategy
  • Find alignments with Business Partners
  • Identify Artifacts to Communicate OnGoing Success- A roadmap? A schedule? A transformation diagram?
  • Is schedule king or is cost king? . . . and what to do if it is neither.

Gaining Influence: Starts with Ownership

  • Create a framework within which others contribute
  • Technical Architects own their piece (The first 90 days: what got you here won’t get you there)
  • Business Partners are key stakeholders

Energizing the team: Create Opportunities for Success with Skill Development

  • Effective Estimation
  • Framework Choice
  • Governance that works
  • To Meet or Not to Meet?
  • Vendor Selection
  • Celebrate, Acknowledge, Reward


  • Document Your Business Rhythm
  • Follow Your Business Rhythm
  • Improve Your Business Rhythm

Communicate with the stakeholders.

  • On The Business Rhythm.
  • Continually Update and Pitch your Artifacts – Articulate your value – continually sell
  • Implement useful changes, even if they don’t have acceptance. Yet.
Photo of Maggie Carroll

Maggie Carroll

Maggie Carroll has worked as a Software Architect and Enterprise Architect for the last 6 years, and has worked in Software Engineering for the last 30 years. Maggie has a variety of experience. She has helped launch 2 successful startups and has helped with several large real-time systems in the aerospace industry.

Maggie currently works as a Software Architect putting together a system of systems and enabling vendors to play well together. She loves leaning up processes and has a passion for improving team dynamics to get great results!

Leave a Comment or Question

Help us make this conference the best it can be for you. Have questions you'd like this speaker to address? Suggestions for issues that deserve extra attention? Feedback that you'd like to share with the speaker and other attendees?

Join the conversation here (requires login)