FogBugz vs. Kanban Tool vs. KanbanFlow

FogBugz has been a very useful tool to our organization, and much preferred over other options we reviewed, mainly JIRA. There are still some improvements needed, but with the fairly recent acquisition by DevFactory, we have a great deal of hope for what is in store given DevFactory's focus and transparency. It seems like both DevFactory and FogBugz customers are eager for substantial improvements on the front-end, but there is/was a great deal of backend housecleaning that definitely needed to take place first.

Incentivized

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

Most of the project management software in existence today is focused on agile/sprint based processes. If your team happens to use Kanban instead, KanbanFlow is one of the best options for tracking work. It's quick to get started and learn and has a manageable feature set that won't overwhelm anyone.

Incentivized

• Tasks, Subtasks, and notes. All three of these areas were critical for our team. Tasks in Fogbugz were a bit easier to see than in more bug based software like Trello or JIRA
• The entire screen is used to view a task or case. Clicking on a task or case will open up and take up the entire screen, aside from the sidebar nav columns. I like to see details and I think Fogbugz does this very well, using up as much digital real estate as possible.
• Flowcharting in Fogbugz with Creately is nice - instead of getting an exterior flowchart software like Lucidchart, Creately works right in Fogbugz.

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

• Project monitoring with detailed management reports.
• Keep the team organized, focused on projects and demonstrate your goals in the tool.
• Simultaneous collaboration of the team in activities.
• Intuitive and user-friendly interface to use. Ease of learning how to use the tool.

Incentivized

• The simplicity of a single admin type user is not great because anyone who can create a job or client in the system, can also add and delete users. Content and User administrative rights should be separated.
• There are ways to change the terminology/lexicon within the tool, but we are not able to get it to work even after reaching out to tech support. So we are forced to use the system terminology that doesn't match up to our company making training a bit difficult.
• There is a subscribe function that you can opt into, there should be a way to add subscribers as you create a new task.

• 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

• I'm not sure if it has this or not because I've only been using it for about 6 months but we haven't quite figured out how to archive things. We have lots of data on that main page from Q3 and Q4 of last year but we need to figure out how to get it away from our main page so we can focus on new things this quarter
• I know when I was first added there were a few things the admin had to do in order to do that. All I remember is that it wasn't simple for them to get me hooked up. They had to do a few steps and then I was granted access. I don't know what exactly but I had to wait.

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

The integration with Teams is well suited. This works wonderful for my
company. Our team can easily prioritize tasks based on their importance.
It help our team identify and reduce inefficiencies in workflow. With
great visibility in data our team can make informed decisions. Ensuring
clear accountability and responsibility of team members

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 like JIRA a lot better than Fogbugz for many reasons. If I had a choice, I'd use JIRA every time

Incentivized

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.

I really like the simplicity and the subtasks found in KanbanFlow. It seems to be the easiest tool to get clients not using another method to use this without any challenges on their part. Trello has card dependencies, which is a nice touch. Trello also has a lot of add-ons, but I find them to be a little glitchy. Kanban Tool has really nice reporting and analytics.

Incentivized

• Saves time by quickly allowing Developers to make the necessary notes without getting bogged down in bloated UIs
• Has allowed us to look back easily and see the exact code changes made for the exact Case to aid in decisions for current changes, increasing the certainty of the decided path, without regression

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.

• Creating visibility of the status of all open work items
• Allowed for self-service ownership of projects by stakeholders

Incentivized