Free Practice Questions for APMG-International AgileBA-Foundation Exam

A business case typically includes several critical components that justify and outline the benefits of a project. These components are:

Metrics for measuring the success of the solution in operational use: This involves defining how the success of the project will be measured once implemented. Metrics might include performance indicators, key results, and other measurable outcomes to ensure the project meets its objectives.

Anything that could adversely affect the delivery of the outcome: This would encompass risks and potential issues that could hinder the successful delivery of the project. Identifying these in the business case helps in planning mitigation strategies.

Ongoing operational, maintenance, and support costs: These are detailed to provide a clear picture of the long-term financial commitment required for the project. It ensures stakeholders understand the total cost of ownership beyond initial implementation.

However, allocation of roles for the project is typically not part of a business case. This aspect falls under project management plans or other documentation related to project execution and governance rather than the justification and high-level planning that a business case provides.

References:

Business Analysis.pdf: The structure of a business case typically includes sections on cost-benefit analysis, risk assessment, and performance metrics, but not on role allocation​​.

When taking a holistic view of the business, the Agile BA typically assumes the role of a Business Architect. This involves analyzing all aspects of the business system, including processes, people, information, and technology, to identify opportunities for improvement and ensure alignment with business goals. The holistic approach requires considering the entire business environment to uncover potential areas for enhancement and support strategic objectives.

References:

Business Analysis.pdf, "There appears to be universal agreement that business analysis requires the application of a holistic approach"​​.

Before agreeing to facilitate a workshop, an Agile BA should carefully assess their independence. They need to ensure that they can remain neutral and unbiased during the workshop. If the BA is required to participate significantly in the discussion, they should avoid facilitating the session to prevent any conflict of interest or bias. This separation allows for a more balanced and objective facilitation process, ensuring that all stakeholders' views are considered fairly.

References:Business Analysis.pdf, Chapter 5, Investigation Techniques​

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."

References

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

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

References:

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

In the Dynamic Systems Development Method (DSDM) Team Model, the role that owns the deployed solution and is responsible for realizing any benefits associated with it is the Business Visionary. The Business Visionary is typically a senior project stakeholder with a clear understanding of the business objectives and the strategic direction of the organization. They ensure that the project remains aligned with business goals and that the benefits of the deployed solution are realized.

References:

The Business Visionary is crucial in the DSDM framework as they own the deployed solution and are accountable for the realization of the associated benefits. This role is responsible for ensuring that the project's outcomes meet the strategic business needs and deliver the expected value​​.

In the DSDM (Dynamic Systems Development Method) team model, the role that owns the Deployed Solution and is responsible for the realization of any benefits associated with it is the Business Visionary. This role is pivotal in ensuring that the project delivers the expected benefits to the business.

Business Sponsor: This role provides the overall funding and champions the project at the highest level but does not directly own the deployed solution.

Business Visionary: This role is responsible for defining the business vision for the project and ensuring that the solution delivered meets this vision. They work closely with the team throughout the project lifecycle to ensure the project remains aligned with business goals. The Business Visionary is the key figure in realizing the benefits as they have the strategic oversight and authority to ensure the solution delivers value.

Agile BA: While the Agile Business Analyst plays a crucial role in facilitating communication and ensuring requirements are met, they do not own the deployed solution.

Business Ambassador(s): These stakeholders represent the end-users and ensure their needs are communicated, but they do not hold ownership of the deployed solution.

Thus, the correct answer is B. Business Visionary, as this role is integral to owning the deployed solution and ensuring the realization of associated benefits.

The main focus of Impact Mapping is on benefits and goals. This technique helps to visualize the connections between the high-level goals of an organization and the specific actions that will help achieve those goals. It involves identifying the key stakeholders, the changes needed to meet their needs, and the specific deliverables that will contribute to the overall objectives. Impact Mapping ensures that all activities are aligned with the strategic goals of the organization.

References:Business Analysis.pdf, Chapter 14, Delivering the Business Solution​

In an Agile environment, interested stakeholders are encouraged to attend Daily Stand-up meetings to observe project progress. This practice fosters transparency and engagement by allowing stakeholders to see firsthand the current status of the project, any impediments the team is facing, and the planned tasks for the day. This regular interaction helps build trust and ensures that stakeholders are kept in the loop without the need for lengthy reports or additional meetings.

References:

Business Analysis.pdf, "Stakeholder management...frequent meetings and discussions about the direction the project is taking"​​.

The purpose of the Investigation step in a Structured Timebox is to understand the Timebox objectives. This initial step involves clarifying the goals and the scope of the Timebox, ensuring that all team members have a shared understanding of what needs to be achieved. This involves gathering detailed information about the requirements and the desired outcomes, which helps in planning the subsequent work. By focusing on understanding the objectives, the team can align their efforts towards meeting the specific goals of the Timebox, leading to more effective and efficient development cycles. References:Business Analysis document, sections on Timebox structure and objectives​​.