Free APMG-International AgileBA (Agile Business Analysis) Foundation (2015) AgileBA-Foundation Exam Questions

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

The role responsible for protecting models that go on to become part of the future 'As Is' support for the delivered solution is the Solution Developer. The Solution Developer ensures that the technical models, including system architectures and detailed design documents, are preserved and maintained. These models are crucial for ongoing support and future enhancements. The Agile BA supports this by providing clear and well-documented requirements and analysis that feed into these models, but the responsibility for their protection and maintenance lies primarily with the Solution Developer.

Reference: Business Analysis.pdf, Chapter 13, Delivering the Requirements

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.

An Agile project environment requires stakeholders to exhibit trust and partnership. Agile methodologies emphasize collaboration, transparency, and mutual respect between the project team and stakeholders. This collaborative approach ensures that stakeholders are actively involved in the project, contributing their insights and feedback, which is vital for the project's success. Stakeholders are expected to work closely with the project team, share information openly, and trust the team's decisions, fostering a partnership that supports the project's goals.

Business Analysis.pdf, 'In an Agile software development environment...the business analyst will be involved in supporting the business users'.

The technique used to categorize stakeholders according to their level of involvement in the project is the Power/Interest Grid. This technique is essential for identifying which stakeholders need to be managed closely and which can be monitored with less effort. The grid categorizes stakeholders based on their power to influence the project and their interest in the project's success. This categorization helps in devising appropriate stakeholder management strategies by assessing their power and interest levels and planning interactions accordingly.

Business Analysis.pdf, 'Stakeholder analysis...provides a means of categorising stakeholders in order to identify the most appropriate stakeholder management approach'.

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