Kanban Tool vs Smartsheet

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.

There were new vendors who needed to submit their documents by the sales department for legal and Risk department for reviewing and checking the validity of the documents, The way of escalation and attaching the documents and the vendor's data was well suited to be done through the smart sheet. As the sales use smart sheet tickets for submitting the vendor's details and attaching the documents. Through the Smartsheet automation process, a notification mail was sent to the legal and risk department for reviewing and the tickets were assigned already to the admins for validating . After the admin's review and tick mark on the check box of reviewing in the smart sheet which was customized than when its clicked send automated emails to the supervisors for approval, Then after the supervisor's approval, an automated mail was sent to the sales team for completing approval of the vendor. All of these scenarios and hierarchy did because of Smartsheet.

• 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.

• Its hard to overstate the value of familiarity. Being able to use a tool that has some familiarity takes away the time needed to train and orient employees on a new tool and allows an organization to hit the ground running.
• Smartsheet covers most of the basics of a project management tool, the usual tasks, milestones and project viewing options.
• For data viewing, you get multiple data viewing options including a calendar view (good for marketing teams and those who work around scheduling), Kanban, Gaant etc

• 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.

• Smartsheet set up is similar to Excel, yet when you upload an Excel file, things like conditional formatting are lost. Smartsheet has its own conditional formatting, and you have to reinstate the rules. It would be great if those would apply automatically once a file is uploaded
• Some Smartsheet management and access rules can take some tweaking to work properly. This may be a case of offering more info to admins so they can apply these better and with more efficiency

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.

It definitely meets our needs as far as organizing and archiving our tasks and files. As we train more staff to view it, I see opportunities for more improvement, which I am sure this program can handle. I look forward to seeing continued improvement from Smartsheet on their capabilities and functionality.

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.

Smartsheet is very easy to learn. However, while I have been able to pick it easily, Microsoft Excel and Project super users that I have trained on Smartsheet get bogged down in the differences and can find it frustrating. Explaining the differences ahead of time and why Smartsheet is being chosen instead of a different software seems to counteract those reactions

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.

I give this rating because it fills a niche in the market. MS Project scares many away from proper task management but there are limited tools our there, especially cloud-based that are mobile-friendly. Smartsheet fills this market gap, especially for small to medium-sized businesses. IT is not fair to compare it to MS Project, but fairer to see what gaps it fills.

It's absolutely paramount to take a few minutes to actually play with the software. It's nearly impossible to do anything wrong or make a mistake which cannot be fixed easily. Under the help menu is Live Training option. After you familiarize yourself with the commands, watch the live training for some in depth understanding of how to make the software fit your needs perfectly.

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.

Jira and Redmine are much more robust and technologically advanced project management solutions. I enjoy using either when managing a very large project. However, I prefer to use Smartsheet for my smaller to medium sized projects. As for Google Drive - I would say that Google sheets and Smartsheet are almost identical in my opinion when it comes to functionality. Personally I prefer to manage smaller projects via Google Drive, but it is a personal preference!

• 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.

• This has really opened up collaboration across teams. A lot less working in silos.
• It hasn't fully replaced any one tool so it means having to go to another place. Hopefully, we can eliminate a tool or two in the next six months.