“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.”

“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.”

“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.”

"We used to manage and share reports by email, but they would get lost or forgotten. Backlog lets improved how we manage reports for each issue. All reports can now be found in the same project, making them much easier to review."

"Before Backlog, it was messy, hard to keep track, lots of emails flying around. Someone replied to this email but might miss another. And with attachments, it makes the emails really large, which is not feasible."

“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.”

“I felt we needed a tool that was easy to use for everyone in the company and that at the same time would give us the possibility to control and manage our work in one place.”

"Backlog makes it easy to tell who’s responsible for what within each project. Many project management tools make it difficult to understand who’s involved in projects, but Backlog makes it simple."

“The biggest benefits of Backlog are that it can be operated easily by anyone and that you can grasp individual work status in detail.”

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

"We work with a large number of clients who have never used project management tools before. We tested other pm tools, but the UIs were too complicated for everyone to master. Backlog offered both functionality and intuitiveness."

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

“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.”

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