Our Developers and Project Managers both have indicated that sometimes (1/3 to 1/2) Jira tickets do not include sufficient analysis.
It seems like the Lead Developer is the best person to confirm this.
My first thought was to essentially add an "acceptance test" for accepting Issues onto a Sprint. So the Lead Dev would take a look at each Issue, confirm that it's got sufficient analysis and then move it into Todo. If it's not sufficiently "analyzed" then they'd kick it back to whoever created the Issue for clarification.
Any thoughts on this?
Where should this go?
New column on Sprint board? New column in the Backlog?
Ok, so you're suggestion this possible implementations:
#2 Might be easier to track in metrics (how often do Issues get sent back for more analysis)
That sound about right?
You've added new requirements/factors
- not all issues may need analysis, so you need to be able to specify if the analysis is needed.
- you want to report on how many issues "go back for analysis", which implies that perhaps the determination for needing analysis may not happen before the issue goes into a sprint
I think you need to first clarify for yourselves what the actual or desired process flow is with its requirements for transitions from one step to the next.
There are a lot of ways this could be done depending on
- your desired process
- how you want to be be able to segregate issues needing/not needing analysis
- how you want to segregate issues where the needed analysis has/has not been completed
- how strictly you want to enforce the process
- what reporting you want to do on the process
There are options for using custom fields, statuses, multiple boards, swimlanes (if you don't have other requirements for swimlanes), and workflows.
The options are also impacted by whether you are using a Company Managed project or a Team Managed project.
The simplest solution might be to have a status for "Analysis Needed". Have that as your first status for newly created issues. Assume Analysis is needed until it is determined that it is not. When you determine the analysis isn't needed, or is complete, move it to the next status that is an indicator it is ready for assignment to a sprint or ready for work in a sprint to which it is already assigned. Have all the statuses on just one Scrum board so that if a issue in an Active sprint is determined to need more analysis, it can be moved to the Analysis Needed status while remaining on the board. You would be able to report on issues that "go back" using a CHANGED or WAS JQL operators.
https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-operators/
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Jira Administrator
Configure Jira Software, Jira Core, or Jira Service Management, including global settings, permissions, and schemes.
Managing Jira Projects Cloud
Learn to create and configure company-managed projects in Jira Software and partner effectively with Jira Admins.
Learning Path
Become an effective Jira Software Project Admin
This learning path is designed for team leaders who configure Jira Software projects to match a team's processes.