There was no access challenges faced while using Jira because Jira is a very simple tool. It was easy to document the requirements in the form of use cases or use stories in there as when then scenarios. Again, once I was working on the story, I would put it in a, you know, like requirement gathering state. I change the status and till I get a sign of I would not change the status back to ToDo. When I'm trying to get a sign of, I'll map it to the, you know, assign it to the client stakeholders who were part of Jira tool also. And drop an email, have a meeting with them and post their meeting. I'll ask them to give their sign up over the Jira comment section. And based on that sign up, I'll assign the Jira to the development team so that they can take it up or put it in backlog if it's not that of a priority. So Jira has not been a challenge. Sometimes it's getting a sign up from the client could have been challenging. But, you know, communication is the key skill. As long as I'm able to convey my thoughts and the purpose of that particular user story and some validations, I have been able to achieve and get a sign of accurately and timely manner.

