Showing posts with label myths. Show all posts
Showing posts with label myths. Show all posts

Wednesday, July 6, 2016

Disadvantage of being business analyst

As we have seen, there are many benefits to being a professional business analyst. However, no one ever talks about dark side. Here are few points that you need to watch out for if you wish to build a successful career in business analysis.

Getting it done without Authority: Being positioned in a central role, the business analyst has to be a Jack of all trades and juggle numerous duties and responsibilities. These duties can range from managing stakeholders (from the CEO to the end user who is generating a report in some corner) and maintaining an IT department along with balancing a unique set of requirements specific to the task.

It sounds difficult, but that’s the fun. Not everyone is a people person.

Value Creator: Sometimes you need to elicit requirements, confirmation and enter into communication with stakeholders when they each have their own BAU and other priorities. Beware that at times, stakeholders do not always see value in business analysis efforts and respond accordingly.

Know it all: While joining a new role, the hiring person/line manager mentioned that they knew I was new to the domain and they were fine with it. However, after 3 months, the same person suggested I obtain more knowledge than the SMEs and senior director who had been working there for over 10 years.

It is an unrealistic expectation to require business analysts to have a deeper and wider knowledge of the domain than the stakeholder. To elicit the requirements in the correct way, boil down the question to its simplest and purist form, and manage the scope at the right place.

If the BA changes the domain, then it is like starting all over again.

Super Dynamic: The business analysis is very dynamic profession as they are the first to react to new changes in business/industry such as new regulations, laws, codes of practice, business processes and methods.

The business analyst often has to walk on a challenging path through both the academic and practitioners' world, acquiring new knowledge and skills and implementing them effectively in real life situations.

If you are not quick to adapt to new circumstances and conditions, it will invariably lead to frustration.

Superman(woman)’s Confidence: A good BA must have the confidence to stand up for their points to present, negotiate, and manage conflict (if it arises) using logic and every weapon in their arsenal. Remember, the audience could be anyone in the organization.

Unsung Hero: Think of the person who provides ideas to integrate business with technology to create a million (or billion) dollar enterprise. For example, the iPod that changed the music industry or airbnb who revolutionized the hotel industry. The identity of these individuals remains largely unknown, unless he/she happens to be ‘Steve Jobs!’

Most modern inventions that applied technology and innovation to industry are a direct result of business analysis that created billions of dollars of revenue, but many are yet to get their dues.

However, the situation is changing. Being a professional BA is now considered a proper career and many organizations, both profit and non-profit, are working towards making it even better.

Apart from these pitfalls, being a BA is fun!

Saturday, May 30, 2015

5 myth about Business Analysis

Having interacted with several Business Analysts during my years in the Investment Banking industry, I find that only a very few really understand the intricacies of Business Analysis.

I am therefore proceeding to share a few myths and facts around it.

1. Domain knowledge is secondary
Domain knowledge is the most important factor. However, Business Analysts belonging to a technical background often feel that domain or business knowledge isn't that important in effective discharge of their role. Well, that’s completely untrue. IT solutions are only meant to facilitate in improving the overall business. Therefore, Business Analysts must first thoroughly attempt to understand the business before offering any solutions.

If a Business Analyst barely grasps intricacies of his domain, how will he either make suggestions to improve the business processes or launch new products?

2. Tools are more important
Tools are important as they help in creation of artefacts in a comprehensible format. Diagrams or pictorial representations help us to better understand complex requirements or processes. We are all aware that client or business side professionals usually avail of commonly available tools such as MSOffice, Share Point, MS Project, Visio and at times Business Object for fulfilling their requirements as information technology not being their core business only serves to act as a facilitator. However, vendors such an IT company, usually have most advanced tools and technology at their disposal in order to manage projects in their realm.

Analysts must, therefore, either focus on tools that are easily available to their stakeholders or convert any artefact into an easily and widely shared file.

For instance, the 19th century Russian writer, Leo Tolstoy writing on paper cannot be superior to a novelist writing on an iPad. At the end of the day, it is the story and its presentation that matter. Of course, technology does play a role in movie making business when sophisticated CGI (computer generated imagery) is used to bring even the hitherto unthinkable images alive on the silver screen.

3. Stakeholders hate new ideas
Business Analyst must understand a stakeholders’ point of view. Any drastic overhaul might only serve to jeopardise well entrenched processes.

4. Technical knowledge is must
Technical know-how is essential. We need to understand what a programmer is doing or how he is she or he working to incorporate your requirement. However, we need not step on to their role and do it ourselves as that will only culminate in your rubbing everyone else around you in a wrong way.

5. Requirement specifications for generating reports must commence development work starts.
No, that usually starts with a business needs documents. It gradually enriches and evolves through discussion held in the initial phases (requirement elicitation and management phases) of the of project life. Although it is completed before a solution is validated before development, it is an ongoing process where requirement is identified through discussions.

It is a fact that what we visualise initially will change to create a clear demarcation between estimation and actual.

I have many more examples up my sleeve. But for a start, these are good enough to start exploring new dimensions in order to broaden your thought process.

Good Luck!

--------------
#BusinessAnalysis, #BusinessAnalysisTraining #Businessanalyst #Training #certification #ANISAN #ANISANtechnologies #SandhyaJane #myth #howtolauchbusinessanalystcareer #businessanalysiscourse #career #businessanalysiscareer #BusinessAnalysis #career #BusinessAnalysiscourse #BusinessAnalyst #Chennai #Delhi #Bangalore #Gurgaon #HongKong #Hyderabad #Mumbai #Pune #SandhyaJane #ANISAN #technologies #BusinessAnalysisTraining #certification #Dubai #sydney #London #Tokyo #Shanghai #Beijing #careerpath #businessnalaysiscareer #BA Sandhya Jane, San Francisco, Bangalore, Beijing, Chennai, Delhi, Dubai, Hong Kong, Johannesburg, Kuala Lumpur, London, Mumbai, Hong Kong, New York City, Shanghai, Delhi, Dubai, Sydney, Tokyo, UK, USA, India, China, Australia, Business analysis consulting, consulting services