Well no I don’t think so; I have seen a person doing just the ETL, though not a part of the Business Intelligence or Business analyst team is called a BA.
People doing requirements drafting for a development team are BA’s so on & so forth there at least a 100 interpretations of the TAG “Business Analyst” at each of them are unique to each company & specialize in their skill sets.
What is the repercussion’s of this???
Hiring mistakes done by the companies who do not sufficiently mine the prospective skill sets.
Inconsistency between the BA team & the management in delivering what is needed by the business. This is a disaster!!!!! This would badly affect the purpose of having a BA team thereby affecting the companies, decision making/supporting systems & processes.
Here is a simple Case parallel to the analogy of Business analysts.
A report was to be produced which needed to support the training needs for Service desk analysts during the off peak/non business hours. It was not just a report but also confirmation on some of the issues that are reported during the off-peak hours & the analyst needed to also confirm the pattern, impact & other correlations. This was needed within 2 hours of the request being made & was on high priority.
So there was a definite amount of analytics that had to go into the report before any decision could be made.
There were 2 separate teams; one was that of data Analysts & another of operations analysts. The DA’s are supposed to be good at SQL queries, extraction & so on. The operations analyst team was supposed to be good in analytics. But there was no coordination between these two teams & were functioning separately. Unless the data arrived from the DA’s the Ops analysts could not go ahead.
However this roadblock was broken when one of the ops analysts sought DA’s assistance in a politically correct manner. Surprisingly the entire DA team was on in solving the puzzle as the query had to be developed. It was fairly easy question but drawing a accurate query within a short time was the challenge.
The data that was needed had to be after 7pm up to 6 am on Monday to Fridays. + Starting 7 PM Friday continuously to 6AM Monday morning.
There were 2 queries that were developed one was by the DA team & one was by a person who hailed from the DA team (Thanks Vidya) but at that time worked with the ops analyst team. Below is the query developed by the DA team.
SELECT * , --teadd(n (24*60-DATEPART(HOUR,EST_OPEN_TIME))+(7*60),EST_OPEN_TIME),24-(DATEPART(HOUR,EST_OPEN_TIME)) AS HR,60-(DATEPART(MI,EST_OPEN_TIME)) AS MI,60-(DATEPART(SS,EST_OPEN_TIME)) AS SS, CONVERT(VARCHAR(4),24-(DATEPART(HOUR,EST_OPEN_TIME))) +':'+ CONVERT(VARCHAR(4),60-(DATEPART(MI,EST_OPEN_TIME)))+':'+CONVERT(VARCHAR(4),60-(DATEPART(SS,EST_OPEN_TIME))) as done, CONVERT(VARCHAR(4),7+(24-(DATEPART(HOUR,EST_OPEN_TIME)))) +':'+ CONVERT(VARCHAR(4),60-(DATEPART(MI,EST_OPEN_TIME)))+':'+CONVERT(VARCHAR(4),60-(DATEPART(SS,EST_OPEN_TIME))) as did FROM VW_INCIDENTS_HISTORIC_BLRWHERE COMPANY = 'xxxxxxx'AND EST_OPEN_TIME>='20-FEB-07' AND EST_OPEN_TIME<'20-MAY-07'--AND DATEPART(HOUR,EST_OPEN_TIME)>=18 --AND datepart(HOUR,(dateadd(n, (24*60-DATEPART(HOUR,EST_OPEN_TIME))+(7*60),EST_OPEN_TIME)))<=07 --AND (CONVERT(VARCHAR(4),7+(24-(DATEPART(HOUR,EST_OPEN_TIME)))) +':'+ CONVERT(VARCHAR(4),60-(DATEPART(MI,EST_OPEN_TIME)))+':'--+CONVERT(VARCHAR(4),60-(DATEPART(SS,EST_OPEN_TIME)))) AND DATEPART(HOUR,EST_OPEN_TIME) NOT BETWEEN 7 AND 18AND DATEPART(DW, EST_OPEN_TIME) IN (2,3,4,5,6)UNIONSELECT *, --dateadd(n (24*60-DATEPART(HOUR,EST_OPEN_TIME))+(7*60),EST_OPEN_TIME),24-(DATEPART(HOUR,EST_OPEN_TIME)) AS HR,60-(DATEPART(MI,EST_OPEN_TIME)) AS MI,60-(DATEPART(SS,EST_OPEN_TIME)) AS SS, CONVERT(VARCHAR(4),24-(DATEPART(HOUR,EST_OPEN_TIME))) +':'+ CONVERT(VARCHAR(4),60-(DATEPART(MI,EST_OPEN_TIME)))+':'+CONVERT(VARCHAR(4),60-(DATEPART(SS,EST_OPEN_TIME))) as done, CONVERT(VARCHAR(4),7+(24-(DATEPART(HOUR,EST_OPEN_TIME)))) +':'+ CONVERT(VARCHAR(4),60-(DATEPART(MI,EST_OPEN_TIME)))+':'+CONVERT(VARCHAR(4),60-(DATEPART(SS,EST_OPEN_TIME))) as did FROM VW_INCIDENTS_HISTORIC_BLRWHERE COMPANY = 'xxxxxx'AND EST_OPEN_TIME>='20-FEB-07' AND EST_OPEN_TIME<'20-MAY-07'--AND DATEPART(HOUR,EST_OPEN_TIME)>=18 --AND datepart(HOUR,(dateadd(n, (24*60-DATEPART(HOUR,EST_OPEN_TIME))+(7*60),EST_OPEN_TIME)))<=07 --AND (CONVERT(VARCHAR(4),7+(24-(DATEPART(HOUR,EST_OPEN_TIME)))) +':'+ CONVERT(VARCHAR(4),60-(DATEPART(MI,EST_OPEN_TIME)))+':'--+CONVERT(VARCHAR(4),60-(DATEPART(SS,EST_OPEN_TIME))))AND DATEPART(DW, EST_OPEN_TIME) IN (7,1)
And below is the query developed by the person from the DA team but was now in the Ops Analyst team.
select numberprgn , month(open_time), datepart(dw, open_time), datepart(hh,open_time),
case
when (datepart(hh,open_time) >=7 and datepart(hh,open_time) <=18 and datepart(dw, open_time) between 2 and 6) then 'Buss'
else 'Non'
end as 'Classi'
from VW_INCIDENTS_HISTORIC_BLR
where company like 'xxxxxxxxxxx'
and open_time>='1-Jan-2007' and open_time<='1-Sep-2007'
After hrs query –
Time Considred
Mon – Fri 7am to 6 PM – Buss Hrs
Mon - Fri - 6 PM – 7 am - non Buss
Sat - Sun full day – non Buss
The former took a lot of time to be written, was lengthy to comprehend, execute etc. unlike the latter.
By this time the 2 hour deadline of delivering the report is already breached, presumably there is a negative business impact.
What do we infer from this event?
( would follow next……….)
No comments:
Post a Comment