Most Recent APMG-International AgileBA-Foundation Exam Questions & Answers

The Business Ambassador works with the Agile BA to prepare the users of the solution within the relevant business area for each incremental deployment of an evolving solution. The Business Ambassador acts as a liaison between the development team and the end users, ensuring that the requirements and feedback are effectively communicated and that the users are ready to adopt the new increments of the solution as they are deployed.

Business Analysis.pdf, 'The role of the business analyst in an Agile environment...supporting the business users'.

In Agile projects, user requirements are prioritized at multiple levels to ensure effective planning and execution. These levels include:

Project Level: At this level, high-level requirements are prioritized to align with the overall project goals and objectives.

Project Increment Level: Here, the prioritization focuses on what needs to be delivered in the upcoming increments or releases.

Timebox Level: During each timebox or iteration, the most critical and high-priority requirements are selected for development and delivery.

This multi-level prioritization ensures that the project remains aligned with business needs and adapts to changes effectively, delivering value incrementally.

Reference: Business Analysis.pdf, Chapter 10, Establishing the Requirements

Facilitated workshops are a technique used to gather user requirements. These workshops involve bringing together key stakeholders and users to discuss and document their needs and expectations for the system. This collaborative approach helps ensure that all viewpoints are considered, promotes consensus-building, and provides a comprehensive set of requirements that can guide the development process.

Business Analysis.pdf, 'Facilitated workshops are effective in gathering user requirements and ensuring all perspectives are captured'.

In Agile frameworks, particularly Scrum, the concept of a timebox refers to a fixed period during which specific work is completed and made ready for review. The optimum length of a timebox (or Sprint) is typically two to four weeks. This duration strikes a balance between allowing enough time to complete meaningful work and maintaining a high frequency of feedback and adaptation. Shorter timeboxes (such as one week) might not provide sufficient time to produce a potentially shippable product increment, while longer timeboxes (over four weeks) might delay feedback and the ability to respond to changes. The two to four-week duration supports the Agile principle of regular delivery of valuable software and facilitates a continuous improvement process through frequent retrospectives and planning sessions. Reference: Business Analysis document, sections on Agile practices and Sprint planning.

According to the MoSCoW technique, a 'Must Have' requirement is something that the project will fail without. These requirements are absolutely essential for the system to function and meet the business needs. If even one 'Must Have' requirement is not met, the project would be considered a failure. This prioritization ensures that critical functionality is delivered in the first increment and forms the basis of the minimum viable product (MVP).

The MoSCoW technique defines 'Must Have' requirements as mandatory and essential for the project's success, without which the system has no value.