21 Backlog Testimonials

Industry
Company Size
15 per page
  • 15
Reset
  • “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.”

  • “Backlog's UI design is very easy to use compared to other task management tools, so I recommend it to those who are not familiar with IT tools.”

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

  • "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 is attractive because even members who are inexperienced with this kind of tool can use it easily to collaborate in real time.”

  • “Simultaneous work requires a very smooth and clear communication flow between our teams. In order to make it work, we must find good tools or applications to manage our projects that also allows all the teams to know about the progress. We are so happy to know about Backlog because the application makes all tasks easier to manage. We will continue to have Backlog as our project management tool for Petshopbox studio.”

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

  • "Before Backlog, information sharing was difficult. New project members experienced information gaps. After Backlog, people joining in the middle of a project could easily follow progress and get up to speed quicker."

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

  • "When managing projects with Backlog, we communicate within issues, so it’s always clear what we’re talking about and who’s involved. This is much more efficient than email."

  • "Backlog gave us the capability of managing requests in bulk, which means we are now able to assign and organize task priorities easily."