AgileBA-Foundation Exam Questions & Answers

A project stakeholder can be categorized into different types, and understanding these categories is crucial for effective stakeholder management. The primary categories are:

Internal Stakeholders: These are individuals or groups within the organization who are affected by or can affect the project. This includes employees, managers, and other departments within the organization.

External Stakeholders: These include entities outside the organization such as customers, suppliers, investors, regulatory bodies, and the community at large.

Technical Stakeholders: Typically refer to individuals or groups responsible for the technical aspects of the project, such as IT staff, system architects, and developers.

Strategic Stakeholders: These are stakeholders who have a significant influence over the strategic direction of the project or organization, such as senior executives and board members.

Among these, the primary stakeholder categories are internal and external, as they encompass the broadest range of individuals or groups affected by the project. Internal stakeholders are particularly crucial as they are directly involved in the execution and outcome of the project. Therefore, option A (Internal) is a correct answer as it represents a primary project stakeholder category.

Reference

Business Analysis.pdf, Section on Stakeholder Analysis and Management

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

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

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.

One of the core principles of DSDM (Dynamic Systems Development Method) is to 'Build incrementally from firm foundations.' This principle emphasizes the importance of establishing a solid understanding of requirements and creating a stable base before moving forward with incremental development. This approach ensures that each increment builds on a reliable foundation, reducing the risk of rework and enhancing the stability of the overall solution.

Business Analysis.pdf, 'The Dynamic Systems Development Method (DSDM) defined a richer approach to prioritisation using the mnemonic MoSCoW'.