Trello vs waffle.io: What are the differences?
What is Trello? Your entire project, in a single glance. Trello is a collaboration tool that organizes your projects into boards. In one glance, Trello tells you what's being worked on, who's working on what, and where something is in a process.
What is waffle.io? Simple project management for your GitHub issues, free for open source. Track priority and rank for your GitHub issues across multiple repositories. Automatically see issues moved across a board for you, when you open pull requests or create branches.
Trello can be classified as a tool in the "Project Management" category, while waffle.io is grouped under "Kanban for GitHub Issues".
Some of the features offered by Trello are:
- Add a checklist to keep on top of all those little to-dos. There’s also a nice, big progress meter, because who doesn’t love a nice, big progress meter?
- Got a relevant file, image, or document? Attach it right to the card, and you’ll never have to go scrambling through your inbox looking for it later.
- Attach photos, drawings, sketches, and mockups to quickly illustrate ideas at a glance.
On the other hand, waffle.io provides the following key features:
- Issues displayed in columns based on GitHub labels
- Realtime updates
- Automatically moves issues across states when you take actions like creating Pull Requests
"Great for collaboration" is the top reason why over 701 developers like Trello, while over 41 developers mention "Tight integration with github issues" as the leading cause for choosing waffle.io.
Medium, Stack Exchange, and StackShare are some of the popular companies that use Trello, whereas waffle.io is used by Movielala, triGo GmbH, and Key Location. Trello has a broader approval, being mentioned in 2181 company stacks & 1770 developers stacks; compared to waffle.io, which is listed in 37 company stacks and 23 developer stacks.
What is Trello?
What is waffle.io?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using waffle.io?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
We originally decided to use Trello because GitHub Issues were getting way too crowded and overwhelming. Also, GitHub Issues are great for detailed bits of work, but they're not so great at high-level tasks or buckets of work. The milestones stuff in there just doesn’t cut it.
We love Trello. It's great because it’s super flexible. Almost to a fault. The one thing I wish it had: velocity. Not sure why they don’t add that, but I would so use it. Right now we just add an estimate of hours at the top of the description field. I also wish they had a more robust Calendar and concept of time. Trying to get Trello to act like a product planning tool is almost impossible. And using other tools is a nightmare. So we’re kind of stuck using Trello as-is. But Trello as-is is > all the other PM tools we’ve tried (and we’ve tried a lot).
The various projects that we'll have on the go at any point in time, within the R&D team, are internal projects that will prove long term benefits. We use Trello to track individual tasks that comprise those projects, and work with them in an Agile approach.
리스트 목록: Inbox, ToDo, Doing, Done, 얘기해봐야할 것들, 디자인 Preview,런칭 후 개선할 것들, Document(컨플루언스 대신 씀. 로드맵 공유)
원랜 Github issue로 이슈트래킹을 했었는데 첫 개발땐 워낙 바뀌는것도 많고 빨리해야될것도 많고 해서 트렐로로 유연하게 관리하니까 좋음. 앞으로 사용자가 생기고 소스코드 풀면 github issue로 관리할 생각
Trello is the core of our workflow. All tasks to be done go on Trello, and whenever you have to work on something, you go on Trello to check out what you could work on. And it works perfectly for us.
I use Trello for organizing projects. Typically I break a project up into sections, add and prioritize tasks for each section. For largest projects, I'll break it into multiple trello boards.