You work at a large company as the Scrum Master of a team that has delivered valuable increments at a steadily increasing rate for over 2 years. At a Retrospective, the Developers on your team grumble about a new departmental policy that was recently announced: all effort estimates shall be entered into JIRA as story point values with decimal precision (3.1, 15.4, etc.). The purpose of the policy is to help Engineering Management improve the accuracy of forecasts and budgets, but your Developers believe that the new policy won’t help with those goals, and that it will just lead to a lot of unproductive arguments about estimates. They are clearly irritated, and you have concerns that their morale is going to suffer. What is your assessment of the situation, and what actions do you take?

As a Scrum Master, your role is to facilitate communication and resolve any issues that may arise within your team. In this situation, it's clear that the new policy is causing some discontent among the Developers.

Here's a step-by-step approach to address this issue:

1. Understand the Concerns: First, you need to fully understand the Developers' concerns. Why do they believe the new policy won't help with the stated goals? Why do they think it will lead to unproductive arguments? Gather as much information as you can.

2. Empathize and Validate: Acknowledge their feelings and concerns. It's important that they feel heard and understood.

3. Communicate with Management: Next, you should take these concerns to the Engineering Management. Explain the Developers' concerns and how the new policy is affecting their morale.

4. Seek Clarification or Modification: Ask the management if there's a specific reason for the decimal precision in the story point values. If the reason isn't compelling, request a modification in the policy.

5. Educate the Team: If the policy remains, you'll need to help your team understand why it's necessary and how it can actually benefit them and the project.

6. Monitor and Adjust: Keep an eye on the team's morale and the effectiveness of the new policy. If it's causing more harm than good, it may be worth bringing up with management again.

Remember, as a Scrum Master, your goal is to keep the team functioning at its best. If a policy is hindering that, it's your responsibility to address it.