Wow.. it's so good and simple. It's exactly what I searching for alternative of jira with low cost. Why is it free ? What is the price plan for the future ? After knowing that, I will move all my projects to there.
Do you support Github issues? If so, that awesome. If not, it might be worth an assessment since platforms like GitHub and GitLab have lightweight project management tools used by many. The problem is, they are lightweight. This makes it so teams have to decide where to manage their project issues, etc. It would be helpful if Tara supports the creation and management of GitHub/GitLab issues, labels etc all in Tara.
@emmanuelbuah Yup! We support github issues (and gitlab is coming very soon). Take a look here: https://tara.ai/how-it-works/
Once you've authorized your github profile - Tara can import any active issues as tasks.
Tara is the like the wonderful baby that Trello and JIRA had when they finally realized neither of them worked well for startup engineering teams. We've been having a great time using Tara to keep our sprints on track. I can see our teams have little friendly competitions to complete their sprint tasks on time and get better at estimating effort for each task. This is the fist time we're seeing this happen on a consistent basis and that's been the most rewarding part of using Tara. Highly recommend!
We've been running R&D sprints on Tara for some time now and couldn't be happier! After jumping from JIRA to Trello to just a Notion Kanban board, Tara was finally the solution that is really sticking with us and structuring the work we do.
Our product and growth teams are now itching to jump on too! Great stuff!
Hey PH Community 👋
Kat- thanks for the hunt! We're psyched to be sharing Tara AI - in its open beta.
My co-founder Syed and I started noodling on productivity tools a few years ago. After interviewing 250+ engineers and founders, we discovered that most project management software a) takes a lot of time to configure b) is not built for cross-functional teams and c) takes away focus from the release cycle. The status quo is that engineers spend precious time wading through tickets, and EMs + PMs continue to lack visibility at the release level. This only gets worse with distributed teams across different time zones, and as teams outside of engineering rely on product to meet customer milestones and release dates.
We've been lucky to meet others that share these frustrations and assemble a founding team passionate about the problem. As a team, we've been dedicated to designing a modern and simple interface, that just works.
Tara is free for teams of all sizes - for unlimited users 🚀
In our open beta, teams can:
-> Create requirements and tasks (in one scroll)
-> View daily priority tasks and Github PRs in home
-> Start sprints in seconds (weekly or bi-weekly) with ongoing team insights
-> Plan manageable sprints based on recent effort with a smart indicator
What's slated next:
-> Multiple teams (growth, etc) can run sprints and view insights
-> Task lifecycle (i.e. when is a task truly done?) and automated statuses
-> More smart indicators, with improved effort estimation
Thanks for reading. Would love to hear your thoughts and suggestions!
Gratefully,
Iba | Co-founder & CEO
@mike_seekwell Hey Mike- just quoting my co-founder's response from below thread:
"Principally, we believe teams shouldn’t have to be limited by user counts when deciding which project management system to use. Most are still clunky and cap at 10 users for free accounts- we’re planning to have a free forever plan for unlimited users (much like Gitlab).
Paid plans may include functionality for enterprise teams, full fledged integrations and/or smart features such as automated sprint management."
TLDR: the free forever plan will always be for unlimited users - no user caps. We've mindfully built the infrastructure and raised funding to support this.
@mike_seekwell@ibamasood By far this is one of the most usable product I have found and that too for free. May be this is disruption small teams needed to become better at building software. Thanks a lot for doing amazing work.
My suggestion : A comment thread on task is really helpful, I use that very often with my team and I am sure you might find strong use case for this also. Please have a look and see if this make sense for you guys.
@mike_seekwell@designerbaniya Thank you! We've been thinking through designs for task activity stream, history and commenting. The key is to design them in such a way that they don't bloat the task modal. Will keep you in the loop once we introduce these features.
I've been watching this team and product go from strength to strength while in private beta and I'm excited to see it finally out in the wild.
The delightful workflow is already there, and while this is phase one of smart functionality, there's so much more yet to come.
@ibamasood@syedahmadz are amazing to work with and incredibly responsive to new feature and integration requests, too!
@dmitry_gorshkov Great question! The unit of "days" is actually an experiment we're running. The only place where "days' shows up is the task detail modal. We tried it out to see if we can help more novice software teams to get started with the process of effort estimation and with sprint planning more easily. Everywhere else, we've kept it unitless like all other agile tools. I've heard feedback where for some teams it was helpful to frame estimation that way. That said, I've also heard a lot of feedback around leaving it as unitless and letting the teams decide how to come up with effort scores is more familiar. Certainly this is an area we'll iterate on.
Simple enough, easy for developers. But this is not Jira alternative. It's like Trello or Asana. This can be a solution for companies with <50 employees.
This is a Jira killer. Everyone talks about agile, but the nitty gritty of actually doing it is time intensive upfront, gets complicated to coordinate and tough to maintain at speed.
Many of the legacy tools out there are bloatware, require cobbling together with other solutions or have gaps in the flow. Tara is setting the bar higher, removing friction and getting distractions out of the way so you can build faster and with less pain.
This is aimed at startups, but any organization with engineering teams needs to get more efficient at this. This is the product mgmt tool we’ve been waiting for!
Great product, for effort estimation do you use natural language processing to find and analyse similar previously completed tasks.
Do you have a mechanism to automatically migrate tasks from existing project management tools, like Jira, Monday.com, etc. I believe this will speed up adoption (with enterprise especially)
@rilwan_owolabi1 So as part of this release- no NLP yet! The plan is to assess and really understand the issues teams and individuals face with effort estimation, and how they can be alleviated with some form of "suggestions" around effort based on past performance. We're doing this on a lighter level with the sprint load indicator and plan on doing the same across other parts of the PDLC. I think the key is not to get tied down with having smart features for the sake of being "smart"- we're trying to be thoughtful around how to do suggestions and predictions that actually provide value to teams. We learned that the hard way with an earlier version that was ML-based predictions only (spoiler: it didn't do well).
And yes! Can't agree more on the automatic migration. It's on the way! We're thinking through the data models and labelling scenarios around this- the last thing we want to do is have teams manually have to label and structure their data set from Jira. Using it is painful enough.
Getting more utility from products plans means more time to invest in better products. Investor in Tara and excited to see the progress of the product! Nice work!