What is Aha!?
What is Confluence?
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 Aha!?
What are the cons of using Confluence?
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
As a small startup we are very conscious about picking up the tools we use to run the project. After suffering with a mess of using at the same time Trello , Slack , Telegram and what not, we arrived at a small set of tools that cover all our current needs. For product management, file sharing, team communication etc we chose Basecamp and couldn't be more happy about it. For Customer Support and Sales Intercom works amazingly well. We are using MailChimp for email marketing since over 4 years and it still covers all our needs. Then on payment side combination of Stripe and Octobat helps us to process all the payments and generate compliant invoices. On techie side we use Rollbar and GitLab (for both code and CI). For corporate email we picked G Suite. That all costs us in total around 300$ a month, which is quite okay.
There are lots of project management tools available nowadays. The choice ended up between Trello and Basecamp. Asana , JIRA and monday.com got a fair review but they didn't make it to the final list for several reasons (either way to complex or some UX issues or just too many options - good in some cases but not a good fit in this case).
Between Basecamp and Trello the battle was between ease of use and price. Basecamp packs a great set of features and if you are ready to move to an all in one solution: chat, file storage, and a PM tool, then @basecanp is by far the right choice. But since all the features are within one package that cannot be customized, moving to Basecamp but only using a part of the tool feels.. well.. not right. On the other hand Trello has the #kanban format that is just too easy to use and the price point for small and midsize team that no one can beat.
At the end, all solutions have a good fit in some cases. A better fit. But I think Trello can do the job in any case - it can fit with any scenario.
We use Nextcloud for company-file-management, personal work-documents and for collaborative work (through collabora), organize our #TODOs, that are not covered by the Bugtracker. Existing solutions either were very expensive ( Google Drive ), missed a lot of features ( Trello ) or were pretty much overloaded with features ( Wekan within Sandstorm ).
That made Nextcloud ud our natural fit for our company management and we're convinced of its integrations and flexibility.
We were using a hosted version of Redmine to track defects and user stories originally. We migrated to Jira.
Jira was an easy decision for a number of reasons:
- It's much more "Scrum ready" straight out of the box
- It's so much easier to keep a track of progress (I love the reporting)
- It natively encourages you to adhere to Scrum/Agile/Kanban practices
- Atlassian has a fantastic DevOps ecosystem when considering the likes of Confluence and Bamboo etc
- So many integrations!
- Its UI is so intuitive which makes it an absolute pleasure to use!
I know there are alot of other tools in this space but not even considering anything else at the moment. Love Jira!
I use Trello, the macOS app for my personal projects and Google Chrome for work. At work, I have 7-8 active boards for various projects.
At first, I wasn't sure about Trello. The last company I worked at used Asana and I was really used to that. Before then I was using Jira. Now I ❤️Trello. It is amazing. Power-Ups™️ are so awesome!
For personal projects, I have used it for planning a move across town. I'm also using it for my Wedding. I got my fiancè almost loving it too.
We've been really happy with Clubhouse for project organization / task management / kanban board while developing FeaturePeek. The featureset is rich and the UI uncluttered. Clubhouse is different in that it makes some assumptions on how things should be (workflow state, the relationships between stories/epics/milestones, etc). having it be opinionated from the start helps you hit the ground running, while still being editable / extensible for tweaking things to your liking.
The pricing is spot-on too – a flat $10/month for teams of 10 or less. This really made it attractive to us to try out.
If you think Trello is too basic / lightweight but Jira is too full-featured / heavy, you should give Clubhouse a shot – I think you'll be pleasantly surprised.
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.
PrometheanTV utilizes Confluence to interface with and manage external consulting projects.