PMI-ACP 無料問題集「PMI Agile Certified Practitioner」

（A）Periodically, at both the release and project level

（B）At a sprint level after each demo

（C）At the end of each sprint

（D）Holistically at the project level

（A）No. any work that is not released cannot be considered complete as per the definition of done (Do

（B）No, because the product owner has not reviewed the release implementation checklist for potential issues.

（C）Yes because the story has been tested and accepted by the business as per the definition of done (Do

（D）Yes, because the development work is complete and quality assurance (QA) and release are external dependencies.

（A）Work with the product owner to assess the impact for reprioritization.

（B）Ask another team that is less busy to handle the situation.

（C）Work on the customer request in the next iteration as a top priority.

（D）Work overtime to meet the customer request and the iteration commitments.

（A）Finish the product as it was initially planned.

（B）Re-estimate the project.

（C）Try to include as many changes as possible.

（D）Ask the product owner for approval to proceed.

（A）Daily coordination meeting

（B）Work collaboration platform

（C）Web conferencing

（D）Instant messaging tools

（A）Kept track of all current issues in a log. and then reviewed their progress at the end of every iteration

（B）Invited subject matter experts (SMEs)

（C）Measured and reported the outcome of improvement actions to the team

（D）Conducted problem detection to determine root causes

（A）Conduct a vision-sharing session with the teams to communicate the project's overall goals.

（B）Create a new team to deliver the dependencies, and bring team B under performance management.

（C）Swap team members from both teams so that deliveries are better supported.

（D）Discuss negotiating the delivery timelines with team A.

（A）Ask the customer to define the requirements of all stakeholders and select the most valuable features.

（B）Define all requirements so value can be added by delivering a high-level plan at the initiation phase.

（C）Ensure the client has a clear idea about the features and end product before the project starts.

（D）Suggest the product owner prioritize the work items by feature to maximize value.

（A）Deliver working software often with a preference for shorter timescales and changing requirements

（B）The importance of customer-centric product development practices over product-centric approaches.

（C）The belief that contributions and interactions are more important to success than processes and tools.

（D）The best architectures, requirements, and designs emerge from self-organizing teams.

（A）Encourage team members to write code that is tightly coupled together.

（B）Follow the project schedule created at the start of the project.

（C）Allow team members to choose improvement items and trust their judgment.

（D）Hold regular retrospectives and have team members commit to specific actions.

（A）Email all stakeholders with status updates

（B）Create a central repository for information, and provide access to team B

（C）Use an information board that will be visible to all passing through the workspace

（D）Provide team B with the information on an "as needed" basis

（A）Encourage the team to independently find a solution.

（B）Work with the team to create a solution for disseminating team knowledge throughout the company.

（C）Recommend hiring an external expert to advise on the best methods for sharing knowledge among teams.

（D）Suggest that all agile teams share weekly reports on their projects.

（A）Stop the team politely and suggest scheduling another meeting to discuss this specific matter.

（B）Inform the team that the meeting will be extended so there is time to hear what the team member is reporting

（C）Ask the team member to wait to discuss until the next daily coordination meeting, the team needs to review the current status.

（D）Dismiss the rest of the team from the meeting to focus on the problem reported by the team member

（A）Code is unit tested, code is peer reviewed, functional testing is passed, business testing is passed, and all acceptance criteria are met.

（B）Code is unit tested, all acceptance criteria are met, business testing passed, code is merged, code is peer reviewed, and documentation is updated.

（C）All acceptance criteria are met, documentation is updated, functional testing is passed, business testing is passed, and code is peer reviewed.

（D）Code is unit tested, all acceptance criteria are met, business testing is passed, functional testing is passed, code is merged, and documentation is updated.

（A）Inaccurate pressure on customers.

（B）Capacity planning will not be accurate.

（C）Delivery speed increases while morale decreases.

（D）Quality increases while output decreases.

（A）Ensure that QA team members who lack the appropriate skill sets sign up for training within the next few weeks

（B）Ask QA team members experienced with the new automation framework to cross-train the other QA members

（C）For upcoming sprints, have QA team members ensure that their respective skill sets are considered when acceptingstones

（D）Have QA team members with the appropriate skill sets spend extra time to help the team succeed

（A）Ask the team to develop user stories and build deliverables based on the requirements.

（B）Ask the team to restate the requirements and review them with the client.

（C）Ask the team to find user stories from similar projects for this customer.

（D）Try to motivate the team by recounting examples of their past successes.

（A）Run a spike at the end of the sprint to investigate the issue and reduce project risk.

（B）Focus on performance in the retrospective, then present performance indices and validate with the team.

（C）Start using feedback loops in every sprint to reevaluate project and team performance.C Emphasize business requirements and investigate the pair-programming approach