“Backlog allows you to store some documentation so that later, rather than raising a new issue again, we can just refer back to the attached documents or shared files. So, you have a sort of FAQ or manual to refer to.”

“We chose Backlog because it’s user-friendly, easy to track multiple projects, and provides Gantt charts and many other features.”

“Backlog is attractive because even members who are inexperienced with this kind of tool can use it easily to collaborate in real time.”

“We saw how our client managed their projects very effectively in Backlog. From then on, we also started using it.”

“At that time, I tried to be a kind of bridge between developers and non-developers. But sooner or later, it turned out that I was the bottleneck of the communication. I thought then that we should use the same tool for communication.”

“If I want to present my workload to my managers, it’s very easy. Like, ‘hey this is me, it is full’. There’s a lot of tools like that in Backlog, especially when you look at the Gantt Chart, and the filtering of issues assigned to me.”

“With the Wiki feature, it’s where we store information that is relevant to the specific project. So it’s like documentation for the specific project. We also used Google Docs before but it’s kind of hard to organise the documents there alone.”

“Because Github charges per user, it quickly gets expensive, particularly when we’re working with part-time developers. Github doesn’t differentiate between part-time and full-time users. So this is where the package setup of Backlog was a good aspect for us.”

“In Backlog, it’s easier to change the task status and status of pull requests, etc. So it saves time as a project manager, and as a developer, it’s easier to use and to learn to use.”