Marg LiquidPlanner

1. The timing feature is helpful for adding to your timesheet.

2. You can upload relevant documents to a task and all members of the task or project can view them.

3. The filtering and search functionality from the project view is decent.

1. The UI isn't intuitive.

2. The timesheet layout is the most useful, but if you remove the time from a task (i.e., to move to another day), the task disappears and you have to find it again on the main projects page.

3. The projects page layout is confusing; some of this is attributable to user error, but it gives a lot of unnecessary information that clutters the view.

4. The card view is not particularly useful.

5. If you're in a task, the documents you need may be held in a parent item and you don't have access to them unless you navigate away from the task.

None of these are major issues, of course, and as a product, it's fine. However, I think there are other systems that do a much better job at organizing the information and are more intuitive. All things being equal, I would choose a different product.

What problems are you solving with the product? What benefits have you realized?

The flexibility of this product is what give it the unique standout among all other products. LiquidPlanner is not just Scrum, Waterfall, Kanban. It is a mix of all the possibilities and the greatness and the flexibilities of all.

LP also has the great way of handling cross referencing, between different tickets as dependencies and dependent. These are something jira doesn't give you up front.

LP also has the greatness at regroup tickets in different orders in different groups. It makes managers easy to see tickets in different ways.

The strength of LP is also its weakness. It gives the management too much flexibilities. It breaks the concept of protective sprint . And also ticket references are not easy to manage, have to use actual ticket title to link. And this greatness of linking is the most headache within LP if people lost track of it. You need to have better view than simply these are tickets depends on these tickets and depends on other tickets.

And also, this time remaining concept is old concept. You need to bring in efforts and use points to measure. This way we not too focusing on 'time', how many hours left, and how many hours a human should work. We are not robots, and we are not all contractors. And most of all you guys need to understand what dos 'estimate' means within developers. There is no way anybody can estimate accurately up to the hour. Therefore, hour estimate is never going to be right.

I seriously don't like the concept of estimate of finishing a sprint on time. Unless you are trying to make all developers or software engineers as robots, there is no way we can make this close to estimation. You are empower management the wrong way. You are making upper management believe if they can control the hour, then they can have a smooth delivery. Again, we are not all contractors.

Recommendations to others considering the product:

What problems are you solving with the product? What benefits have you realized?

Good integration. Very flexible. The on-page timer is clutch.

Requires too much human process adherence

Recommendations to others considering the product:

What problems are you solving with the product? What benefits have you realized?

The only thing I like is being able to see recent uploads from other users.

It's not intuitive and there's no active calendar activity.

Recommendations to others considering the product:

What problems are you solving with the product? What benefits have you realized?

Rich tracking and resource management. Unique dynamic features. Drag-and-drop simplicity. Responsive site.

The product is expensive and there is a big of a steep learning curve.

What problems are you solving with the product? What benefits have you realized?