IIBA Updated CBAP Exam Questions and Answers by malak

 A cost management plan is a document that defines how the project will be estimated, budgeted, and how changes to cost will be managed. It is a subsidiary plan of the project management plan and it describes the processes, tools, techniques, and methodologies that will be used to plan, execute, monitor, and control the project costs. A cost management plan also specifies the level of accuracy, units of measure, organizational procedures, reporting formats, and thresholds for cost variances and corrective actions. References:

Section 7: Project Cost Management - Q & As for the PMBOK® Guide Sixth …, section 7.1, page 1

Project Cost Estimation: How to Estimate Project Cost - ProjectManager, under What Is a Project Budget?

Project cost management basics - Clockify, under Step #1: Plan the resources

A trigger for re-prioritization is an event or a change that affects the relative importance or urgency of the project’s requirements or deliverables1. A new initial public offering (IPO) in the stock market is an example of such an event, as it may create new opportunities or threats for the online stock trading system and its stakeholders. The project team may need to re-prioritize the requirements or deliverables to align with the new market conditions and stakeholder expectations. The other options are not triggers for re-prioritization, but rather project issues or risks that need to be managed or mitigated. References: 1

 A requirement attribute is a characteristic or property of a requirement that provides additional information about it. Requirement attributes can help to manage, prioritize, trace, and verify the requirements. Some common requirement attributes are source, priority, status, owner, version, etc. One of the qualities of a good requirement is that it should be unambiguous, which means that it should have only one possible interpretation and avoid any confusion or misunderstanding. An unambiguous requirement is clear, precise, and consistent, and it can be easily verified and validated. An ambiguous requirement, on the other hand, can lead to errors, defects, rework, and conflicts among the stakeholders. References:

Characteristics of Effective Software Requirements and Software Requirements Specifications (SRS) - Jama Software, under Qualities of Good Requirements

The Four Attributes of High-Quality Requirements - ArgonDigital, paragraph 1

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, page 47

 A trainer is a role that works with the project team to understand the deliverables and then teaches the users of the deliverables how to utilize the project’s product. A trainer is responsible for designing, developing, and delivering training programs and materials that enable the users to learn and apply the skills and knowledge required to use the project’s product effectively and efficiently. A trainer also evaluates the effectiveness and outcomes of the training programs and provides feedback and support to the users and the project team12. An end user is a role that uses the project’s product to perform their tasks or functions. An end user is the ultimate beneficiary of the project’s product, and their needs and expectations are the primary drivers of the project’s requirements and scope. An end user also provides feedback and input to the project team throughout the project lifecycle, and participates in testing and validating the project’s product13. A database analyst is a role that designs, develops, and maintains the database systems and structures that store and manage the data and information for the project’s product. A database analyst is responsible for analyzing the data and information requirements and specifications, creating and modifying the database schemas and models, ensuring the data quality and integrity, and optimizing the database performance and security14. A stakeholder is a role that has an interest or influence in the project or the project’s product. A stakeholder can be an individual, group, or organization that is affected by or can affect the project’s outcomes and objectives. A stakeholder can have different roles and responsibilities in the project, such as a sponsor, a customer, a supplier, a regulator, a team member, or a subject matter expert15. References:

CBAP® Handbook

Trainer - iiba.org

End User - iiba.org

Database Analyst - iiba.org

Stakeholder - iiba.org