Kanban Tool vs. Landscape Management Network (LMN)

Kanban is well suited for a fast-paced working environment for larger teams who want continuous communication with users. Kanban is good for rapid development and daily meetings for updates and statuses. Kanban is less suited for smaller teams or groups who don't require collaboration and constant communication with involved users. Kanban is time-consuming and it takes additional effort outside of your regular work to maintain and manage the tool.

Incentivized

LMN is best used if you go all in on it, otherwise you'll end having to use several other software to round it out. Making use of budgeting, estimating, timesheet, job costing, invoicing, payment, planning can all be done with this software. If used to it's potential, i can make running a business a seamless and timesaving endeavour.

Incentivized

• It provides a good basic overview of where tasks are on a timeline (particularly helpful for a pull-based approach).
• It provides a good collaborative space to have multiple folks commenting on multiple tasks.
• It does a good job of managing very basic visual elements of an agile development cycle.

Incentivized

• time tracking
• client data retention
• project estimating
• material data retention

Incentivized

• Kanban does not show the task or story clearly. You have to open the project separately to view the details of the project.
• Kanban gives a higher level project management view but it lacks customization and personal settings features.
• I would like to see Kanban provide mobile access to their tool, data, and board. This would be very useful for all companies and provide an increase in efficiency and productivity.

Incentivized

• Customer facing experience can be improved and modernized
• Estimating component has been stagnant can needs updates
• Better budgeting system would be good

Incentivized

We are more likely than not to renew our use of Kanban. Even with its limits, it still is a good product that fulfills our needs.

Incentivized

Again, this is a strong tool for software teams using Agile that are distributed across multiple geographies. It can be good for co-located teams too, but there are better platforms on the market like JIRA that provide a more built-out story.

Incentivized

This is the best tool I had a chance to work with- since I started to use it I saved a lot of time and I made my work go smoothly.

We've only tried JIRA Agile and KanbanFlow before. Kanban Tool was the one that our team actually liked and enjoyed working with. Also - it's been much easier to get started with and to understand than some of the other two (JIRA in particular). Although JIRA has many more features that we would have possibly used, the user feedback on it was so poor we were afraid that the negativity would create time wasted and less "job satisfaction" amongst the team.

We use both Service Autopilot and Landscape Management Network in tangent with eachother. They work well but, each has pros and cons that are easily eleviated by the other.

Incentivized

• Better communication and organization of ongoing projects.
• We are a very small team, with many areas to work on. Having everything in one system gives us a lot of visibility.
• Greatly reduced costs from using other tools that were much more expensive.

• Helps with project organization, knowing what a job needs and how much, etc.
• Allows us to track every labour hours to know where time is spent. Informs where we need to see improvement
• Makes estimating very quick for anyone. Save time in pricing jobs out so we can shorten sales pipeline.

Incentivized