5th October'23 - ACP Answer File - Daily Q&A
5th October'23 - ACP Answer File - Daily Q&A
Question - 1
Q. You have analyzed all the themes of your project and have assigned each one of them to one of
the four quadrants of a risk-value matrix that has a risk rating (high and low) on the y-axis, and a
business value rating (high and low) on the x-axis. What is the recommend approach to be taken for
the themes that fell under the “Low Risk” and “Low Value” quadrant?
A. Avoid
B. Do second
C. Do last
D. Do first.
Answer: C - “Do last” is recommended for themes that have been classified as “Low Risk” and “Low
Value”. [Cohn, M., 2006. Agile Estimating and Planning. 1st ed. Massachusetts: Pearson Education.
Page 85] [Problem Detection and Resolution]
Question - 2
Q. You are currently troubleshooting a pain point on your project. You ask the team to start using
Kanban boards to see the flow of work and work in progress limits to understand the impact of the
demand on the team or product. Which of the following is most probably your pain point?
Answer: C - Kanban boards are visual management tools that help manage the flow of the project
work. Recommending Kanban boards means there is something wrong with the flow of work. Based
on this logic, the project charter and team charter choices can easily be eliminated. Inefficiently
ordered product backlog will affect the release value and not the flow of work during the iteration.
The best answer to this question is, “unexpected or unforeseen delays”. [Agile Practice Guide, 1st
edition, Page 59] [Problem Detection and Resolution]
Question - 3
Q. Without attention to the highest value for the customer, the Agile team may create features that
are not appreciated, or otherwise insufficiently valuable, therefore wasting effort. How does an Agile
team mitigate this risk?
A. By creating the detailed project management plan with the help of the project manager.
B. By creating the detailed project management plan with the help of the product owner.
C. By creating the product backlog with the help of the product owner.
D. By creating the product backlog with the help of the project manager.
Answer: C - Agile teams do not create detailed project management plans. In Agile, the product
owners create the product backlog for and with the team. The backlog helps the team see how to
deliver highest value without creating waste. [Agile Practice Guide, 1st edition, Page 41] [Problem
Detection and Resolution]
Question - 4
Q. You are leading an Agile team responsible for developing an ERP system for an organization that
has recently transitioned to Agile approaches. The enterprise PMO has asked to develop a detailed
schedule Gantt chart and report Red/Amber/Green status against each project task on a weekly
basis. What should you do?
C. Negotiate with the enterprise PMO to only oversee projects following traditional lifecycles.
Answer: A - Agile approaches do not include detailed schedules and task status reporting; these are
traditional approaches. If the PMO is still using these tools, it implies that it hasn’t successfully
transitioned to Agile approaches. As an Agile practitioner, you need to educate and help enterprise
PMO transition to Agile approaches. [Cohn, M., 2006. Agile Estimating and Planning. 1st ed.
Massachusetts: Pearson Education. Page 51] [Problem Detection and Resolution]
Question - 5
Q. An Agile team wants to contract out part of the project’s scope of work. A fixed-price contract
hedges their financial risk but doesn’t provide the required agility in the relationship. A time and
material contract provides the required agility but doesn’t hedge the financial risk. Due to the
complexity of the project, agility is required but the team wants some degree of control over the
costs. What do you recommend?
Answer: D - Customers incur unwanted risk from a traditional time and material or cost
reimbursable arrangement. On the other hand, suppliers incur unwanted risk from a fixed-price
arrangement. One alternative is to limit the overall budget to a fixed amount using a not-to-exceed
time and materials contract. [Agile Practice Guide, 1st edition, Page 78] [Problem Detection and
Resolution]