Okay, JIRA. JIRA actually, we have a sprint. We have followed the Agile methodologies and we have worked based on the sprints. For each sprint, we will take at least two to three weeks. So we will, initially we had a meeting and we will pick up those item, pick up 10 to 15 items, features and bugs related to that and we will put it in the sprint and we will work based on the priority and we use sprint to track that working progress. Basically, we will have the scrum and Kanban. Kanban, which is basically a tool, we can, we can visually, we can visually see what is the progress, like whether it is in the development or in the QA or in the development in done. So RSV and the UAT, so are in that release. So we can visualize the process of the development. So as a, as a team, we are we are working on one product and we just want to know and what the progress. So we can use the sprint in the JIRA and we can, we can use the JIRAs to track the progress actually. So we can, we can follow the Agile methodologies by following this. And so I haven't used the Rally and I have used the JIRA only. So also we can, in JIRA, we can, if there is any bugs, they, in QA, they can assign the bugs, QA can assign the, can create and assign the bugs and detailed reproduction, reproduce steps will be presented in the, in the ticket. And also if there is any feature, the BA will provide the user stories and the detailed user stories and what the expectations and what the flow will be, there will be presented with the diagram. So that's it.
