What are the common deliverables at the end of Business Architecture engagement?

There should be no independent business architecture deliverables. What you should have a set of EA deliverables of which there are business architecture artefacts representing the business view. You cannot do business architecture in isolation; you will just end up with another organisational silo or similar situation to what we had in the early information architecture days – a conceptual data model for the entire organisation that took so much time and effort to develop that it broke people and then was of little or no use to anyone. In EA you need the BITS – business, information, technology and solution architecture views to every problem you are trying to solve or every strategy you are trying to execute. I do not think there is a modern organisation that conducts business independent from information, applications and technology if there is then there would be separate BA deliverables.

Think carefully about what you are trying to achieve and if it is just creating THE business architecture then you will be heading down a risky path. Instead think about using business architecture deliverables to make better future state decisions. Then think about what these will look like and as Harish mentioned they will vary every time. Ask your self this question – “What information do I need to make a decision about this future state architecture?” Then define the deliverables that will help.