AgileBA-Foundation AgileBA (Agile Business Analysis) Foundation (2015) Exam Questions and Answers

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.

References :

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

The perspectives of testing during Iterative Development include Functional, Non-functional, and Usability. Functional testing ensures that the software operates according to the requirements. Non-functional testing assesses aspects such as performance, security, and reliability. Usability testing evaluates the user experience to ensure that the system is easy to use and meets user expectations. These perspectives ensure a comprehensive evaluation of the system from different angles, ensuring quality and effectiveness.

References :

Business Analysis.pdf, " Testing is an integral part of the iterative development approach... functional, non-functional, and usability aspects are continuously evaluated " ​​.

Porter ' s Five Forces Analysis is used to analyze the competitive position of an organization. This framework helps in evaluating the attractiveness and profitability of an industry by examining five key forces: the threat of new entrants, the bargaining power of suppliers, the bargaining power of buyers, the threat of substitute products or services, and the intensity of competitive rivalry. By understanding these forces, an organization can develop strategies to enhance its competitive position and profitability within its industry.

References :

Business Analysis.pdf, " An analysis tool that helps to evaluate an industry’s profitability and hence its attractiveness is Michael Porter’s Five Forces model " ​​.

In addition to preparing for the content of the Workshop, the Facilitator and Workshop Owner must oversee the preparations for venue and logistics. The Facilitator is responsible for ensuring that the workshop ' s objectives are met through effective facilitation, while the Workshop Owner ensures that all logistical arrangements, such as booking the venue and organizing necessary materials, are in place. Together, they ensure the workshop runs smoothly and achieves its goals.

References :

Business Analysis.pdf, " The success or failure of a workshop session depends in large part upon the preparatory work done by its facilitator and its business sponsor " ​​.

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 docu ments, 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.

References: Business Analysis.pdf, Chapter 13, Delivering the Requirements​

In an Agile project, the Company Board of Directors is considered a strategic stakeholder. This category includes individuals or groups who have a significant interest in the success and direction of the project but are not involved in the day-to-day activities. Their role is to provide high-level guidance, oversight, and support to ensure that the project aligns with the organization ' s strategic goals.

References :

Business Analysis.pdf, " high interest/high power stakeholders are the key players and require positive management " ​​.

A good User Story should include Acceptance Criteria. Acceptance Criteria define the conditions that must be met for the story to be considered complete and ensure that the developed feature meets the user ' s needs and expectations. These criteria provide a clear and measurable way to verify that the functionality works as intended and helps in achieving a shared understanding between the development team and the stakeholders.

References :

Business Analysis.pdf, " The user story will generally be framed to answer the questions Who? What? Why?...and include acceptance criteria " ​​.

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.

References :

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

A requirement in the context of Agile Business Analysis is understood as a service, function, or feature that a user needs. This definition encompasses the broad spectrum of what a requirement can entail, focusing on what the system or product must provide to meet the user ' s needs. By defining requirements this way, it ensures that the focus remains on the capabilities and functionalities that are necessary to deliver value to the user, rather than on specific solutions or objects which might limit the scope of what can be developed. References : Business Analysis document, sections on requirement definitions and user needs.

evel end-to-end prototype of the solution to be

Within a DSDM (Dynamic Systems Development Method) project, the Solution Development Team is responsible for estimating. This team includes developers, testers, and business representatives who collaboratively estimate the effort required for each requirement. Their combined expertise ensures that the estimates are realistic and achievable, facilitating effective planning and delivery of the project.

References: Business Analysis.pdf, Chapter 11, Documenting and Managing Requirements​

The process of Requirements Engineering is designed to ensure that requirements are carefully elicited, analyzed, and validated in a structured and rigorous manner. It involves evolving requirements from high-level business objectives down to low-level detailed specifications. This ensures that the final requirements are aligned with business needs and can be effectively implemented in the solution. The process typically includes several stages:

Requirements Elicitation: Gathering requirements from stakeholders through various techniques such as interviews, workshops, and observations.

Requirements Analysis: Refining and prioritizing the elicited requirements to ensure they are clear, complete, and feasible.

Requirements Validation: Confirming that the requirements accurately represent the stakeholders ' needs and are feasible for implementation.

Requirements Documentation: Recording the requirements in a formal document to ensure they are communicated clearly to all stakeholders.

Requirements Management: Managing changes to the requirements as the project progresses.

References:

The comprehensive process of Requirements Engineering ensures that requirements evolve from high-level objectives down to low-level detail, aligning with the needs and expectations of the business​​.

In an Agile project, adherence to the principle of " Demonstrate Control " is shown by making plans visible and accessible to all stakeholders. This transparency ensures that everyone involved in the project can see the progress, understand the current status, and be aware of any changes. This is typically achieved by:

Displaying Plans in a Shared Workspace: This could be physical (like a Kanban board) or digital (like a project management tool) where plans, progress, and any changes are visible to the entire team and other stakeholders.

Regular Updates and Reviews: Frequent stand-ups, reviews, and retrospectives ensure that the team maintains control over the project by continuously assessing progress and making adjustments as necessary.

Collaborative Tools: Using collaborative tools that support transparency and open communication helps in maintaining control over the project ' s direction and progress.

These practices contrast with traditional methods where control might be demonstrated through strict adherence to predefined processes or by delivering all requirements regardless of their prioritization.

References:

Business Analysis.pdf: Emphasizes the importance of transparency and regular communication in Agile projects to demonstrate control and ensure alignment with project goals​​.