Architecture Training Calendar


IT Architect Training is needed to get your IT organization in the best shape ever.  This is the original Architect Boot Camp and started in 2002.  These classes are not readily offered at universities, nor at many technical training colleges.  Architect training is required because to become an architect, it takes a combination of experience, skill and desire, as well as some very specialized training in process, methods and soft skills.

We created some of the very first IT Architecture training ever, and have been doing it for over ten years.  Check out our calendar, and let us know what you are interested in.  We periodically offer schedule public training based on demand, and custom site architecture training is always available.

The Architect Boot Camp training workshops for winter/spring 2012.  IT Architecture Training is planned… Download our catalogue of publicly available architecture workshops. Indicate your interest in future architecture seminars, or contact us about a custom onsite architecture education at your workplace.

Also – See our Training Testimonials.

Workshop Date Duration Location RegistrationDates

Intro to Architecture Boot Camp


TBA 8 hours web Get details
Executive Architect Boot CampXAB January 2012 8 hours n/a Get details
IT Architect Boot Camp FundamentalsIAB Winter 2012 24 hours


Get details
Enterprise Architect Boot CamEA Fundamentals

EA Advanced

EA Masterclass


Calgary May 8&9
16 hours web/ in person Get details
Solution Architect Boot Camp


TBA 16 hours web Get details
Business Architect Boot Camp


TBA 16 hours web Get details
Technical Architect Boot Camp


TBA 16 hours web Get details

Technical Architect Boot Camp

You have indicated that you are most interested in the Technical Architect Boot Camp.

Business Architect Boot Camp

You have reached this page because you would be most interested in the Business Architect Boot Camp workshop.

Executive Architect Boot Camp

You’ve arrived at this page because you have indicated an interest in the Executive Architect Boot Camp class.

Happy Holiday Weekend to my Canadian Friends,

Some of you luck ones may have fled your cubes, offices or project rooms – and for those of you left, you might be in for a little reading.

If you have been considering the Canadian training coming up October 20-24th, there are still 3 spots available in the IT Architect Boot Camp workshop, and 4 spots in the Solution Architect workshop.  It will exciting as the exercises and labs have been a real treat to create and will be fun and challenging for the participants.  I truly wanted the attendees to experience what it was like to be put into the position of being an IT Architect, and a Solution Architect in a variety of situations.

For those of you watching the Google Group posts, or the IT tool box posts, there has been one of the most lively weeks I’ve seen for a really long time with many chiming in on the “types of architects” threads.  I’ve almost jumped in many times this week, and it took real discipline to get back to the training preparation I have been doing, and to keep my eyes off of the email, as well as dismal world news that is flooding our eyes, ears and households.

My hope for all of you is that Architecture is, and will remain to be alive, well and thriving in your companies and that those around you see what an incredible job you are doing with your projects and programs.  I hope you are in a position to enhance and tune your skills in the soft skills area, as well as in the areas in which you consult with peers and business folk alike.  During these tough times, you may be called upon to come up with some creative ways to continue business with less funding, and help the teams in your finance areas plan quickly.

If we can use some of the scenario analysis skills we’ve gained during our architecture training, as well as skills as an organizational politician and consultant, we should be able to add value to our business teams as they are trying to figure out how to continue to move towards corporate goals.  One of the soft skills we rarely touch on is empathy, and just trying to really understand what they are going through, before pressing on with the transitions that we had planned for systems inthe company is one of the things we can do to help.

It is your job as the architects to constantly keep a finger on the pulse of your business stakeholders.  Rather than keeping our heads down and surging forward with our work, we need to check in and make sure that they still feel that we are going in the right direction and that we are still spending our time and energy on the right things.

Happy Thanksgiving to my friends in Canada, and Happy Architecting to everyone.


Want to become a great architect?  Why not join our Architect Professional Site – entirely aimed at creating GREAT IT Architects!

IT Architect Skills

Recently I was asked that if a person was already acting in the role of a software integrator, did they really need to learn how to be an Architect.  The answer was a little bit complicated, but it was an emphatic “yes!”

While the basis or core skills of a great IT architect does come from solid software integration knowledge and practice, the basic practices, approaches and thought processes as well as ways of thinking in the correct context is what is taught during an IT Architecture workshop.  Various approaches and ways of thinking allows an IT Architect to get a new perspective of the various contexts they must review before choosing a solution or constructing an architecture.

There are various thoughts on how one becomes an IT Architect, and granted there are so many ways to get here, the result is the same.  In order to become good or even excellent, the Architect takes on a different mind set.  There are various perspectives that are reviewed, and as well, various options with respect to ways about thinking about the issue, problem or opportunity are reviewed.

The architect considers more than fitting two pieces of software together, and the approach learned in a workshop will take them through the business objectives and IT Enterprise objectives, through to the various decision making techniques and options for formulating a solution.  Typically the instructions given to an integrator are taken after an architect has determined the best approach and seen best fit for the components that are selected.

During these exercises, the architect takes on a different approach with respect to requirements analysis, solution review, as well as some softer skills to deal with the political and communication parts of the equation.  Often integrators are given something very specific to be done, as well as a roadmap for doing so.  The architect takes part or creates that roadmap, and many more variables are considered than may be actually visible to the integrator.

Finally – there are various approaches that an architect learns to getting from A to B.  They learn to view a solution from a multitude of angles, and those which will enable them to see their way to the minimal path of risk.  In part, the approaches are part of the culture of the organization for which they must have an appreciation for, as well as a component of the overal IT & Business Strategies.

Hopefully that sheds a bit of light on the benefits of learning to become an IT Architect, rather than skipping these important steps.  For more information on training, see our site.

Happy Architecting.

IT Architecture Training FAQs

First of all – reminder that the deadlines for early bird pricing on the Architect Boot Camp workshops in October are creeping up on us.  Get your registration completed and reserve your spot at Early Bird Rates!  There are limited seats, and all we need is your registration, and you’ve got your spot.  We’ll send you confirmation and invoices.

I’ve been answering a few questions in email lately, so I thought I’d add the questions in this blog:

Question: Do you see a big benefit from the Solution Architect Workshop (SAB)?  What’s the difference between it and the Information Architect Boot Camp Workshop (IAB)?

Answer: The IAB will teach you what the role of IT Architect is, how the various types of IT Architects are interrelated, how they fit into the project lifecycles, and how to be an architect practitioner.  You’ll learn the skills you’ll need to play any architect role and the basic architecture methods and process.

The SAB will teach you how to do solution architecture, review many options and put together solutions.  You will learn the skills as well as the steps and process to complete various Solution Architect activities and artifacts.  It is the best course for someone in a project architect role, provided the attendee already knows how or has basic IT architect knowledge and skills

Question: Should I take both of these courses together?

Answer: As we go through the IAB workshop, we are going to practice the various IT Architect skills as they are taught.  We’ll work on a project throughout the three day workshop, and each successive step will build on the previous, so that we will have gone through a typical Architecture activity from start to finish after we have spent three days together.

In the following two days in the SAB, we’ll learn more about putting solutions together and about the various scenarios the Architect faces when asked to create or update the architecture.  We’ll use the existing Architect’s skills if the attendee is just joining us, or the skills just acquired in the IAB if they are continuing.  It is not necessary to take both, but if you are a self-taught architect, it would be beneficial to take both together, to learn some of the best of breed approaches, and practices.

Question: What happened to the 1 day Architect Boot Camps – The Introduction and the Executive Architect Boot camp?

Answer: These training sessions have been held multiple times in the last few years and demand wasn’t high following the catalog release.  These classes are targetted to be offered as an online offering in October.  There will be some self-study, and some instructor/participant interaction offered.  More information to follow – stay tuned!

Question: Where are the classes being held?

Answer: Currently we are only scheduled for Winnipeg in October.  We have plans to offer some classes in Phoenix Arizona in 2009, and are currently looking into demand in other large Canadian and U.S. centers.  Classes are always available in group settings.  If you are interested in booking a class for 6 participants or more at your workplace, contact us for more information – choose the option of “other” for location and fill out the rest of the form.

Question: Do you offer a coaching and mentoring service?

Answer: Our online coaching service will be released today – more information later on.  We do also offer Enterprise Architecture coaching through EAdirections.  For more information on either of these services, please contact us, or watch for our information blast coming out shortly.  If you would like to get on our list for notification, please fill out the contact request form.

If you have more questions, or have other architecture problems or questions you’d like answered, please give us your comments.

Happy Architecting

Lately, I’ve been working on the Architect Boot Camp info site and trying to lay out some really basic architecture information and some more advanced stuff. It dawned on me that there might be some who don’t understand the difference between system requirements and architectural requirements. If this is news to you – stick with me. If not, I won’t waste your time – catch you later.

Architecture requirements are typically those you collect during the initial scoping and context setting sessions at the beginning of a project while you are collecting high level system requirements. You need to determine the business objectives for the system, and for the architecture specifically.

It is so important to ensure that the architecture is aligned with the business drivers and objectives for the project. The architect keeps his or her eye on knowing where VALUE WILL BE ACHIEVED. What are the stakeholder goals? Main criteria for success?.

Setting system context helps to measure scope and set the appropriate boundaries. The architect needs to understand what the system interface will be, and what factors will characterize the architecture. Getting a list of top-level and high-priority goals will assist in setting this scope. This list can be further expanded when moving towards the elaboration phase of the project, and further gather the functional requirements.

The infrastructure must be designed to support the services and functionality that users require. It must deliver the appropriate levels of performance, security, usability and flexibility. All are factors that must be considered at the very beginning during the structure design and concept building of the solution architecture.

If the product is being purchased, the solution or system architects must review the requirements in order to determine their relevance and completeness. Specifically – those relating to non-functional requirements – specifically in the areas of performance, volume, methods of doing transactions or using the system, whom will use the system, how they will use it, etc. require review by the architects.

The architect must also ensure that these architectural requirements align with the Enterprise Architecture view. There are standards that are set for an organization, and typical infrastructures and patterns that are acceptable. Knowing, studying, analyzing these considerations in advance make up the architecture requirement gathering efforts for the early stages of the project.

These requirements need to be included in the solution architecture documentation set, and potentially used for volume, stress, and usuability testing during prototyping stages if the technologies are new, or if the requirements are risky.

Pure business functionality are user and system requirements. These are typically gathered by the systems and business analysts. An overview of such requirements should be held with the architect to ensure that they don’t become intermingled, but there are shades of grey when it comes to “which documentation set” they belong to. You are a smart individual – you’ll figure it out.

For more on architecture how-to’s, visit The Architect Boot Camp.

Happy Architecting!