What is Trello?
Who uses Trello?
Why developers like Trello?
Here are some stack decisions, common use cases and reviews by members of with Trello in their tech stack.
Although Trello has some good and easy to use triggers to push updates from Trello in different environments we use, using Zapier has made our life much easier. Creating a zap is easy and a full management of those zaps are in a full overview to review and manage.
With GitHub in the same combo with Zapier and Trello it's very easy to track issues and bugs and make them available to the responsible project manager or team directly.
One of my favorite project management tools Trello
Feedbacks from Retrospective Meetings are save here. For list called Backlog, each card will generate a new issues (by IFTTT recipe) Trello
I use it to keep track of my todo list Trello
Here are some stack decisions, common use cases and reviews by companies and developers who chose Trello in their tech stack.
So I am a huge fan of JIRA like #massive I used it for many many years, and really loved it, used it personally and at work. I would suggest every new workplace that I worked at to switch to JIRA instead of what I was using.
When I started at #StackShare we were using a Trello #Kanban board and I was so shocked at how easy the workflow was to follow, create new tasks and get tasks QA'd and deployed. What was so great about this was it didn't come with all the complexity of JIRA. Like setting up a project, user rules etc. You are able to hit the ground running with Trello and get tasks started right away without being overwhelmed with the complexity of options in JIRA
With a few TrelloPowerUps we were easily able to add GitHub integration and storyPoints to our cards and thats all we needed to get a really nice agile workflow going.
I'm not saying that JIRA is not useful, I can see larger companies being able to use the JIRA features and have the time to go through all the complex setup to get a really good workflow going. But for smaller #Startups that want to hit the ground running Trello for me is the way to go.
In saying that what I would love Trello to implement is to allow me to create custom fields. Right now we just have a
Description field. So I am adding
User Stories &
How To Test in the Markdown of the
Description if I could have these as custom fields then my #Agile workflow would be complete.
For Etom, a side project. We wanted to test an idea for a future and bigger project.
What Etom does is searching places. Right now, it leverages the Google Maps API. For that, we found a React component that makes this integration easy because using Google Maps API is not possible via normal API requests.
You kind of need a map to work as a proxy between the software and Google Maps API.
We hate configuration(coming from Rails world) so also decided to use Create React App because setting up a React app, with all the toys, it's a hard job.
Thanks to all the people behind Create React App it's easier to start any React application.
We also chose a module called Reactstrap which is Bootstrap UI in React components.
An important thing in this side project(and in the bigger project plan) is to measure visitor through out the app. For that we researched and found that Keen was a good choice(very good free tier limits) and also it is very simple to setup and real simple to send data to
Slack and Trello are our defaults tools to comunicate ideas and discuss topics, so, no brainer using them as well for this project.
I use GitHub because it can handle all the project management (it's got a great built-in kanban for projects that integrate beautifully with Issues. Also line-comments on commits are super useful to us. The integrated environment is perfect, light-weight, and it's nice NOT to have to deal w/ project management with a tool like Trello outside of the codebase. It's good to have everything in one place.
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.
When starting a new company and building a new product w/ limited engineering we chose to optimize for expertise and rapid development, landing on Rails API, w/ AngularJS on the front.
The reality is that we're building a CRUD app, so we considered going w/ vanilla Rails MVC to optimize velocity early on (it may not be sexy, but it gets the job done). Instead, we opted to split the codebase to allow for a richer front-end experience, focus on skill specificity when hiring, and give us the flexibility to be consumed by multiple clients in the future.
We also considered .NET core or Node.js for the API layer, and React on the front-end, but our experiences dealing with mature Node APIs and the rapid-fire changes that comes with state management in React-land put us off, given our level of experience with those tools.
We're using GitHub and Trello to track issues and projects, and a plethora of other tools to help the operational team, like Zapier, MailChimp, Google Drive with some basic Vue.js & HTML5 apps for smaller internal-facing web projects.
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.
- 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.
- Customize labels for your cards, and use filters to only show what you want. You can also filter by keywords and by person (if you’re on a team).
- Attach a date and it will appear on the front of the card. When that date is approaching, it will turn yellow as a gentle reminder.
- Trello keeps a record of everything that’s happened on the card: comments, changes, additions. You’ll never wonder “How did that happen?” again.