PMI-ACP敏捷认证练习题（六）英文版

PMI-ACP敏捷认证练习题（六）英文版

Answers, Explanations and References

1) Where is your team most likely find the first warnings of potential problems?

1. Retrospectives
2. Daily stand-ups
3. Sprint planning
4. Iteration demos

Answer: B

Explanation: Daily stand-up meetings are typically the earliest source of warning signs or indications of potential problems, since these meetings occur every day. The third question in that meeting asks about impediments to progress, which could be signs of problems. Problems might also be uncovered in retrospectives and demos, but usually that isn't the earliest opportunity to discover them. Planning meetings are unlikely to help the team detect problems.

Reference: For more explanation, see PMI-ACP Exam Prep – Second Edition Page 332

 

2) Your upcoming project will be the organization's first use of agile, and the sponsor asks you about tailoring the new methodology. How do you respond?

1. Customizing the methodology upfront will allow us to streamline the adoption process.
2. Adapting the new methodology will be a good way for the team to learn about agile practices.
3. The team should become comfortable with the new methodology before we consider changing it.
4. We should wait to adjust our practices until we see where the team runs into difficulties applying them.

Answer: C

Explanation: Agile practices should be mastered and fully understood before we attempt to customize them. If we change the practices first and then encounter problems, we won't be able to tell if those problems are due to the changes we made or other causes.

Reference: Page 369

 

3) Although your team has completed their last iteration, it hasn't been "approved." What does this mean?

1. The team still needs to do refactoring and user testing.
2. In trying out the product increment, the customer thought of another feature to add to the backlog.
3. In the demo, the customer decided that the team hadn't completed one of the items selected from the backlog for that iteration.
4. The product increment hasn't passed QA testing.

Answer: C

Explanation: An iteration is "approved" when the product owner is satisfied that the product increment meets the iteration goal--the items selected from the backlog for that iteration. Although the customer might also think of another feature to add to the backlog, they would still approve the iteration if the work that was done meets the goal that was set. The other two options (missing refactoring, user testing, and QA testing) describe activities that should have been done during the iteration. If the team hasn't done them, that might be a reason for not approving the iteration. But they aren't the best answer to this scenario, since we don't have enough information to pick one of them.

Reference: Page 390

 

4) Your cutting-edge project has several major risks that the team wants to eliminate as quickly as possible. What's the best way for them to monitor how well this effort is going?

1. Risk-based spike
2. Risk-adjusted backlog
3. Risk burndown graph
4. Risk velocity chart

Answer: C

Explanation: The best tool for monitoring risk reduction is a risk burndown graph; this shows the project's evolving risk profile in one easy-to-understand chart. The team could also use risk-based spikes for their risk reduction efforts, and their latest risk-adjusted backlog would reflect the currently expected monetary value of the remaining risks. However, neither of these options directly addr