Get the latest tech news
Jira Tickets as a Checklist
Recently, as a function of rapid growth, we were encountering problems with newly released features and functionality due to missing critical considerations in the ticketing process. In other words, we would release functionality and then realize it had product impacts we didn’t foresee.
In other words, we would release functionality and then realize it had product impacts we didn’t foresee. In addition to the standard requirements and acceptance criteria, the product team member writing the story must go through a checklist of key considerations. This checklist concept is starting to reduce the number of reopens and follow on tickets and limits “oh shit moments” by ensuring that we are not surprised by issues we didn’t anticipate.
Or read this on Hacker News