The correct answer is to explain to the customer that tasks with lower priorities may be dropped from the project entirely. An Agile team is able to accept changes early or late in the project because of the iteration methodology. However,
the customer must understand that the team still needs to work within the project’s timeframe and budget. While new functionalities can certainly be added to the project, it’s at the expense of a lower-priority work item. Agile teams
are committed to being “agile,” or flexible, so dictating timeframes or having a lack of work/life balance is part of the Agile methodology. The project team should never be overworked to maintain the pace of the project work. The
other responses are incorrect. To accommodate higher-priority items which balance the fixed restraints of costs and time, lower-priority requirements should be dropped from the project scope; good management does not allow for the
cancellation of vacation days or time off; this negatively affects the team morale and team support of the project. Finally, requirements should not be on a separate list but prioritized into the product backlog. The existing product
backlog will already be mapped to the fixed time constraint.