Wayfair's developers found difficulty with Jira tickets that lacked specificity, leaving the team hounding each other for required information.
To resolve this, they created a set of structured ticket templates for bug reports, design changes, feature requests, and optimization tasks that contained all the necessary information before being discussed or assigned.
The templates improved productivity, allowing developers to complete 3x more tickets in an hour-long meeting and shortening development cycles while making them more concise.
Through structured templates, this provides benefits such as accurate estimates, hitting the 100% completion mark on sprints consistently, and higher quality code.
This method requires a dedicated time investment, worthwhile for the long-term benefits it brings.
Start by assessing if documentation issues are widespread and altering templates based on the type of tickets that flow through your system.
Once guidelines are established, share these templates with everyone who will be writing tickets after collecting feedback to make sure everyone is comfortable with the changes.
You should enforce these changes strictly and not entertain any Jira tickets presented without specific details.
Wayfair's success in employing structured templates improved their team's process and morale, and it's worth a consideration for you too.