CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. APMG-International
  5. AgileBA-Foundation

Free AgileBA-Foundation Exam Braindumps (page: 6)

Page 5 of 14
PDF with 50 Questions

During which process phase is the Prioritised Requirements List baselined?

  1. Feasibility
  2. Foundations
  3. Evolutionary Development
  4. Deployment

Answer(s): B

Explanation:

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.


Reference:

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



During the Foundations phase, how is the Prioritised Requirements List used for Requirements Planning?

  1. Requirements allocated to each Development Timebox are arranged into a Story Map
  2. Requirements are broken down into tasks and prioritised
  3. Requirements are displayed on a Story Board for visibility
  4. Requirements and priorities are negotiated to allow the first increment to be planned

Answer(s): D

Explanation:

During the Foundations phase, the Prioritised Requirements List is used for Requirements Planning by negotiating requirements and priorities to allow the first increment to be planned. This negotiation ensures that the highest priority requirements are addressed first and that the development team can focus on delivering the most valuable features in the initial increments. This approach aligns with Agile principles of iterative development and delivering value early.


Reference:

Business Analysis.pdf, "Prioritisation is extremely important during solution development...The MoSCoW prioritisation categories are related to the development and delivery of the solution".



At which of the following levels are user requirements prioritised?
1) Project
2) Project increment
3) Timebox
4) Iterative cycle

  1. 1,2,3
  2. 1,2,4
  3. 1,3,4
  4. 2, 3, 4

Answer(s): A

Explanation:

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



What is the Agile BA role in the communication of requirements?

  1. Owns the Prioritised Requirements List
  2. Decides on any changes to the prioritisation of Must Have requirements
  3. Approves the Prioritised Requirements List
  4. Keeps the Prioritised Requirements List current and accessible

Answer(s): D

Explanation:

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.






Post your Comments and Discuss APMG-International AgileBA-Foundation exam with other Community members:

AgileBA-Foundation Discussions & Posts