APMG-International AgileBA (Agile Business Analysis) Foundation (2015) AgileBA-Foundation Exam Practice Test

Answer : D

In Agile methodologies, the role of a Business Analyst (BA) is pivotal in managing requirements. The Agile BA is responsible for ensuring that the requirements are clearly communicated, prioritized, and updated as needed throughout the project lifecycle. Keeping the Prioritised Requirements List (PRL) current and accessible is crucial because it ensures that all team members and stakeholders are working with the most up-to-date information, which is essential for the iterative nature of Agile projects. The BA works closely with stakeholders to gather and refine requirements and collaborates with the development team to ensure that these requirements are understood and can be implemented effectively. By maintaining the PRL, the BA helps the team stay focused on delivering the highest value features first, adapting to changes quickly, and ensuring continuous alignment with business needs. Reference: Business Analysis document, sections on Agile methodologies and the role of a Business Analyst in requirement management.

Answer : D

The phase in the DSDM process used to review the success of the deployed solution in the operational environment is the Post-Project phase. This phase involves evaluating whether the deployed solution has met its business objectives and delivered the expected benefits. It includes a benefits review to determine the extent to which the anticipated benefits have been realized and to identify any further actions needed to achieve these benefits fully.

The Post-Project phase focuses on reviewing the success of the deployed solution in the operational environment, assessing whether it has met the business objectives, and conducting a benefits review to evaluate the realization of the predicted benefits.

Answer : C

In an Agile project, adherence to the principle of 'Demonstrate Control' is shown by making plans visible and accessible to all stakeholders. This transparency ensures that everyone involved in the project can see the progress, understand the current status, and be aware of any changes. This is typically achieved by:

Displaying Plans in a Shared Workspace: This could be physical (like a Kanban board) or digital (like a project management tool) where plans, progress, and any changes are visible to the entire team and other stakeholders.

Regular Updates and Reviews: Frequent stand-ups, reviews, and retrospectives ensure that the team maintains control over the project by continuously assessing progress and making adjustments as necessary.

Collaborative Tools: Using collaborative tools that support transparency and open communication helps in maintaining control over the project's direction and progress.

These practices contrast with traditional methods where control might be demonstrated through strict adherence to predefined processes or by delivering all requirements regardless of their prioritization.

Business Analysis.pdf: Emphasizes the importance of transparency and regular communication in Agile projects to demonstrate control and ensure alignment with project goals.

Answer : A

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.

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

Answer : C

Prototyping is a powerful technique in Agile methodologies that serves multiple purposes. First, it is an effective way to achieve communication between stakeholders. By creating prototypes, stakeholders can see and interact with a representation of the final product, which helps in clarifying requirements and expectations. This visual and interactive approach ensures that all parties have a shared understanding of what is being developed. Second, prototyping makes elements of the evolving solution visible. This visibility allows stakeholders to provide feedback early and often, ensuring that the development process stays aligned with their needs and expectations. Prototypes can be adjusted iteratively based on feedback, which enhances the accuracy and relevance of the final product. Reference: Business Analysis document, sections on prototyping and stakeholder communication.

Answer : D

In the KANO Model, the three distinct types of customer needs are:

Expected (Basic Needs): These are the fundamental requirements that customers expect to be met. If these needs are not fulfilled, customers will be dissatisfied.

Normal (Performance Needs): These are the needs that customers explicitly state and expect to be fulfilled. The better these needs are met, the more satisfied the customers will be.

Exciters (Delight Needs): These are the features that go beyond customer expectations and provide delight when fulfilled.

'Teasers (When)' is not a type of customer need in the KANO Model.

The KANO Model focuses on Expected, Normal, and Exciters needs to categorize customer requirements and satisfaction levels.

Answer : C

When defining and planning a larger workshop, it is crucial for the Workshop Owner, with the support of the Workshop Facilitator, to ensure that all participants have enough information to make effective decisions. This involves thorough preparation, including distributing necessary documents and context ahead of the workshop, setting clear objectives, and ensuring that all participants understand their roles and the workshop's goals. This careful preparation helps to facilitate effective decision-making and productive discussions, leading to better outcomes from the workshop.

Reference: Business Analysis.pdf, Chapter 5, Investigation Techniques