Leankit Review
June 21, 2016

Leankit Review

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with LeanKit

We use Leankit across the organization but have divided boards on a department basis. We use LeanKit as our primary development tool for all stories and defects.
  • Transparent as to the status of stories.
  • Allows customization of fields and colors.
  • Showing icons for who is assigned stories or blockers is very transparent.
  • Setting card counts is allowing us to progress to seamless integration.
  • Integration with other tools. Being in QA having a separate tool for labs and scripts and not integrating makes tracking tedious (we are using testrails).
  • Better notification on movement of stories of interest.
  • Stories going to bottom of column on creation.
  • We used Pivotal Tracker in the past and we were losing stories as project grew larger. With LeanKit we are doing more frequent releases and have better understanding of project status.
  • Setting up QA columns made assignment for the offshore team transparent.
  • Assigning stories is done with ease.
Being from QA I prefer SpiraTest and QC for the fact my team can do all our work in one program and it is linked. But the tech department as a whole prefers Leankit as it is the tool of choice based on ease of use and overall performance.
It is well suited for being Agile and progression of stories and ease of use.
Providing general information (requirements) can be done using tasks but you then have to drill down into those tasks for information and comments.

Planview AgilePlace Feature Ratings

Task Management
Resource Management
Gantt Charts
Support for Agile Methodology
Support for Waterfall Methodology
Document Management
Email integration
Mobile Access
Timesheet Tracking
Change request and Case Management
Budget and Expense Management
Not Rated

Using LeanKit

16 - Tech and Content team.
3 - We have a developer, project, and QA manager support Leankit but if needed it is easy enough for one person to do it.
  • Entering issue for the content team to address
  • Developing a new product.
  • Managing day to day operations.
  • We have linked Leankit to our release process thus once a story is release to production the story moves to archive.
  • Assigning tasks to offshore teams via emails is no longer needed.
  • Link to addition tools in the future.
  • Create addition boards so that the support team can use Leankit so we can save costs on Salesforce.
I see no reason why in the future my department would not be using this product.

Evaluating LeanKit and Competitors

Yes - Pivotal Tracker was replaced and we did this because tracking stories became a nightmare as the amount of tickets grew larger.
  • Product Usability
  • Prior Experience with the Product
The ease of use and searching and finding tickets was easily done.
I would not change a thing.

LeanKit Implementation

Change management was minimal - It do not effect us in any manner.
  • We did not have any issues we tried a demo version and went right to purchase.

LeanKit Support

It solves all our needs at this time.
Quick Resolution
Good followup
Knowledgeable team
Problems get solved
Kept well informed
No escalation required
Immediate help available
Support understands my problem
Quick Initial Response
No - Once we got running the knowledge based was all we needed.
We had a question about columns and card counts that was resolved quickly.

Using LeanKit

All users in our company were told our process but never had to be taught how to use the product.
Like to use
Relatively simple
Easy to use
Technical support not required
Well integrated
Quick to learn
Feel confident using
  • Drag and drop
  • Assigning stories.
  • Creating tasks.
  • Visually knowing status
  • Creating stories are tedious when creating them. You have to submit before adding attachment.