[2024年11月14日] 365日更新、有効なAgileBA-Foundation知能問題集
ベスト品質のAgileBA-Foundation試験問題集でAPMG-Internationalテスト高得点を目指そう
質問 # 29
Which of the following are stages within the lifecycle of a Requirement?
1) Elicitation
2) Analysis
3) Evaluation
4) Management and documentation
- A. 1,2,4
- B. 1,2,3
- C. 2, 3, 4
- D. 1,3,4
正解：A
解説：
The lifecycle of a Requirement in an Agile project includes the stages of Elicitation, Analysis, and Management and documentation. Elicitation involves gathering requirements from stakeholders. Analysis is the process of understanding, refining, and prioritizing these requirements. Management and documentation involve maintaining requirements and ensuring they are properly documented and tracked throughout the project lifecycle.
References:
* Business Analysis.pdf, "requirements elicitation 189-93, requirements analysis 185-6, requirements management 218-22".
質問 # 30
What statement about prototyping is true?
1. One of the many ways to achieve effective communication between stakeholders
2. Make elements of the Evolving Solution visible
- A. Both 1 and 2 are true
- B. Neither 1 or 2 is true
- C. Only 1 is true
- D. Only 2 is true
正解：A
解説：
Prototyping is a powerful technique in Agile methodologies that serves multiple purposes. First, it is an effective way to achieve communication between stakeholders. By creating prototypes, stakeholders can see and interact with a representation of the final product, which helps in clarifying requirements and expectations.
This visual and interactive approach ensures that all parties have a shared understanding of what is being developed. Second, prototyping makes elements of the evolving solution visible. This visibility allows stakeholders to provide feedback early and often, ensuring that the development process stays aligned with their needs and expectations. Prototypes can be adjusted iteratively based on feedback, which enhances the accuracy and relevance of the final product. References:Business Analysis document, sections on prototyping and stakeholder communication.
質問 # 31
During Evolutionary Development, what happens in the Validation stage of the Requirement lifecycle?
- A. The full set of Requirements is approved
- B. The project objective is documented and agreed
- C. Each requirement is tested against its acceptance criteria and for alignment to the business need
- D. Users are interviewed to capture requirements in more detail
正解：C
解説：
During the Validation stage of the Requirements lifecycle in Evolutionary Development, each requirement is tested against its acceptance criteria and checked for alignment with the business need. This ensures that the requirements are not only met but also fulfill the intended business objectives. Validation involves thorough review and testing to confirm that the solution will deliver the expected benefits and meet stakeholder expectations.
References:Business Analysis.pdf, Chapter 10, Establishing the Requirements
質問 # 32
What should an Agile BA do before agreeing to facilitate a workshop?
- A. Assess their independence carefully and avoid facilitating workshops where they are required to have significant participation
- B. Define a clear rationale for their involvement in the workshop should they be called upon to participate
- C. Check that the date of the workshop does not conflict with a review point in a Structured Timebox
- D. Identify workshop attendees from the wider stakeholder community
正解：A
解説：
Before agreeing to facilitate a workshop, an Agile BA should carefully assess their independence. They need to ensure that they can remain neutral and unbiased during the workshop. If the BA is required to participate significantly in the discussion, they should avoid facilitating the session to prevent any conflict of interest or bias. This separation allows for a more balanced and objective facilitation process, ensuring that all stakeholders' views are considered fairly.
References:Business Analysis.pdf, Chapter 5, Investigation Techniques
質問 # 33
What would you NOT find in a Business Case?
- A. Allocation of roles for the project
- B. Metrics for measuring the success of the solution in operational use
- C. Anything that could adversely effect delivery of the outcome
- D. Ongoing operational, maintenance and support costs
正解：A
解説：
A business case typically includes several critical components that justify and outline the benefits of a project.
These components are:
* Metrics for measuring the success of the solution in operational use: This involves defining how the success of the project will be measured once implemented. Metrics might include performance indicators, key results, and other measurable outcomes to ensure the project meets its objectives.
* Anything that could adversely affect the delivery of the outcome: This would encompass risks and potential issues that could hinder the successful delivery of the project. Identifying these in the business case helps in planning mitigation strategies.
* Ongoing operational, maintenance, and support costs: These are detailed to provide a clear picture of the long-term financial commitment required for the project. It ensures stakeholders understand the total cost of ownership beyond initial implementation.
However, allocation of roles for the project is typically not part of a business case. This aspect falls under project management plans or other documentation related to project execution and governance rather than the justification and high-level planning that a business case provides.
References:
* Business Analysis.pdf: The structure of a business case typically includes sections on cost-benefit analysis, risk assessment, and performance metrics, but not on role allocation.
質問 # 34
During the Foundations phase, how is the Prioritised Requirements List used for Requirements Planning?
- A. Requirements allocated to each Development Timebox are arranged into a Story Map
- B. Requirements are displayed on a Story Board for visibility
- C. Requirements are broken down into tasks and prioritised
- D. Requirements and priorities are negotiated to allow the first increment to be planned
正解：D
解説：
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.
References:
* Business Analysis.pdf, "Prioritisation is extremely important during solution development...The MoSCoW prioritisation categories are related to the development and delivery of the solution".
質問 # 35
What are the main ingredients of a culture that supports Agile?
- A. Command and control
- B. Trust and ownership
- C. Confidence in chaos
- D. Risk and reward
正解：B
解説：
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".
質問 # 36
What phase in the DSDM process is used to review the success of the deployed solution in the operational environment?
- A. Evolutionary Development
- B. Deployment
- C. Foundations
- D. Post-Project
正解：D
解説：
The phase in the DSDM process used to review the success of the deployed solution in the operational environment is the Post-Project phase. This phase involves evaluating whether the deployed solution has met its business objectives and delivered the expected benefits. It includes a benefits review to determine the extent to which the anticipated benefits have been realized and to identify any further actions needed to achieve these benefits fully.
References:
* The Post-Project phase focuses on reviewing the success of the deployed solution in the operational environment, assessing whether it has met the business objectives, and conducting a benefits review to evaluate the realization of the predicted benefits.
質問 # 37
Which statement about Requirements Activities during Feasibility is true?
1. The Project objective can be defined as a high-level Epic Story
2. Epic Stories may be classified into Themes
- A. Both 1 and 2 are true
- B. Neither 1 or 2 is true
- C. Only 1 is true
- D. Only 2 is true
正解：A
解説：
During the feasibility stage of an Agile project, the requirements activities can indeed include defining the project objective as a high-level Epic Story. This is a common practice as it provides a broad understanding of the project scope and goals. Additionally, Epic Stories are often classified into Themes. Themes are groups of related Epics that align with larger organizational goals or strategic objectives. This classification helps in organizing and prioritizing work more effectively during the project lifecycle.
References:
* The feasibility study stage involves identifying broad requirements and considering various options to address these requirements. This includes defining the project objective as a high-level Epic Story and organizing Epic Stories into Themes for better management and alignment with strategic goals .
質問 # 38
In Bill Wake's - INVEST model, which characteristic of a User Story requires that it be kept to a few person-days or at most, a few person weeks?
- A. Small
- B. Valuable
- C. Estimable
- D. Negotiable
正解：A
解説：
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.
References:
* 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}.'".
質問 # 39
What is the Agile BA role in the communication of requirements?
- A. Owns the Prioritised Requirements List
- B. Approves the Prioritised Requirements List
- C. Decides on any changes to the prioritisation of Must Have requirements
- D. Keeps the Prioritised Requirements List current and accessible
正解：D
解説：
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. References:Business Analysis document, sections on Agile methodologies and the role of a Business Analyst in requirement management.
質問 # 40
Which of the following is a DSDM Principle?
- A. Build incrementally from firm foundations
- B. Build incrementally in Timeboxes
- C. Building iteratively from Feasibility onwards
- D. Build continuously from Foundations onwards
正解：A
解説：
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.
References:
* Business Analysis.pdf, "The Dynamic Systems Development Method (DSDM) defined a richer approach to prioritisation using the mnemonic MoSCoW".
質問 # 41
When defining and planning a larger Workshop what should the Workshop Owner consider doing, with the support of the Workshop Facilitator?
- A. Splitting the Workshop over two or more sites at different geographic locations
- B. Taking extra care when ensuring that participants have enough information to make an effective decision
- C. Not allowing Observers to attend the Workshop due to lack of space
- D. Sharing the role of Facilitator between two or more people
正解：B
解説：
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.
References:Business Analysis.pdf, Chapter 5, Investigation Techniques
質問 # 42
Identify the missing words in the following sentence:
In addition to preparing for the content of the Workshop, the [?] must oversee the preparations for venue and logistics.
- A. Business Visionary and Business Sponsor
- B. Facilitator and Workshop Owner
- C. Workshop Owner and Co-facilitator
- D. Facilitator and Co-facilitator
正解：B
解説：
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".
質問 # 43
Which of the following are perspectives of testing during Iterative Development?
1. Functional
2. Non-functional
3. Usability
4. Vertical
- A. 1,2,4
- B. 1,2, 3
- C. 2, 3, 4
- D. 1,3,4
正解：B
解説：
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".
質問 # 44
During Iterative development, what would be considered as an advantage of delivering a horizontal slice of the solution?
- A. To reveal that the solution has evolved in a way that is not right
- B. To enable Solution Increments to be more quickly and frequently deployed into live use
- C. To provide an initial view of the overall solution early in the project
- D. To allow a high-level end-to-end prototype of the solution to be demonstrated
正解：D
解説：
Delivering a horizontal slice of the solution during iterative development allows for a high-level end-to-end prototype of the solution to be demonstrated. This approach provides an overview of how different components of the system interact with each other and helps in identifying any integration issues early. It offers a comprehensive view of the entire system, which can be valuable for getting early feedback from stakeholders and ensuring that the overall architecture is sound before diving into detailed development.
References:
* Business Analysis.pdf, "horizontal traceability concerns tracing the requirement from inception to delivery".
質問 # 45
......
注目すべき時短になるAgileBA-Foundationオールインワン試験ガイド：https://jp.fast2test.com/AgileBA-Foundation-premium-file.html