Most Recent APMG-International AgileBA-Foundation Exam Dumps

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

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

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.

The main ingredients of a culture that supports Agile are trust and ownership. Agile methodologies emphasize the importance of empowering teams to make decisions, fostering a culture of mutual respect, and encouraging individuals to take ownership of their work. This environment promotes collaboration, transparency, and accountability, which are essential for the success of Agile projects.

Business Analysis.pdf, 'Individuals and interactions over processes and tools...Customer collaboration over contract negotiation'.