Eliminate Waste

Correct Answer: Get agreement from stakeholders to respect scope agreement for the duration of the Sprint and to add changes to a backlog for future Sprints.

The best strategy to handle frequent scope changes causing a waste of time in rework during the Sprint is to 'Get agreement from stakeholders to respect scope agreement for the duration of the Sprint and to add changes to a backlog for future Sprints'. This strategy is ideal in Agile methodology as it respects the principle of change adaptability but ensures it doesn't disrupt the work during a current Sprint Let us analyze why the other answers are not quite as effective: The suggestion to 'Ignore the scope changes and continue with the original plan' contradicts the Agile principle of accommodating change, and hence is not a good strategy 'Allocate extra time in each Sprint for rework due to scope changes' might sound like a plausible solution, but it is only a workaround and not a remedy. It would lead to inefficiency and dilute the process of Sprint planning Lastly, asking 'team members to work overtime to accommodate the changes' is neither sustainable nor fair. It could lead to team burnout and negative attitudes, leading to poor product quality in the long run.

Correct Answer: Evaluate materials inventory, order materials only when needed in future Sprints.

The correct answer addresses the issue of inventory waste by evaluating material usage and only ordering them when needed. The wrong answers either fail to address the problem or exacerbate it by overstocking or using unsuitable materials.

Correct Answer: Refactor code by abstracting common functionality into reusable modules.

Refactoring code and creating reusable modules will eliminate the waste created by code duplication. Other options either do not address the problem or make it worse.