Difference between revisions of "Business Architecture"
From Organic Design wiki
(+Enterprise Architecture wiki (looks marginal)) |
(rm from stub already in peder todo) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
Notes im collecting on what is my (peder) real job is: | Notes im collecting on what is my (peder) real job is: | ||
| − | ==various names== | + | == objective == |
| + | i am done with presenting preliminary information and knowledge to clients without getting paid for it. My deliverable is a piece of paper, and i get paid to talk. | ||
| + | |||
| + | == various names == | ||
*Enterprise Architecture. | *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. [http://blogs.ittoolbox.com/eai/engineering/archives/lets-get-rid-of-the-role-of-business-architect-2142] | *"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. [http://blogs.ittoolbox.com/eai/engineering/archives/lets-get-rid-of-the-role-of-business-architect-2142] | ||
| + | ([[w:Systems architect]] | ||
| − | + | == difference == | |
| − | ==difference== | + | *standard [[w:Architect]] has gvmt code and engineering constraints |
| − | |||
| − | *standard | ||
*ba has "[[best practice]]" | *ba has "[[best practice]]" | ||
| − | ==function== | + | == function == |
| − | |||
===the problem:=== | ===the problem:=== | ||
| Line 20: | Line 19: | ||
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. [http://blogs.ittoolbox.com/eai/engineering/archives/lets-get-rid-of-the-role-of-business-architect-2142] | 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. [http://blogs.ittoolbox.com/eai/engineering/archives/lets-get-rid-of-the-role-of-business-architect-2142] | ||
| − | ===The Solution=== | + | === The Solution === |
| − | |||
*Deliver a paper on what the problem is. | *Deliver a paper on what the problem is. | ||
*Maintain and provide relationships with vendors that can take this "blueprint" and create a bid | *Maintain and provide relationships with vendors that can take this "blueprint" and create a bid | ||
*Make sure that the plan gets implemented | *Make sure that the plan gets implemented | ||
| − | + | == marketing == | |
| − | ==marketing== | ||
*[http://news.pghtech.org/teq/teqstory.cfm?id=724 build you venture with a business architect]] | *[http://news.pghtech.org/teq/teqstory.cfm?id=724 build you venture with a business architect]] | ||
*whitepapers | *whitepapers | ||
| Line 33: | Line 30: | ||
*BNI, Leads group | *BNI, Leads group | ||
| − | ==workflow== | + | == workflow == |
| − | + | === Problem Architect === | |
| − | ==Problem Architect== | ||
*engage client | *engage client | ||
*Define the problem | *Define the problem | ||
| Line 43: | Line 39: | ||
[http://wiki.ittoolbox.com//index.php/Topic:Enterprise_architecture Enterprise Architecture wiki] | [http://wiki.ittoolbox.com//index.php/Topic:Enterprise_architecture Enterprise Architecture wiki] | ||
| + | [[Category:phalseid/Todo]] | ||
Latest revision as of 09:37, 9 February 2009
Notes im collecting on what is my (peder) real job is:
Contents
objective
i am done with presenting preliminary information and knowledge to clients without getting paid for it. My deliverable is a piece of paper, and i get paid to talk.
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 w: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
workflow
Problem Architect
- engage client
- Define the problem
- present "blueprint" or "recipe"
- develop "Function Point Analysis" like thingy useful for scoping budget
