APMG-International AgileBA-Foundation Exam Actual Questions

In an Agile project, the Company Board of Directors is considered a strategic stakeholder. This category includes individuals or groups who have a significant interest in the success and direction of the project but are not involved in the day-to-day activities. Their role is to provide high-level guidance, oversight, and support to ensure that the project aligns with the organization's strategic goals.

Business Analysis.pdf, 'high interest/high power stakeholders are the key players and require positive management'.

The lifecycle of a Requirement in an Agile project includes the stages of Elicitation, Analysis, and Management and documentation. Elicitation involves gathering requirements from stakeholders. Analysis is the process of understanding, refining, and prioritizing these requirements. Management and documentation involve maintaining requirements and ensuring they are properly documented and tracked throughout the project lifecycle.

Business Analysis.pdf, 'requirements elicitation 189--93, requirements analysis 185--6, requirements management 218--22'.

The principle that 'the Agile BA should do enough to move on, and no more' directly relates to the DSDM (Dynamic Systems Development Method) principle of 'Deliver on time.' This principle emphasizes the importance of maintaining strict deadlines and delivering products within the agreed-upon timeframe. The idea is to prioritize work based on its necessity for the current iteration and ensure that the team does not spend excessive time on tasks that are not immediately essential. This approach helps in preventing scope creep and ensures that the project remains on track.

In the context of Agile, this principle aligns with the practice of iterative development, where each iteration is timeboxed, meaning it has a fixed duration. The goal is to produce a potentially shippable product increment at the end of each iteration. By doing just enough to move forward, the team ensures that they can deliver valuable functionality within each timebox, thus adhering to the principle of 'Deliver on time.'

Reference

Business Analysis.pdf, Agile systems development, DSDM principles section

In Bill Wake's INVEST model, the characteristic of a User Story that requires it to be kept to a few person-days or at most, a few person weeks is 'Small.' This characteristic ensures that user stories are manageable, can be completed within a single iteration, and allows for more accurate estimation and easier testing and integration.

Business Analysis.pdf, 'The user story will generally be framed to answer the questions Who? What? Why?... and be expressed in the format: 'As a {user role} I want {feature} so that I can {reason}.''.

During the feasibility stage of an Agile project, the requirements activities can indeed include defining the project objective as a high-level Epic Story. This is a common practice as it provides a broad understanding of the project scope and goals. Additionally, Epic Stories are often classified into Themes. Themes are groups of related Epics that align with larger organizational goals or strategic objectives. This classification helps in organizing and prioritizing work more effectively during the project lifecycle.

The feasibility study stage involves identifying broad requirements and considering various options to address these requirements. This includes defining the project objective as a high-level Epic Story and organizing Epic Stories into Themes for better management and alignment with strategic goals .