We have several different teams and they all have different boards for tracking, tasks, projects, and then completing work.

I use a board at the department level to track all of the projects that we are working on as a company. At the group level, we have five different technology teams. Each one of those has its own teams. Some of them have three teams, some have one team. I create cards on the department level for projects that we then send down to the individual groups. Those groups then take those cards, create more tasks, and then send those tasks down to the team. The team then breaks those into their daily tasks. I think LeanKit just helps us delegate and send priorities and work down to the different groups and then move things if we need to.

I have two boards where it is a bit of a pilot, one of which was my suggestion to our organization. 

Predominantly, we are using LeanKit for our agile management. Basically, we are a PMO. We belong to the PMO organization within our company, and we deploy products that are used by our project management team. Typically, we use LeanKit for that purpose.

LeanKit is a SaaS application. They update the version, and everybody gets the same version, as far as I understand. I don't think we are going to be in a prior release and then jump into the new release. 

With Leankit, our PMO has a single solution and Program Increment Board to integrate teams and projects and align priorities across the entire program - which consists of 22 Scrum teams. 

It allows us to track our PI goals, sprint goals, dependencies, and impediments across all of the teams creating extreme visibility and predictability for product owners, stakeholders and the teams. With integration into JIRA and the team boards, it allows us to have one single source of truth while not overwhelming the teams with the added responsibility of manually updating their epics, stories, and/or tasks. 

There is a group in our company that tracks all of the capital spend in the company. They are using LeanKit to track cash and incentives also. It has also been used for incentive tracking since earlier this year. 

In addition, various teams are using it for the Kanban board functionality, which helps them track work. My team, for example, created a board to share with our customer success manager. It's shared with Planview and we put cards out there when we have questions or when we need a demo. It's also how we track remote office hours. 

There are other groups within the company that are using these boards for various activities. Use cases pop up all the time. We're a very large company.

We have a unique use case. Normally, people use LeanKit to track agile development in IT. However, we use the product to track our savings on capital projects.

We're using LeanKit for our IT teams right now, but we're hoping to utilize it enterprise-wide. We're using it for Kanban boards and methods to help with our lean and Agile workflows.

We use this solution in a pretty standard way for project management. Most importantly, we start with the request phase, which is one of the most important use cases for us. We were missing this ability earlier. Now, across the organization, any department can provide us with an overview or a business case of why they want us to work on a project by putting a request through.

We created request forms with the help of Planview PPM Pro. These help us gather important metrics. Several gauge stages are included in the process. 

There is also an approval process in which we review the request. We have the option to send the request back if we want to ask more questions. 

Once the request is approved, we start working on the use case and creating a project out of it. We start by assigning a project manager at which point the request becomes a project. We can then start populating the project in LeanKit with information from the project charter, which is an overview of the project. We can also create project tasks in LeanKit. 

Next comes the project planning, execution, monitoring, and closure. The last use case in this entire journey is capturing the lessons learned through the PPM Pro platform by delivering those forms to all the stakeholders. We look at both the things we did right and what we need to learn. 

This solution takes us from request to closure. 

In our organization, a lot of individuals have been using it to plan out their work or keep track. Some people here are using it for things they know are coming but haven't started. They are using it to track the progress of things going on in their department and then be able to see and share it with their staff to give visibility.

We are using its most current version because it is accessed through the web. It is SaaS-based.

We do it to make work visible on one board in the area of sales and transformations on another.

I am just a user. I do not administrate it nor do I manage it. I do not set anything up for it. I am just opening up cards.

Our clients use LeanKit heavily. I have seen it at Walmart, for example.

We are currently using LeanKit as a task tracking tool for all of our teams. Since COVID hit, we just wanted to use it to see where our teams are on their work, see where they need help, and also to keep track of how long specific projects are taking. We also use it to make sure our employees are not being overloaded with any work.

We're still early in our organization of actually adopting it. We transitioned to LeanKit from JIRA. We wanted to find a way to cut costs. We realized that we can use both, but since they're both task tracking tools, we wanted to just utilize the one.

Third-party integrations are one of the things that I've heard a lot of users not necessarily happy with. One of the teams is our security team. They use some tools that provide automatic updates and information provided to their tasks and stories in JIRA. But those third-party applications don't work automatically with LeanKit right now. We haven't utilized the APIs at all. I don't know if these other tools have access to the APIs to develop any integration with them. That's something we haven't really done any research into as we're still getting users into it.

The third-party aspect is still the one thing that we liked about JIRA. They have so many third-party extensions and applications along with it and it seems that LeanKit is still gaining ground in that area.