Các khóa học đã đăng ký


PMI-PBA® Examination Content Outline (ECO) mô tả chi tiết về câu hỏi thi PMI-PBA®.

Bảng bên dưới xác định tỷ lệ phần trăm (%) câu hỏi từ mỗi domain trong số 5 domains sẽ xuất hiện trong bài thi PMI-PBA®.


% of Items on Test

Domain 1. Needs Assessment


Domain 2. Planning


Domain 3. Analysis


Domain 4. Traceability and Monitoring


Domain 5. Evaluation


Chi tiết PMI-PBA® Examination Content Outline

Domain 1. Needs Assessment (18%)

The Needs Assessment domain includes activities related to understanding a business problem or opportunity and evaluating various inputs to help develop an effective solution.

Task 1. 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.

Task 2. Collect and analyze information from a variety of sources using valuation tools and techniques to contribute to determining the value proposition of the initiative.


Task 4. Identify stakeholders by reviewing goals, objectives, and requirements in order that the appropriate parties are represented, informed and involved.

Task 5. Determine stakeholder values regarding the product, using elicitation techniques in order to provide a baseline for prioritizing requirements.

Domain 2. Planning (22%)

The Planning domain focuses on the preparation required to effectively manage the business analysis activities that will occur within the project. This includes establishing tools, policies, and procedures for the requirements management plan, requirements traceability, change management, document control, and acceptance criteria.

Task 1. Review the business case, and the project goals and objectives, in order to provide context for business analysis activities.

Task 2. 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.

Task 3. 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.

Task 4. 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.

Task 5. Select methods for document control by using documentation management tools and techniques in order to establish a standard for requirements traceability and versioning.

Task 6. Define business metrics and acceptance criteria by collaborating with stakeholders for use in evaluating when the solution meets the requirements.

Domain 3. Analysis (35%)

The Analysis domain centers on requirements management activities. Tasks include the elicitation, analysis, decomposition, acceptance, approval, specification, and validation of the requirements for a product or project.

Task 1. Elicit or identify requirements, using individual and group elicitation techniques in order to discover and capture requirements with supporting details (e.g., origin and rationale).

Task 2. 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.

Task 3. Evaluate product options and capabilities by using decision-making and valuation techniques in order to determine which requirements are accepted, deferred, or rejected.

Task 4. 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.

Task 5. Obtain sign-off on requirements baseline using decision-making techniques in order to facilitate stakeholder consensus and achieve stakeholder approval.

Task 6. 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).Task 7. 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.

Task 8. Elaborate and specify detailed metrics and acceptance criteria using measurement tools and techniques for use in evaluating whether the solution meets requirements.

Domain 4. Traceability and Monitoring (15%)

The Traceability and Monitoring domain includes the activities related to managing the life cycle of requirements. The tasks within this domain comprise the continuous monitoring and documenting of requirements as well as the communication of the requirements status to stakeholders.

Task 1. 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.

Task 2. 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.

Task 3. 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.

Task 4. 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.

Task 5. 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.

Domain 5. Evaluation (10%)

The Evaluation domain includes activities that relate to the assessment of how well the delivered solution fulfills the requirements and meets the business need. Tasks within this domain include testing the solution, determining if there are gaps, and obtaining sign-off.

Task 1. 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.

Task 2. 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.

Task 3. Obtain stakeholder sign-off on the developed solution using decision-making techniques in order to proceed with deployment.

Task 4. Evaluate the deployed solution using valuation techniques in order to determine how well the solution meets the business case and value proposition.


  1. Analytic tools and techniques (for example, decomposition, progressive elaboration, dependency analysis, gap analysis, impact analysis, risk analysis, and assessment)
  2. Backlog management
  3. Business rule analysis tools and techniques (for example, decision table, decision tree, rule catalog)
  4. Change control tools and techniques
  5. Collaboration tools and techniques
  6. Communication skills, techniques, and tools (for example, technical writing, business writing, working with virtual teams, presentation skills, verbal and nonverbal communication)
  7. Conflict management and resolution tools and techniques
  8. Contingency planning
  9. Data analysis tools and techniques (for example, data model, data dictionary, state diagram)
  10. Decision making tools and techniques (for example, Delphi technique, multi-voting, consensus building, options analysis)
  11. Development methodologies (for example, agile, iterative, incremental, waterfall)
  12. Documentation management tools and techniques
  13. Elements of a requirements management plan
  14. Elicitation tools and techniques (for example, brainstorming, focus groups, interviewing techniques, workshop facilitation, observation, document analysis, research, surveys, and questionnaires)
  15. Estimating tools and techniques (for example, estimation poker, quadrant analysis, averaging)
  16. Facilitation tools and techniques
  17. Interface analysis (for example, prototyping, storyboarding, interoperability)
  18. Leadership principles and skills
  19. Lessons learned and retrospectives
  20. Measurement tools and techniques (for example, service level agreement)
  21. Negotiation tools and techniques
  22. Organization assessment (for example, organizational readiness)
  23. Planning tools and techniques (for example, strategic and tactical)
  24. Political and cultural awareness
  25. Prioritization tools and techniques (for example, multi-voting, weighted criteria, MoSCoW)
  26. Problem solving and opportunity identification tools and techniques (for example, brainstorming, value engineering, scenario analysis, user journey maps)
  27. Process analysis tools and techniques (for example, user stories, use cases, process model, data flow diagrams, dependency graphs, events)
  28. Project methodologies (such as waterfall, agile, iterative, lean) and how they impact requirements and business analysis practices
  29. Qualitymanagement
  30. Reporting tools and techniques
  31. Requirements traceability tools and techniques
  32. Requirements types (for example, business, stakeholder, solution, transition, project, and quality)
  33. Root cause analysis (for example, Ishikawa/fishbone, 5 Whys)
  34. Scheduling tools and techniques
  35. Stakeholder analysis (for example, personas, role definition [RACI], job analysis, skills assessment)
  36. Systems thinking
  37. Validation tools and techniques (for example, acceptance criteria [for example, given-when-then] User Acceptance Testing)
  38. Valuation tools and techniques (for example, cost-benefit analysis, force field analysis, Kano model, net promoter score, purpose alignment model, SWOT analysis, value stream map)
  39. Verification methods and techniques (for example, inspection, test, walk-through, desk checking, peer review)
  40. Version control tools and techniques

Xem thêm

Tài liệu PMI-PBA® (Professional in Business Analysis)

Khóa học Business Analysis (BA) - Phân tích nghiệp vụ kinh doanh

Cũ hơn Mới hơn

Thông tin liên hệ

Thông tin chuyển khoản
Công ty Cổ phần ATOHA. Ngân hàng Á Châu (ACB). Số tài khoản: 6868 2468, PGD Tân Sơn Nhì, TPHCM.
Đăng ký khóa học
Chọn khóa học phù hợp bằng cách điền thông tin như link bên dưới. Tư vấn viên Atoha sẽ liên hệ anh/chị ngay.
Câu hỏi thường gặp

“Có. Atoha sẽ có chứng nhận hoàn thành chương trình đào tạo dành cho học viên và cung cấp 35 giờ đào tạo bắt buộc (1 trong 3 điều kiện thi lấy chứng chỉ PMP quốc tế)."

“Cả 2. Tài liệu có thể là tiếng Anh hoặc tiếng Việt tùy vào lớp. Atoha có thể đào tạo bằng cả tiếng Anh hoặc tiếng Việt."

“Chưa bao gồm. Học viên sẽ cần đóng phí thi trực tiếp cho viện PMI nếu muốn đăng ký thi, phí thi tham khảo 555usd/non-member và 405usd/member. Tham khảo thêm tại: www.pmi.org"

"Một số khách hàng doanh nghiệp tiêu biểu: 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),.."

Liên hệ ngay với Atoha để được tư vấn về chương trình phù hợp