These are what I consider the highlights of the discussion. It may have been different for other participants, this is what stood out for me.
- Attracting Diversity - we need diversity in the group! It would make the group stronger, more resilient to changes, and help it last beyond one or two peoples efforts. When we talked diversity it mostly focused on a good spread of ages and experience and how there was much that could be shared to bring younger IT people into the architect roles. The diversity also included discussion from the broader sense of gender and ethnic / cultural background. In the end, it was mostly focused on age and experience and including as much diversity as we could.
- Atlantic Canadian Architects are well prepared - the Atlantic Canada market is smaller for IT Architects, and yet, the responsibilities and opportunities are not specialized, the IT Architects in Atlantic Canada have therefore developed broad experience. In other words, they have filled many of the Architectural roles because the work needed to get done and they were the most appropriate to get it done. This is a real strength for IT Architects in Atlantic Canada. To be a good Architect you need to see the big picture and having a wide range of experience is essential.
- Remain Technology Agnostic - we agreed that it is best to remain technology agnostic. This means we never align ourselves with a particular vendor, framework, approach, methodology, partner, certification, training, etc. This means that we encourage discussion about everything architectural and how different technologies and approaches work together and the best way to get something done. This means we encourage involvement from all vendors, frameworks, methodologies, etc... in the end, deepening our understanding of how to work with all vendors products, methodologies, frameworks, etc... is best for everyone.
In addition to the highlights there are other discussion themes worth mentioning
- We have a good number of very experienced Architects in Atlantic Canada who have worked internationally and across all the different architectural disciplines. When you consider our associations vision to become internationally known for our architectural abilities we already have a very solid foundation.
The many roles of the IT Architect.
- These kinds of groups / associations have come and gone over the past 30 years and it is a good idea to start meeting again. There is great value both for the profession and for the technology industries in Atlantic Canada. Mostly, its having other architects to discuss how to best get things done and to deepen understanding of emerging technologies. We also need to reach out to the younger IT professionals to be sure the IT Architecture within Atlantic Canada stays strong and healthy.
- Having this as an Atlantic Canada initiative is a really good idea. This mostly comes from Atlantic Canada being a relatively small market and many IT professionals know one another. It is also well aligned with how many public and private organizations function within Atlantic Canada. When wanting to partner and get support from these organizations it is important that we span all four Atlantic provinces so we can reduce duplication of effort and have broader impact in all we do.
The Next Steps
- Get together often, formally and informally - yes, it is a good idea to have formalized meetings and events, but it is also a good idea to get together informally for Lunch, or a game of pool, and just talk architecture. We agreed we need as many informal meetings as formal meetings.
- Use the #ACAITA hashtag - whenever you post or use online networks / media use the #ACAITA hashtag. This hashtag will assist in bringing the communities online discussion together and followed.
- Attend all kinds of events as a ACAITA member - discussing architecture (as a member of the ACAITA) at the many technology and other events will bring our association more attention. Good IT architecture is needed wherever a technology initiative is underway. Get involved, reach out, talk architecture.
- Identify all the IT Architecture and related education programs in Atlantic Canada - we agreed it would be very useful to gather a list of as many of the computer science, technology and business programs that wouldbe interested in IT architecture.
- Identify the Architectural Groups we could consider partnering - we also need to consider all the existing associations that would be useful to align ourselves. This could be of great assistance to our collective success, but also save us a lot of time and effort by learning from those who have gone before us.