APMG-International AgileBA-Foundation Exam Dumps

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.

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.

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.

The Prioritised Requirements List (PRL) is baselined during the Foundations phase. This phase is critical for establishing a clear understanding of the requirements and priorities before the development work begins. Baselining the PRL ensures that there is a formal agreement on the scope and priorities of the requirements, which serves as a foundation for subsequent development iterations.

Business Analysis.pdf, 'requirements validation is carried out to review and agree the requirements documentation...At this point the CIs that describe the requirements are said to be 'baselined''.

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. Reference: Business Analysis document, sections on Timebox structure and objectives.