良質なAgileBA-FoundationのPDF問題集でAgileBA-Foundation試験問題を試せます
一番最新のAPMG-International AgileBA-Foundation試験問題集PDF2024年更新
APMG-International AgileBA-Foundation 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
質問 # 28
What technique can be used to gather user requirements?
- A. Facilitated workshops
- B. Story Mapping
- C. MOSCOW
- D. Kano
正解：A
解説：
Facilitated workshops are a technique used to gather user requirements. These workshops involve bringing together key stakeholders and users to discuss and document their needs and expectations for the system. This collaborative approach helps ensure that all viewpoints are considered, promotes consensus-building, and provides a comprehensive set of requirements that can guide the development process.
References:
* Business Analysis.pdf, "Facilitated workshops are effective in gathering user requirements and ensuring all perspectives are captured".
質問 # 29
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 broken down into tasks and prioritised
- C. Requirements are displayed on a Story Board for visibility
- 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".
質問 # 30
What is the Agile BA role in the communication of requirements?
- A. Keeps the Prioritised Requirements List current and accessible
- B. Decides on any changes to the prioritisation of Must Have requirements
- C. Approves the Prioritised Requirements List
- D. Owns the Prioritised Requirements List
正解：A
解説：
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.
質問 # 31
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. Facilitator and Co-facilitator
- B. Facilitator and Workshop Owner
- C. Workshop Owner and Co-facilitator
- D. Business Visionary and Business Sponsor
正解：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".
質問 # 32
During Iterative development, what would be considered as an advantage of delivering a horizontal slice of the solution?
- A. To allow a high-level end-to-end prototype of the solution to be demonstrated
- B. To reveal that the solution has evolved in a way that is not right
- C. To enable Solution Increments to be more quickly and frequently deployed into live use
- D. To provide an initial view of the overall solution early in the project
正解：A
解説：
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".
質問 # 33
What is defined as anyone that is potentially impacted by the outcome of a project?
- A. Supporter
- B. Stakeholder
- C. Customer
- D. User
正解：B
質問 # 34
What phase in the DSDM process is used to review the success of the deployed solution in the operational environment?
- A. Foundations
- B. Evolutionary Development
- C. Post-Project
- D. Deployment
正解：C
解説：
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.
質問 # 35
As a minimum, which of the following would you find in an Agile Project Business Case?
1. Requirements
2. Reasons
3. Options
4. Recommendation
- A. 1,3,4
- B. 1,2,3
- C. 2, 3, 4
- D. 1,2,4
正解：C
解説：
As a minimum, an Agile Project Business Case should include the following components:
* Reasons: The justification for undertaking the project.
* Options: The different approaches or solutions that have been considered.
* Recommendation: The proposed course of action based on the analysis of options and reasons. These elements ensure that the business case provides a comprehensive rationale for the project, considers various solutions, and clearly states the recommended approach.
References:
* Business Analysis.pdf, "The business case follows a clearly defined format leading to clear recommendations to the decision-makers".
質問 # 36
Which role in the DSDM Team Model owns the Deployed Solution and is responsible for the realisation of any benefits associated with it?
- A. Business Visionary
- B. Business Ambassador(s)
- C. Business Sponsor
- D. Agile BA
正解：A
解説：
In the Dynamic Systems Development Method (DSDM) Team Model, the role that owns the deployed solution and is responsible for realizing any benefits associated with it is the Business Visionary. The Business Visionary is typically a senior project stakeholder with a clear understanding of the business objectives and the strategic direction of the organization. They ensure that the project remains aligned with business goals and that the benefits of the deployed solution are realized.
References:
* The Business Visionary is crucial in the DSDM framework as they own the deployed solution and are accountable for the realization of the associated benefits. This role is responsible for ensuring that the project's outcomes meet the strategic business needs and deliver the expected value.
In the DSDM (Dynamic Systems Development Method) team model, the role that owns the Deployed Solution and is responsible for the realization of any benefits associated with it is the Business Visionary. This role is pivotal in ensuring that the project delivers the expected benefits to the business.
* Business Sponsor: This role provides the overall funding and champions the project at the highest level but does not directly own the deployed solution.
* Business Visionary: This role is responsible for defining the business vision for the project and ensuring that the solution delivered meets this vision. They work closely with the team throughout the project lifecycle to ensure the project remains aligned with business goals. The Business Visionary is the key figure in realizing the benefits as they have the strategic oversight and authority to ensure the solution delivers value.
* Agile BA: While the Agile Business Analyst plays a crucial role in facilitating communication and ensuring requirements are met, they do not own the deployed solution.
* Business Ambassador(s): These stakeholders represent the end-users and ensure their needs are communicated, but they do not hold ownership of the deployed solution.
Thus, the correct answer is B. Business Visionary, as this role is integral to owning the deployed solution and ensuring the realization of associated benefits.
質問 # 37
Typically, what is the optimum length of a Timebox?
- A. Two to four weeks
- B. Two to six weeks
- C. One to three weeks
- D. Four to six weeks
正解：A
解説：
In Agile frameworks, particularly Scrum, the concept of a timebox refers to a fixed period during which specific work is completed and made ready for review. The optimum length of a timebox (or Sprint) is typically two to four weeks. This duration strikes a balance between allowing enough time to complete meaningful work and maintaining a high frequency of feedback and adaptation. Shorter timeboxes (such as one week) might not provide sufficient time to produce a potentially shippable product increment, while longer timeboxes (over four weeks) might delay feedback and the ability to respond to changes. The two to four-week duration supports the Agile principle of regular delivery of valuable software and facilitates a continuous improvement process through frequent retrospectives and planning sessions. References:Business Analysis document, sections on Agile practices and Sprint planning.
質問 # 38
In an Agile project, what category of Stakeholder is the Company Board of Directors?
- A. Programme
- B. Strategic
- C. Business
- D. Project
正解：B
解説：
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".
質問 # 39
What should an Agile BA do before agreeing to facilitate a workshop?
- A. Check that the date of the workshop does not conflict with a review point in a Structured Timebox
- B. Define a clear rationale for their involvement in the workshop should they be called upon to participate
- C. Assess their independence carefully and avoid facilitating workshops where they are required to have significant participation
- D. Identify workshop attendees from the wider stakeholder community
正解：C
解説：
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
質問 # 40
What is analysed using the Porter's Five Forces Analysis?
- A. Competitive position of an organisation
- B. Things that place a project at a disadvantage
- C. Likelihood of Government changes
- D. What the organisation is trying to achieve
正解：A
解説：
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".
質問 # 41
What technique is used to categorise Stakeholders according to their level of involvement in the project?
- A. Power/lnterest Grid
- B. Management Hierarchy
- C. Impact Mapping
- D. Organisation Chart
正解：A
解説：
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".
質問 # 42
What is the process of Requirements Engineering designed to do?
- A. Separate requirements into different groups and refocus them
- B. Manipulate requirements to reflect business needs
- C. Consolidate low-level detail into high-level objectives
- D. Evolve requirements from high-level objectives down to low-level detail
正解：D
解説：
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.
質問 # 43
In an Agile project, what demonstrates adherence to the Principle of Demonstrate Control?
- A. Develop the solution using a pre-defined process
- B. Plans are displayed in a shared workspace
- C. Solution delivers the MUST have requirements and no more
- D. Deliver all of the requirements, all of the time
正解：B
解説：
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.
質問 # 44
What is a role of the Agile BA when Handling Requirements?
- A. Approval of any changes that may be required
- B. Estimator of the effort required to deliver each Requirement
- C. Version control of all Requirements on the agreed list
- D. Identification of all Requirements at the outset of the project
正解：B
解説：
In an Agile environment, the role of the Business Analyst (BA) includes working closely with the development team and business stakeholders to clarify and prioritize requirements. One of the critical tasks during this process is to estimate the effort required to deliver each requirement. This estimation is essential for planning the iterations or sprints in Agile development. The BA collaborates with other team members to assess the complexity and effort involved, ensuring that the team can commit to achievable goals within each timeboxed iteration. This role does not typically include approving changes, version control, or identifying all requirements at the outset, which are handled by other roles or processes in Agile.
References:Business Analysis.pdf, Chapter 10, Establishing the Requirements
質問 # 45
According to the MoSCoW technique, what is a Must Have requirement?
- A. Something the project will fail without
- B. Painful to leave out, but the solution will still be viable without it
- C. Extremely important, but not vital for this increment
- D. Contributes to the Business Case in a marginal way
正解：A
解説：
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).
References:
* The MoSCoW technique defines "Must Have" requirements as mandatory and essential for the project's success, without which the system has no value.
質問 # 46
When modeling, the Agile BA should do enough to move on, and no more, relates to which DSDM principle?
- A. Deliver on time
- B. Demonstrate Control
- C. Collaborate
- D. Communicate continuously and clearly
正解：A
解説：
The principle that "the Agile BA should do enough to move on, and no more" directly relates to the DSDM (Dynamic Systems Development Method) principle of "Deliver on time." This principle emphasizes the importance of maintaining strict deadlines and delivering products within the agreed-upon timeframe. The idea is to prioritize work based on its necessity for the current iteration and ensure that the team does not spend excessive time on tasks that are not immediately essential. This approach helps in preventing scope creep and ensures that the project remains on track.
In the context of Agile, this principle aligns with the practice of iterative development, where each iteration is timeboxed, meaning it has a fixed duration. The goal is to produce a potentially shippable product increment at the end of each iteration. By doing just enough to move forward, the team ensures that they can deliver valuable functionality within each timebox, thus adhering to the principle of "Deliver on time." References
* Business Analysis.pdf, Agile systems development, DSDM principles section
質問 # 47
Which core characteristics should the Agile BA consider when planning and implementing change?
1. Culture
2. Communication
3. Contingency
4. Collaboration
- A. 1,2,4
- B. 2, 3, 4
- C. 1,3,4
- D. 1,2,3
正解：A
解説：
When planning and implementing change in Agile projects, the Agile BA should consider core characteristics such as culture, communication, and collaboration.
* Culture: Understanding the organizational culture is critical for implementing change successfully. This includes recognizing existing values, beliefs, and behaviors that may support or hinder the change process.
* Communication: Effective communication is essential to ensure that all stakeholders are informed and engaged throughout the change process. Clear, consistent, and transparent communication helps to build trust and ensures that everyone understands the objectives and benefits of the change.
* Collaboration: Agile methodologies emphasize teamwork and collaboration. Engaging stakeholders, including team members from different disciplines, ensures diverse perspectives and fosters a sense of ownership and commitment to the change initiative.
Contingency, while important, is not typically highlighted as a core characteristic by Agile BAs when planning and implementing change. Instead, Agile frameworks often focus on flexibility and adaptability to manage uncertainties rather than formal contingency planning. References:Business Analysis document, sections on change management, Agile principles, and the role of communication and collaboration in Agile projects.
質問 # 48
What does an Agile project environment require of Stakeholders?
- A. Ownership and Control
B Trust and Partnership - B. Command and Control
- C. Responsibility and Authority
正解：B
解説：
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.
References:
* Business Analysis.pdf, "In an Agile software development environment...the business analyst will be involved in supporting the business users".
質問 # 49
......
100%無料Agile Business Analysis AgileBA-Foundation問題集PDFお試しサンプル認定ガイドカバー率：https://www.jpntest.com/shiken/AgileBA-Foundation-mondaishu
PDF試験材料は2024年最新の実際に出るAgileBA-Foundation問題集：https://drive.google.com/open?id=1_0hB5Yif4jmRPin2V-DGatByj6EJLAMd