I see marketing-speak for how this is so much easier than other tools like JIRA (which we use.) However, I'm not finding details about how this is accomplished.
What are the key differentiators in how this is easier specific to those that use JIRA?
What are the key differentiators in how this is easier specific to those that use JIRA?
In a Jira workflow, there's a lot of customization required and a lot of thought needed to go into how to set up your workflow. Leantime is intended to be "opinionated" in the way that it's already set up -- each work function already has a home. The thing you have to decide is how you want to see the tasks.
Our "home" screen is intended for individual users to have pre-defined organization and not needing to set up their own dashboards either.
The other approach we do differently is to work to engage ICs in the value of the work and we do that by making the goals and work more clear. Some of this is still being developed out and rounded out better by our AI features -- which can be better read about here and how we view it in relationship to our own ADHD and the features behind it... https://leantime.io/2023/07/30/the-top-digital-planner-for-a....
Lastly, for Confluence fans, we come default with docs and (on cloud) we have whiteboards. Some of which will be coming out in plugins to OSS here soon.
I'm not sure what this means entirely, but across our projects we have some with different workflows than the others. These are necessary in that we have certain workflows that must meet compliance requirements, and those workflows are the best way to ensure we execute those. In other projects, they are less onerous and apply to different kinds of work (so, different workflows.)
> Our "home" screen is intended for individual users to have pre-defined organization and not needing to set up their own dashboards
This is good, but we generally keep our exec leadership out of JIRA (they don't really have the context for the details.) Our users can design their own dashboards, but that's a personal preference. We use the standard views.
> making the goals and work more clear
I would prefer to see more fall-into-the-pit-of-success for the equivalent of JIRA stories to be more oriented toward the outcome or feature or capability, as opposed to the accounting/I-got-receipts feeling I get from JIRA. While story points are fine, I prefer a focus on clarity and a better measurement for effort than the subjectivity of a team's interpretation of the fibonacci sequence.
> for Confluence fans, we come default with docs and (on cloud) we have whiteboards
So, Leantime includes a markup engine as well as a whiteboard feature? If I already have a deep investment in other tools that do those things, how do they integrate?
Something that all pm tools have in common these days is that they are glorified task lists with different visualization options. This is not project management. In Leantime you track and work towards goals/outcomes, you see your metrics change and know what impact your work has. Additionally we added a variety of research/strategy focused boards such as Lean Canvas, Business Model Canvas, SWOT etc to allow you to define products and features deliberately and in a central location. This helps to align your entire team.
The docs (while admittedly not as powerful as confluence) keep your documentation where it needs to be (with the project) rather than having to switch between sites.