When an engineer looks at a system proposal, he asks “Why?!”
When a scientist looks at a legacy, he asks “Why not?!”
What’s up?
Apparently the engineer needs a Business Analyst to give him a business domain map that explains
- That the feature will cut down user’s cost from 3 clicks, 2 load screen to 2 click, 1 load screen
- That one specific customer wants that feature to be distinctive from those of competitors
- That the way it will be done complies with the firm’s security terms
- That consistency with legacy systems is maintained
And the scientist needs a Business Analyst to give him an analysis sheet that explains
- That it is not cost-effective to implement what he’s thinking
- That the social side-effect of his idea is too much a price
What Business Analysts are here for!
Tags of this article: consistency,cost-saving,engineering,How Business Analysts work,map,process,science,security,system.
















Recent Comments