Question

I work for an organization that is pretty much a start-up within a large corporation. The team has several database engineers, and a few software engineers (in the data mining field). We’re growing at a fast rate, which puts the need to have an overall architecture strategy or technology roadmap (or compass) for the next few years. As a software engineer, I’ve been assigned the task to start off on bi-monthly meetings to lead that discussion. So, my question is, how do you kick-off your role as an architect? how do you start off an organization-wide architecture discussion?
I started reading the book “97 Things Every Software Architect Should Know”, but I’d like to hear more from your experiences. So, as an architect, how did you start?

Best regards,

Answer 1

1. Find out who’s on your team
2. Find out what they’re interested in at the level of systems analysis
3. Find out who knows people in the wider corporation
4. Find out what’s in use in the wider corporation
5. Find out what people have used before in your particular division
6. Take all of the above information and use it to start talking about Now, Soon, and Eventually. Pay particular attention to how you connect with the outside world both in terms of outside the division and outside the corporation.

Do not start talking about architecture until you know what you’re starting with. Do not start a discussion about architecture until everyone else does, too.