BUSINESS ANALYSIS (BA)

The field of business analysis (BA) has flourished in recent years and is seen as an important leadership capability in the execution of a project, program or portfolio.

Inaccurate requirements gathering consistently ranks in the top three causes of project failure yet only half of organizations have the resources in place to perform this function properly, according to the Pulse of the Profession® research conducted by Project Management Institute (PMI)

It is about time for businesses to consider in training employees about this skill. If you work with stakeholders in defining requirements, delivering project output solutions, this is the program you are looking for.

 

How to implement Business Analysis (BA) course

- According to business’s requirements, the program is designed to meet the participants’ expectations and solve each specific case.

Business Analysis (BA) course training location

- Flexible based on the arrangement of the business. Client's office is always a popular choice for in-house training.

Business customers suitable for Business Analysis (BA)

  • Software development and production company
  • Banking, finance, insurance
  • ERP company
  • Businesses interested in this topic
  • Individual participants who want to develop in the BA field

 

Business Analysis (BA) course content for reference

1. Needs Assessment

  • Define or review a business problem or opportunity using problem and opportunity analysis techniques in order to develop a solution scope statement and/or to provide input to create a business case
  • Collect and analyze information from a variety of sources using valuation tools and techniques to contribute to determining the value proposition of the initiative.
  • Collaborate in the development of project goals and objectives by providing clarification of business needs and solution scope in order to align the product with the organization’s goals and objectives.
  • Identify stakeholders by reviewing goals, objectives, and requirements in order that the appropriate parties are represented, informed and involved.
  • Determine stakeholder values regarding the product, using elicitation techniques in order to provide a baseline for prioritizing requirements.

2. Planning

  • Review the business case, and the project goals and objectives, in order to provide context for business analysis activities.
  • Define strategy for requirements traceability using traceability tools and techniques in order to establish the level of traceability necessary to monitor and validate the requirements.
  • Develop requirements management plan by identifying stakeholders, roles and responsibilities, communication protocols, and methods for eliciting, analyzing, documenting, managing, and approving requirements in order to establish a roadmap for delivering the expected solution.
  • Select methods for requirements change control by identifying channels for communicating requests and processes for managing changes in order to establish standard protocols for incorporation into the change management plan.
  • Select methods for document control by using documentation management tools and techniques in order to establish a standard for requirements traceability and versioning.
  • Define business metrics and acceptance criteria by collaborating with stakeholders for use in evaluating when the solution meets the requirements.

3. Analysis

  • Elicitor identify requirements, using individual and group elicitation techniques in order to discover and cap
  • Analyze, decompose, and elaborate requirements using techniques such as dependency analysis, interface analysis, and data and process modeling in order to collaboratively uncover and clarify product options and capabilities.
  • Evaluate product options and capabilities by using decision-making and valuation techniques in order to determine which requirements are accepted, deferred, or rejected.
  • Allocate accepted or deferred requirements by balancing scope schedule, budget, and resource constraints with the value proposition using prioritization, dependency analysis, and decision-making tools and techniques in order to create a requirements baseline.
  • Obtain sign-off on requirements baseline using decision-making techniques in order to facilitate stakeholder consensus and achieve stakeholder approval.
  • Write requirements specifications using process (such as use cases, user stories), data, and interface details in order to communicate requirements that are measurable and actionable (that is, suitable for development).
  • Validate requirements using tools and techniques such as documentation review, prototypes, demos, and other validation methods in order to ensure requirements are complete, accurate and aligned with goals, objectives, and value proposition.
  • Elaborate and specify detailed metrics and acceptance criteria using measurement tools and techniques for use in evaluating whether the solution meets requirements.

4. Traceability and Monitoring

  • Track requirements using a traceability artifact or tools, capturing the requirements' status, sources, and relationships (including dependencies), in order to provide evidence that the requirements are delivered as stated.
  • Monitor requirements throughout their lifecycles using a traceability artifact or tool in order to ensure the appropriate supporting requirements artifacts (such as models, documentation, and test cases) are produced, reviewed and approved at each point in the lifecycle.
  • Update a requirement’s status as it moves through its lifecycle states by communicating with appropriate stakeholders and recording changes in the traceability artifact or tool in order to track requirements towards closure.
  • Communicate requirements status to project manager and other stakeholders using communication methods in order to keep them informed of requirements issues, conflicts, changes, risks, and overall status.
  • Manage changes to requirements by assessing impacts, dependencies, and risks in accordance with the change control plan, and comparing to the requirements baseline in order to maintain the integrity of the requirements and associated artifacts.

5. Evaluation

  • Validate the solution's test results, reports, and other test evidence against the requirements acceptance criteria in order to determine whether the solution satisfies the requirements.
  • Analyze and communicate the solution's identified gaps and deltas using quality assurance tools and methods in order to enable stakeholders to resolve discrepancies between solution scope, requirements, and developed solution.
  • Obtain stakeholder sign-off on the developed solution using decision-making techniques in order to proceed with deployment.
  • Evaluate the deployed solution using valuation techniques in order to determine how well the solution meets the business case and value proposition.

Contact us:

Atoha Institute of Project Management - The key to professional project management

HCM: 69-71 Thach Thi Thanh, Tan Dinh Ward, District 1 

Hanoi: 299 Cau Giay, Dich Vong Ward, Cau Giay District 

Toronto: 10 Oakfield Dr, Toronto, ON, M8Y 1N7, Canada

Hotline: 0707 666 866 | HCM: (028) 6684 6687 | Hanoi: (024) 6686 1248

 

 

 

Contact Info

Bank Transfer Information
ATOHA Joint Stock Company. Asia Commercial Bank (ACB). Account number: 6868 2468, Tan Son Nhi branch, HCMC, Vietnam.
Register for a course
Choose the right course by filling in the information in the link below. Send us a message and we will contact you shortly.
Frequently asked questions

"Yes. Atoha will issue a certificate of 35 contact hours at the end of the course (1 of 3 requirements for the international PMP certification exam). Atoha's contact hours are pre-approved because we are PMI ATP Premier."

"Learning materials can be in English or Vietnamese depending on the class. Atoha can train in both English or Vietnamese."

"Not included. You need to pay the exam fee directly to PMI in order to register for the exam, the reference exam fee is 555usd/non-member and 405usd/member. For more information, visit: www.pmi.org"

"Some typical corporate customers are Nestle, Colgate-Palmolive, Castrol, Coca-Cola, Suntory Pepsico, Carlsberg, Schneider Electric, GEA, Sonion, Terumo BCT, Lazada, NEC, Apave, Vinamilk, VNG, MB Bank, FE Credit, PTI, Mobifone, VNPT, PV Gas, CJS, MB Ageas Life, Deha Software, PNJ, Square Group, Delta, Gamma, DSquare, Vascara, FECON, VNT19, Vingroup (HMS),.."