First and foremost —
Obselite was built for fun.
It is a learning experience for the software engineers who contribute and support development. It's not meant to replace any of your existing tools. (yet)
Motivation for Obselite stemmed from a frustration of opinionated use of unopinionated tools.
The priorities of Obselite are:
Obselite was designed to be:
Obselite is influenced by industry experts with more than 25 years of knowledge and experience building impressive software. More than other glorified to-do lists, Obselite learns how you work, what you're building and how it's being built.
This is how it is structured:
We call tickets "sprinkles" because they are short and sweet. They help you achieve your sprint goals but you can rename them, of course.
How does it work?
Well, the same way you do.
Obselite assesses the state of your product and team to prioritize the most valuable and important work, according to the available resources and organizational goals.
Sprints, or cycles, can automatically be planned and managed based on your desired length and resource allocation.
You can customize the matrix from one to an infinite number of dimensions or manually override according to specific conditions such as features, labels, statuses, etc.
For example, a feature that is revenue-impacting such as checkout has a higher probability of being worked on sooner.
By default, your organization will use a branch of our shared trained model. We will offer private models in the near future.
All features are free to use. Some features are in development or incomplete. No service guarantees. Terms are subject to change.
Thank you for your interest in Obselite! We look forward to working together!