THE ROOT CAUSE ANALYSIS

ROOT CAUSE ANALYSIS A problem is a matter or a situation regarded as unwelcome or harmful and it needs to be dealt to overcome. Root cause analysis is a method of detection of the problem and solving it to the maximum extent possible. Getting into the roots of the problem …

Read More »

THE VALUE OF BA ROLE

THE VALUE OF BUSINESS ANALYST ROLE   A BA is a valuable tool for any business. They are there to help companies make viable changes to improve their organisation and achieve their goals. While some companies still believe that BA’s are an added cost, they actually do the opposite and …

Read More »

Wireframing and prototyping

Wireframing: A wireframe is also known as blue print, it’s a visual representation of elements on a website or application. They are static and do not include any interactions or animations. They are simple, minimal but they are not clickable. What exactly is a wireframing? It’s a two-dimensional drawing of …

Read More »

Do’s And Don’ts Of Business Analyst

Do’s and Don’ts of BA   Delete the word no from your memory. you can never say no the client. Client cannot be right always but that doesn’t mean you need to argue with the client, for that consult your SME or Project Manager. You should always include your Project …

Read More »

SWOT Analysis!

What is SWOT Analysis? SWOT Analysis is an acronym of Strengths, Weaknesses, Opportunities, and Threats. So SWOT Analysis means we analyze the strengths, weaknesses, opportunities, and threats when starting a blog. It helps analyze what the positives and negative aspects of blogging are. Positives are strengths and opportunities. Negatives are weaknesses and threats. SWOT …

Read More »

Feasibility study of a project

Feasibility study of a project   A feasibility study is used to assess whether a proposed project should be undertaken. It does this by assessing feasibility in four area: Economic feasibility – money Technical feasibility – hardware/software Operational feasibility – resources Schedule feasibility – time Based on the outcome of …

Read More »

Root Cause Analysis(RCA)

Root Cause Analysis is a useful process for understanding and solving a problem. Figure out what negative events are occurring. Then, look at the complex systems around those problems, and identify key points of failure. Finally, determine solutions to address those key points, or root causes. How to conduct Root Cause Analysis? Define the problem. Ensure you identify the …

Read More »

Requirement Traceability Matrix (RTM)

Requirement Traceability Matrix (RTM) is a document that maps and traces user requirement with test cases. It captures all requirements proposed by the client and requirement traceability in a single document, delivered at the conclusion of the Software development life cycle. The main purpose of Requirement Traceability Matrix is to validate …

Read More »

The Value of BA Role

Business Analyst always makes sure that the requirements from the business are collected properly and documented. The same will be conveyed to technical team in UML which is likely to be understood by them. He acts as a bridge between client and development team. He gets the requirement from clients …

Read More »

DO’s and DON’Ts of BUSINESS ANALYST

Business Analyst should always try implement the solutions, he/she should not say no whenever client/business approaches him/her for the IT solution. At the Time of Requirement Gathering from Client, BA should not assume that it is included BY DEFAULT. He/She has to always check with clients. If any point is …

Read More »

Watch Dragon ball super