What Is The Toughest Challenge Facing Your Business Analyst Career Today?
We are compiling and addressing the challenges, questions and concerns facing business analysts in their career right now.
So, post your challenges, concerns or issues here, on this post and we would get back to you with the answers to your pressing issues.
The Following Posts Are Excepts of Issues or Challenges Posted By Business Analysts
1. The biggest challenge I see is to meet the changing customer expectations in these difficult times.
2. With the current state of the market and the lack of funds dedicated to projects, I think the major issue is the perception of the Business Analyst’s role within the project team? From what I had observed in my previous contract, instead of being an integral part of a project, the BA is seen as a luxury resource. The idea of replacing the BA with a SME or other expert users is a step in the wrong direction which will ultimately backfire on those organizing heading down that road. So let’s hope this backward idealism never eventuate and that common sense and history prevail itself?
3. The ownership of a BA lies with Business or IT is also questionable. If IT side owns a BA then they feel as if it is an additional layer of billing hardly adding any value. But one thing is for sure, whatever the challenges, the role of BA would be crucial especially with organisations spawning globally and requirements changing ever so quickly.
4. The SMEs are often so busy in my industry and few that the BA ends up becoming a SME. And why not? After working closely with the SMEs and writing the specs, they often become so intimate with the product that they are looked to as experts. Where that becomes a problem is that you can end up being pulled in different directions, and draws focus away from the requirements portion of the job.
Add this to an already reduced budget and limited resources and the BA role has become something different than what it was 10 years ago, I think. Suffice to say, I find the biggest challenge is the BA’s need to wear many hats; part PM, part editor, part technical writer, add a splash of technical know-how and there you have a recipe for today’s Business Analyst.
5. In the current environment, the “Business Analyst” role can vary according to the designation level, industry, work experience and above all profile expectations.
6. I think the lack of definition for the role (a BA is not a business SME but is a SME on being a BA); lack of consistency and standards for the discipline of business analysis, lack of general understanding of the role, and where it fits in a particular company, all open the door for BA’s to be constantly be pulled away from the intent of the role which is to elicit and gather the requirements.
The furor over use cases, scenarios, templates, etc., is blown away if you have an experienced BA to elicit the requirements.
I find all the wrapping to be distracting and limiting at times and absolutely unnecessary.
I don’t need to write a complex use case; just do it to make others happy, but end up working with the developer on what the real requirements are; they don’t care about the use cases either.
7. Use Cases, BA approach docs, template definitions etc what a waste of time …. ? But then on my last contract, that all changed. In situations where the DEV team is off-site or off-shore and actually use the Use Case package in depth in the design phase, it actually works especially if the organisation does not include the BA in the design and SRS are not part of the delivery to the developers. So
again, it really depends on the organisations and project team structure.