Please enable JavaScript.
Coggle requires JavaScript to display documents.
Alternative Business Model (Pain Points (Delivery teams in different IT…
Alternative Business Model
Pain Points
Delivery teams in different IT organizations having their own governance, processes and prioritization
Increasing RtB and CtB costs due to high overhead
Unacceptable ratio between Managers and Workers requiring increasing time in aligning topics
Missing e2e responsibility on IT side
Missing e2e order book
Business not allowed to submit IT requirements (e.g. in form of SQL statements)
Current segregation of duty call for micro management
Moving targets, short term design changes; requirements freeze missing
Doing Big Changes with high risk rather than deploying small changes into production
Increasing bureaucracy due to inefficient processes, organizations and due to tools
Past Experience
IT Business Analysts with a hybrid role (BI DEV, PM, BA, DA, TM) working e2e allowed to adjust semantic BI layer
RTM for e2e order book management incl. prioritization
SPOC on business and IT side
IT SME for each data topic
Rapid prototyping in sandbox environment in an iterative manner together with the end user
Standing delivery team for topics related to Custody Reporting
CTO involvement rather insufficient
Back to the future
Have a standing sales analytics delivery team in IT
Allow business to prototype in BSWH sandboxes in SQL and to submit SQL statements as requirements
Scripting according to BSWH guidelines
Only SQL insufficient - min. data flow chart, data catalogue and business requirements to be sent to Solution Domain
Have a Lead IT BA for sales topics having a good understanding of sales applications, its data and architecture
Focus on deploying small changes rather big rock changes - e.g. deploy every 3 weeks
Have less Managers and more Workers to reduce alignment efforts and therefore overhead costs resp. have an IT person who is responsiblefor he e2e delivery incl. an e2e order book
Have IT SPOCs with broader role/responsibilities (embodying ITPL, MSTR Dev, DWH Dev, Test Executor, Data Analyst) to reduce number of people involved
Allow business to modify semantic layer in MSTR; deployment by IT (execution only)
Change requires cultural change on both, business and IT side - e.g. also in terms of skills
Pre-Requisites
Business skills required
For SQL enablement
Understand DWH components landscape
Know the BSWH guidelines
Read SQL statements, data flow charts and data catalogues
Use Toad for Db2 and can prototype in sandboxes
For MSTR enablement
Able to use MSTR features (e.g. semantic layer)
Understand SaMaRA Data Mart, ideally on attributes level
Able to document changes according to standards
Adjustments in operating model between business and IT required