1. Failure to engage the right Stake-Holders
Solutions providers like developers, designers and tester may want to look into the specific levels of details in the requirements artifacts and also expect that those artifacts will be discussed with them prior informing the client. There is no benefit of a Business Analyst who remains there in the complete project life cycle without having these stakeholders from the very beginning of the project. Customers may like the way how BA’s of your company work, but it is not necessary that the project stakeholders will like the way BA’s work.
One of the successful implementation method is to have standup meetings, scrum meetings and let the scrum master be the Project Manager.
2. Dependency on Templates
A document template sets expectations about what types of requirements and requirements artifacts are to be produce.
Many templates are focused on software requirements and ignore all of the other areas where business analysis can really be of use, like changes to business policies and rules, job functions, relationships, capabilities and workflows. The problem with most templates is either that they are too generic and broad to be of use on a specific initiative, or that they are too narrowly focused and fail to recognize the differences between projects. The usefulness of the document diminishes as soon as the project is completed. But, the reality is that the requirements actually live on with the solution and could be relevant for many years.
3. Trying to solve so many things at once
Focus on incremental changes; test new techniques and tools in different projects but not everything in one project. Understand the complexity of the project and then implement the right approach. Communicate the success of the approach followed and then find the gaps in it, to improve it for the next time. Also, be prepared to abandon some of the changes which didn’t work successfully.
Research new methodologies according to the project scope and size to get things right!
4. Dictating too much, documenting lesser!
Timely meetings with internal teams are important so as the communication with stakeholders is equally important. But it is more important to document the things instead of dictating them verbally. One more fact is that BA’s are known for better communication, so when they start speaking they keep on speaking convincingly and other people start trusting them where everybody misses the important part of documenting those talks which held in the meeting room.
So the most important part is to note down the “Minutes of Meeting”!
5. Missing Business Objective and Suggesting Latest Trends
Suggestions, User Experience(UX), Latest Trends, Best Practices and Traditional Approaches all lead to one road, which is the road of missing true objectives that what was supposed to achieve in the project “The Business Logic-Most Important Factor. Divide all these demanding factors into phases which means collect the requirements right and then start suggesting the best practices and latest trends to improve the User Experience(UX)following the traditional approaches.
Trust me Business Analysis is no small undertaking. You never know what may click to customer’s mind to take your company to heights or to finish the relationship forever. But it is also important to understand that:
“Anyone who has never made a mistake has never tried anything new.”
― Albert Einstein