# data[].attributes.body
publish test cases covered. Alongwith sample ouputs say using snapshots or notebooks that are reproducible. This helps both validation as well as analysts to understand the feature

# data[].attributes.body
Keeping in mind the storage space of snowflake, it would be great if we can note down all the table names that we have created during our analysis on any of the JIRA ticket. So that post-analysis, we can delete those tables which can save some space
.

# data[].attributes.body
Start monitoring long on-going tickets and stop them from becoming a never-ending task.

# data[].attributes.body
If we are doing any development or fixes the test case document should be done and also it should get reviewed comment in Jira so it will help in reducing the chance of wrong/failure in work for that particular ticket

# data[].attributes.body
Keeping multiple channels of communication and task updates.

# data[].attributes.body
Taking long-running, non-sprint-divisible tickets out of sprint and track them separately rather than on JIRA

# data[].attributes.body
Also, at any point in the process, if we encounter that the dev or validator was unaware of the whole flow,  it should be taken offline and resolved instead of prolonging the ticket

# data[].attributes.body
Continue Validation along with major changes to the dev flow. We should ideally consider changes to process as a separate task.

# data[].attributes.body
I am here :)

# data[].attributes.body
Stop keeping such a large backlog! Determine which items should fit into the sprints, and which items should fit into a continuous improvement category

# data[].attributes.body
Update your Jira tickets more often. More than several times tickets have not been reporting the actual state in the proper swim lane.

# data[].attributes.body
Keep up the good work on closing bugs