Business Architecture

Notes im collecting on what is my real job is:

various names

• Enterprise Architecture.
• "Problem Architect" establishs the scope and focus of the problem to be solved. It's non-invasive to the business types because everyone can agree we have a problem (why would we be talking to IT otherwise?) and it's complementary to IT because it takes IT off the hook from guessing what the problem is. [1]

difference

• standard architect has gvmt code and engineering constraints
• ba has "best practice"

function

the problem:

The Standish group , a IT research group, documents this annually - 31.1% projects canceled, 52.7% of projects will cost 189% of their original estimates and only 16% of projects are completed on-time and on-budget. One only has to look at the rationales given to see the answer: We need a problem architect. [2]

The Solution

• Deliver a paper on what the problem is.
• Maintain and provide relationships with vendors that can take this "blueprint" and create a bid
• Make sure that the plan gets implemented

marketing

• build you venture with a business architect]
• whitepapers
• website
• BNI, Leads group

Problem Architect

• engage client
• Define the problem
• present "blueprint" or "recipe"

• develop "Function Point Analysis" like thingy useful for scoping budget