What is your primary use case for Jira Align?

We use Jira Align for business strategies, collaboration, and reporting. The solution allows us to manage the various products and features delivered on that platform.

We use the product for enterprise agile planning, aiding in project management and customer solutions.

I have used Jira Align for project management.

I use the solution for task reporting.

We use Jira Align for service desk and backlog project management.

When we receive a new customer requirement, the sales and marketing team inputs it into Jira Align. Then, the design team creates a task in Jira Align and assigns it to various engineers, such as hardware, electronics, and software engineers. We track the progress of these tasks and regularly update their statuses in Jira Align. This allows everyone to log in and follow up on the progress. Once the design phase is complete, we assign a plan to the production team to build the initial sample for qualifications and verification purposes. Once we've received approval from the customer or the marketing team, we transition the status from design to production. Our production planning coordinator then utilizes Jira Align to release the work order, especially if we've received a purchase order from the customer. From there, it's an operational process where the warehouse follows the demand, prepares the materials, and releases them to production for building the product. This represents the general progress of our workflow in Jira Align.

We use Jira Align for standard agile use cases.

Our use cases for Jira Align are particularly project-based. Whenever we go on a project, we utilize the solution, and at the end of the project, we drop that subscription. If needed, we go for a new subscription again.

I use Jira as a tool to keep everything in check for our projects. It helps me track and fix any issues that pop up during development, whether it is sorting out problems with the product or organizing tasks for the team. I also use it to store and manage user stories.

The solution can be used to track and update testing progress. We can use it for test management, creating stories, and grading test cases and plans.

Our clients use Jira Align for new development and defect tracking.

In my company, the solution is used for managing our day-to-day activities like kanban and scrum. We have a scrum team in our company. We had adapted scrum long ago. We have been an agile team for a long time now. We do have many use-case stories and backlog items. As and when we get any backlog items, we record all those things in Jira and then build a kanban board and scrum board to take care of with our daily activities.

Jira Align is an excellent tool for project management. We use it to manage our implementations and custom-developed solutions.

The solution helps me with real-time data visibility.

Mainly, we use the solution to maintain our backlogs, scrum processes, and project management. So, we create the entire structure. It is a brief project management tool. Regarding backlog management, the solution includes features apart from using the product for the product backlog, sprint planning, experiments, and defect management.

We use Jira for scrum-related activity and 80 people use this solution within our company.

We're creating a centralized place for our stakeholders and sponsors to have shared access to project details. My partners are normally the architects, engineers, and product owners. I work as a senior project manager and program manager. I have the scrum role added to me when we don't have any since I'm a scrum master too. I've been on the engineering side as an engineer, like onboarding and monitoring and creating all the meetings, and meeting with our customers more. I'm able to use Jira to help facilitate tasks related to various projects.

I mainly use Jira Align for planning apps in the department.

We are primarily managing larger portfolios. In this case here, I'm currently with a bank and this solution is used for larger portfolios of initiatives that are current within the bank. From there we're determining the course of action as it pertains to the work that is then performed by the individual departments.

We generally use it for reporting. It's to have transparency, to get to the incremental values. We do have value streams built up on Align and we get the metrics, how the program works, or the dependencies, not just between the teams, between the programs, or between the portfolios. What you have in Jira are the scalability and the agile approach. It's all about getting to all the stakeholders or the enterprise users so that they can see what is happening from the bottom to the top or from top to bottom and how it's happening. When it's all other agile tools, you could just view what each team is doing, and how the work is delivered within the team. However, it is going above and beyond the teams. When you are doing a scaled agile, when it all involves the whole enterprise, you use the Jira Align. It's a combination when you try to do the scaled agile combining the teams, combining the programs, and combining the portfolios, that is when the Jira Align is of most use. We use Jira Align on top of Safe 4.0 right now. They're not supporting Safe 5.0 yet, however, they are using it as VR; I used it on top of the framework as Safe 4.0.

I primarily use Jira Align for agile.

My company is a partner of Atlassian, a Jira vendor. We deploy the solution through a public cloud.

Our primary use case is for running agile sprints, for our weekly planning, task tracking, assignments, milestones, and reporting. I also use the burndown charts, velocity measurements, and developer productivity. We are customers of Jira.

We use the solution for schedule management and to do any updates on projects that we have had. I am a project manager and our organization put together a portfolio for each of us to have our own set of projects listed specifically under Jira that we had to provide regular daily updates for.

We have a semi-detailed project plan, and our software groups break down design feature X into sub-tasks in Jira and assign estimates, resources, and due dates. Then they manage a sort of agile sprint. They'll look at task items within the next two weeks, and they track that at the beginning of that two-week sprint. At the end of the two-week sprint, they again see where they ended up. We have had people using it to do essentially earned value calculations. They look at what percentage of work has been completed by estimating the total work for a task or set of tasks, and then they track hours spent against those tasks and percentage complete.

I used Jira Align when I was working with CACI. We use Jira Align to build and manage workflows, which allows each team to understand their work.

We mostly use it to track development work, tickets, user stories, and things like that. We put requirements, findings, comments, and stuff like that on the tickets so that the team can see what's going on. It is just a way to track work on various development tickets at a high level.