If I'm looking for ways to organize my schedule (to-do style), which of these should I use? I already use Trello and it's great, but I am wondering if I should switch if there are other programs with more functionality. I'm looking to compare what's offered with the free plans for all of these options.
Both Asana and Trello support Kanban style project tracking. Trello is Kanban-only project management, knowledge management, actually card-management tools. Asana is much more complex, supports different project management approaches, well integrated and helpful for any style/type project.
We choose Asana finally, but still some projects kept in Trello
Procezo is an excellent free-for-life task managing tool with several benefits. Its clear, user-friendly interface is perfect for small businesses and startups as well as enterprise-level use. It makes it a seamless transition from any other project management tools. Its simple but effective layout allows new users to quickly adapt to its ever-expanding set of features. Procezo allows users to create boards and provide access to users or teams as required, set priority and precedence of the task and allowing for subtasks and discussions to be created. With unlimited tasks, users, projects and free support, Procezo is quickly making its way into businesses from across the world and the ultimate growth hack tool.
I loved Slack. We used it for discussion. But somehow, it was always difficult to get things done. HeySpace is what replaced Slack and Trello as it combines the functionality of both tools.
So, now we keep on discussing as we did on slack, but once we to a point where we want to do something, we create tasks on a board and distribute them.
trello has a much simpler interface and easy to learn for any team member. asana might have more features and configuration options but do you really need a complex system for developers to manage tasks?
After Microsoft took over trello, it has become more restricted these days but still good for startups.
Keep it simple! Focus on your product, not tools.
What is Confluence?
What is Restyaboard?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Confluence?
What are the cons of using Restyaboard?
What companies use Restyaboard?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Restyaboard?
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).
All ideas and knowledge that needs to be elaborated or shared is done in this wiki. With plugins for create embedded prototypes.
Also is part of the development processes to create requisites and other artefacts.
It's main use is in the development processes, it could be used to create manuals and software documentation as well, but is used more as a collaboration enterprise tool.
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.
All of our (Engineering) knowledge is in Confluence. We document our thinking, our architecture, support recipes, trip notes, anything and everything. It's very important in a remote setting, to be have this type of knowledge store.
리스트 목록: 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.
We use Confluence for specifications and knowledge sharing. We chose Confluence over other wikis primarily because of its integration with JIRA
Collaborate on project documentation, functional specs, walkthroughs, development standards, coding standards etc.