Kanban Tool vs. Yamdu

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

Even for a small business like mine, Yamdu really felt like a one-stop shop for everything. It's hard to find a comprehensive software for film/video productions, but Yamdu has everything we need. The only thing that really held us back was the cost, ultimately. If anything, I would love a storyboarding feature that let you set the time per shot and build out a sequence in pre-production. I used Storyboarder for this currently and it's very helpful, especially for music videos, to be able to build out a storyboard, set a music/audio track to it, then play it back in real time and see the pacing of the shoot.

• 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

• Crewlists
• Callsheets
• Breakdowns

• 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

• More specific financial management reports.
• Creation of some instant messaging software for the team.

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.

This is one of Yamdu's strongest points.

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.

At the time, there really wasn't anything else like Yamdu. Especially as, in Celtx's case, at that time they weren't doing Excel/CSV exports of shot lists in the A/V format, something we required for what we were shooting. I understand that StudioBinder has increased its featureset the past few years, but Yamdu always felt like the most robust option and more familiar with the film/tv world.

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

• Positive impact, centralized place with some good tools for film productions
• Negative impact, not that flexible and as expected and strict pricing policy with little flexibility