COEPD – Center of Excellence for Professional Development Happy Learning
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 »RACI Matrix
The model is based on few of the best practices to be followed in an organization that helps in just in time delivery of products without wasting time on blaming others in case of a scope creep and gives clarity amongst different roles in the organization. In simple terms this …
Read More »Do’s and Don’ts of a BA
It has long been discussed about the need of a business analyst in the journey of IT development life cycle and having been associated in that profile for many years I thought of penning down a few thoughts regarding the do’s and don’ts of a business analyst that have helped …
Read More »Dos AND DONTs AS A BUSINESS ANALYST
BLOG WRITING 2- Dos AND DONTs AS A BUSINESS ANALYST Any field of work or any job role has some rules or ways to follow. In the same way a Business Analyst also has few basic Dos and Donts to follow for the progress of his organization and in …
Read More »