报名热线0755-8696 0365
设为首页 | 收藏本站

PMI-PBA 考试领域说明

发表时间:2021-07-28 10:53

PBA(Professional in Business Analysis)是PMI基于他们的人才三角,就战略和商业管理方面提出的一项培训和认证。(中国大陆在2016年6月正式启动)



PBA的考试形式规则和PMP类似。考试者要完成200道选择题(目前都为单选题)。PMI随机抽取25道题不计入分数,保证答对剩下175题中的106道就可以通过,如果想要稳妥一点通过的话,就要保证答对131道题。

考试的范围为BA的5个知识领域。占比如下。结果分为A(Above Target), T(Target), B(Below Target), N(Needs Improvement) 四个等级4个等级。最好的成绩就是5A了。

  1. 需要评估 18%

  2. 规划 22%

  3. 分析 35%

  4. 跟踪与监督 15%

  5. 评价 10%

下面详细介绍5个领域的知识内容:

Needs Assessment:The Needs Assessment domain includes activities related to understanding a business problem or opportunity and evaluating various inputs to help develop an effective solution.
需要评估:包括各种理解商业问题和机会的活动。评价各种输入以帮助制定有效的解决方案。

  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.
    使用问题和机会分析技术定义或审查商业问题或机会。从而制定解决方案范围说明,并且/或 为商业案例提供输入。

  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.
    使用价值评估工具和技术收集和分析从不同源头获取的信息。从而帮助确定积极的价值观。

  3. 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.
    协作制定项目远期和近期目标。通过提供清晰描述的商业需求和解决方案范围,是项目目标符合组织的目标。(近期和远期)

  4. Identify stakeholders by reviewing goals, objectives, and requirements in order that the appropriate parties are represented, informed and involved.
    回顾目标和需求以识别干系人,从而保证相关的个人或团体被恰当的通知和邀请。

  5. Determine stakeholder values regarding the product, using elicitation techniques in order to provide a baseline for prioritizing requirements.
    根据产品判断干系人价值。使用启发技术为已优先级排序的需求提供基线。

Planning: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.
规划:关注准备工作,使项目内的商业分析工作可以被高效的管理。包括为以下内容制定工具,政策,流程:需求管理计划,需求跟踪,变更管理,文档控制,验收条件。

  1. Review the business case, and the project goals and objectives, in order to provide context for business analysis activities.
    回顾商业案例、项目目标,为商业分析提供上下文。

  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.
    制定需求跟踪策略,使用跟踪工具和技术建立层级的需求监控和确认。

  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.
    通过以下活动制定需求管理计划,为交付期望的解决方案建立路线图。识别干系人,角色和责任;沟通协议;需求的启发,分析,文档化,管理,审批方法。

  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.
    通过以下活动为需求变更控制选择合适的方法,并整合到变更管理计划中。定义申请沟通渠道;变更过程管理;建立标准协议。

  5. Select methods for document control by using documentation management tools and techniques in order to establish a standard for requirements traceability and versioning.
    通过文档管理工具和技术选择合适的文档控制方法,从而建立标准的需求跟踪和版本化。

  6. Define business metrics and acceptance criteria by collaborating with stakeholders for use in evaluating when the solution meets the requirements.
    协调干系人,就解决方案如何到达需求建立商业度量和验收标准。

Analysis: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.
分析:关注需求管理的活动。任务包括产品或项目的需求的启发、分析、分解、验收、审批、规格、确认。

  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).
    通过单独或一组的启发技术启发和定义需求,从而发现和捕获需求,包括需求的细节(例如起源和根本原因)。

  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.
    通过以下技术分析、分解和阐述需求,例如依赖分析,接口分析,数据建模和过程建模。从而协作性的发现和澄清产品的选配项和能力。

  3. Evaluate product options and capabilities by using decision-making and valuation techniques in order to determine which requirements are accepted, deferred, or rejected.
    通过理性决策和价值技术评价产品的选配项和能力,从而决定哪些需求可以接受,延迟或拒绝。

  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.
    通过以下活动划分接受或延迟的需求,从而建立需求基线。包括平衡范围,日程,预算和资源约束;根据价值观进行优先级排序依赖分析,决策工具和技术。

  5. Obtain sign-off on requirements baseline using decision-making techniques in order to facilitate stakeholder consensus and achieve stakeholder approval.
    通过决策技术获得需求基线的签署,从而促进干系人的共识和获得干系人的批准。

  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).
    使用过程(用例、用户故事),数据和接口细节编写需求规格说明。通过沟通使需求达至可衡量和可执行(即可以进入开发)。

  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.
    使用以下方法进行需求确认,例如文档走查,原型,演示等确认方法。从而保证需求的完整,一致并符合目标和价值观。

  8. Elaborate and specify detailed metrics and acceptance criteria using measurement tools and techniques for use in evaluating whether the solution meets requirements.
    详述和明确度量细节和验收条件。通过测量工具和技术评估解决方案是否满足需求。

Traceability and Monitoring: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.
跟踪与监督:包括如下需求生命周期相关的活动。持续监控,需求文档编制,干系人需求状态沟通。

  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.
    通过跟踪工件或工具追踪需求,获取需求状态,来源和关系(包括依赖)。从而证实需求正在按说明进行交付。

  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.
    通过跟踪工件或工具对需求进行全生命周期的监控。从而保证适当的需求工件(例如模型、文档、测试用例)在各个时点被生产、审查和批准。

  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.
    在需求生命周期中,和适当的干系人沟通,更新需求状态。在跟踪工件或工具记录变更,从而跟踪需求直至关闭。

  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.
    和PM、干系人沟通需求状态,使其知悉需求的问题、冲突、变更、风险和全局状态。

  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.
    通过以下活动管理变更从而保持需求和相关工件的完整性。包括影响评估,依赖,风险符合变更控制计划,对照需求基线。

Evaluation: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.
评价:评价解决方案符合需求和商业需要的程度。任务包括:测试解决方案,差距分析,获取签署。

  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.
    确认解决方案的测试结果、报告和其他对应需求接受条件的测试证明。从而判定解决方案是否满足需求。

  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.
    通过质量保证工具和方法分析和沟通解决方案的差距和偏移量。从而帮助干系人解决如下三方面的差异,解决方案范围、需求和制定的解决方案。

  3. Obtain stakeholder sign-off on the developed solution using decision-making techniques in order to proceed with deployment.
    使用决策技术获取干系人对解决方案的签署从而推进开发。

  4. Evaluate the deployed solution using valuation techniques in order to determine how well the solution meets the business case and value proposition.
    使用价值分析技术评价已部署的解决方案。从而判定解决方案符合商业用例和价值的程度。


PMI, PMP, Project Management Professional, CAPM, PgMP, PfMP, PMI-SP, PMI-RMP, PMI-ACP, PMI-PBA, OPM3 and PMBOK are registered marks of the Project Management Institute, Inc.
会员登录
登录
其他帐号登录:
我的资料
留言
回到顶部