## What Is the Problem With Mandatory Fields in Backlog Tools? Mandatory fields in backlog tools can make creating Product Backlog Items burdensome, leading teams to avoid the process or maintain multiple backlogs, both of which are counterproductive. >[!Experience] >I once worked with a team that tried to improve prioritization by making the due date field mandatory for all [[Work Items]]. Because users couldn’t leave it blank, they entered arbitrary dates—often defaulting to the current day—creating false urgency, constant escalations, and ultimately undermining the prioritization the field was meant to support. ## Works Consulted 1. [Product Backlog Item Attributes](https://www.scrum.org/resources/blog/product-backlog-item-attributes) | Scrum.org | Accessed 13 Jul. 2025. ## Connections follows:: [[1.1 Scrum Guide on Product Backlog Item Attributes]] topics:: [[Topics/Product Backlog Item Attributes|Product Backlog Item Attributes]], [[Friction]] ![[Footer]]