Business Analysis


Blog post on the description of Business Analyst.
By Harvinder Singh

The five concepts of chapter 1 from BABOK 3.0 are:


What is Business Analysis?


Basically, it is a helping system that implements some changes within the organization by telling the solution and the needs of the stakeholders by interpreting the needs and perfect solution that give some of the important value to the stakeholders. Sometimes it is also called as requirements engineering, And these changes include changes to strategies, structures, policies, business rules, processes, and information systems.


Who is a business analyst?


Business analyst is someone whose primary job is to analyze an organization and business performance along with the outside environment of the business and then report business, processor systems and they also focus on requirements which can bring effective changes in the business. In a simple meaning, according to the BABOK 3.0, A business analyst is any person who performs business analysis tasks and come up with a better solution to perform the task.



There are some roles that are very important to play by the business analyst to come up with a good outcome:

v  Analyze the business processes.
v  Analyze Business Needs.
v  Outlining Problems.
v  Planning and monitoring.
v  Making Report.
v  Change Management.

These roles consider being most important to play to get a good result. These activities mean consider the internal and external environment of the business and with the help of planning one can perform really well.


Knowledge Areas in BA


There are some key concepts from the book BABOK are:

1.    Business analyses Planning and Monitoring:
Describe the tasks that the business analyst has to perform like organize and         coordinate the efforts of business analysts and stakeholders

2.    Elicitation and Collaboration:
This term tells us that business analysts perform to prepare for and conduct elicitation activities and confirm the results obtained. Its also define how to collaborate with stakeholders throughout the business analysis activities

3.    Strategy Analysis:
The method describes that in order to clarify the need for strategic and technical importance, the business analyst has to collaborate with the stakeholders and do some alignment to change the strategies to the higher level to the lower level.

List of major tasks for the BA (Business analyst)

Tasks are the key piece to perform work that is informally or formally generated in the business analyst job. Although we talked about some knowledge area above, these tasks are that which BA must have in their profession.
 
·        Description
·        Inputs
·        Elements
·        Guidelines/Tools
·        Techniques
·        Stakeholders
·        Output



Comments

  1. Liliane Marino19 January 2020 at 19:10

    By Liliane Castano Marino

    At Scotiabank, the business analysts are responsible for ensuring the business requirements and solution vision are clearly developed to meet the needs of the stakeholders. The main functional competencies required to become a business analyst at this company are:
    • Leadership skills
    • Strong verbal and business writing skills
    • Skilled in the project lifecycle, its methodologies and outputs.
    • Analytical and problem solving skills.
    • MS Project, MS Office and MS Visio
    • Agile practices and frameworks – Scrum and Kanban
    • Problem-solving skills


    ReplyDelete
  2. Paramjeet Kaur Toor20 January 2020 at 14:31

    After reading this I came to know about Business analyst and their purpose in business. As business analyst do multiple tasks, similar business analyst of Scotia bank perform many activities for example analyse deposits and other transactions, financial analysis to ensure operations of financial institution. In financial institutions, BA' s final report is used to complete loan applications, approve credit lines and open accounts. They work with banking manger, loan officers and other financial professionals.

    ReplyDelete
  3. Hassan Kamara20 January 2020 at 15:57

    Upon reading this blog post I have learned a lot about the versatility of the business analyst role. The business analyst is given a lot of roles and responsibility's within an organization not to mention the various tasks that they are responsible for. I believe an easy way to describe a BA is to describe them as a change manager which happens to be one of their tasks, change management.

    ReplyDelete

Post a Comment

Popular posts from this blog

Chapter 8 - Starting the Solution by Harvinder Singh

  Chapter 8 Starting the Solution We are transferring from an abstract global to the physical international, from policy to technology, from problem to solution; from purpose to design: we have reached the closing quadrant of the Brown Cow Model, in which will be determined how we are going to enforce the essential business. With a solid know-how of the essence of the business, which means that the real trouble to be solved, it’s time to determine which components of that problem would advantage from being automated. The commercial enterprise analyst juggles many factors to determine the most appropriate product to build. Iterative Development Iterative development is a way of breaking down the software improvement of a large application into smaller chunks. In iterative development, feature code is designed, developed and examined in repeated cycles. With each iteration, additional functions may be designed, advanced and examined till there is a com...
Read more

Chapter 4- Business Use Cases - posted by Chelsia Palta

Understanding the Work  The product you intend to build must improve its owner’s work; it will be installed in the owner’s area of business and will do part of the work. It does not matter which kind of work it is commercial, scientific, embedded real-time, manual, or automated you always have to understand it before you can decide which kind of product will best help with it. Use Cases and Their Scope The term "use case" was coined by Ivar Jacobson back in 1987 as a way to describe an interaction between a system and a user of that system. Jacobson needed to break the system into smaller units, as he felt that object models were not scalable. Thus, to conquer the complexity and largeness of modern systems, he said it was first necessary to partition them into convenient chunks, and that these chunks should be based on the user’s view of the system. The Outside World Adjacent systems behave like any other systems: They contain processes and consume and/or...
Read more

Chapter 11 Non-Functional Requirements by Hassan

Non-Functional Requirements Non-Functional Requirements can be generalized as "what a product/system is supposed to be. these requirements tend to be qualities that the product should have and they should specify how well the product does what it does. the requirements should either make the product usable, fast, reliable, attractive or safe and they should describe the character/ the way the functions should behave. Look and Feel Requirements the look and feel requirements are key to the non-functional requirements and as a BA one must consider them for every project. These requirements can describe how a product/system's desired appearance, mood, spirit or overall style/ appearance. The look and feel requirements can further specify what the product/system intends to appear as and is not a detailed design of the product/system itself. The typical look and feel requirement should be simple to use, professional looking, attractive to its market, consistent with previ...
Read more