Roadmap prioritization

Boosted backlog is fed with three sources:

1. Orange's Web UI Kit, basically Orange's design system applied to the web, in its current state;
2. Bootstrap itself: maintenance, evolution, upgrades, etc.
3. Our own repository: issues, maintenance and evolution of our custom components or contents.

We cannot really anticipate what's being done in Bootstrap, preventing us to define sprints. However we're able to:

• estimate tasks coming from UI Kit and issues, using effort:n labels — as a sidenote and after a few delivered features, n value is pretty much the same in days;
• prioritize them based on a simple algorithm.

Prioritization rules

1. Existing components:
   • already in v4, required for some projects to upgrade to v5;
   • needs update next to a UI Kit change.
2. "Popular" components:
   • asked on GitHub,
   • searched on the website (through Algolia),
   • for which a technical solution is already suggested, based on a project's implementation (implying it's already in use somewhere).
3. New components, requiring both research —regarding accessibility and performances mostly— and documentation alongside development.
4. Already feasible components, using Boosted utilities, helpers or components. Those might end up as example templates, alongside their documentation in "Design Guidelines" (and one day, Storybook).

That's simple enough to work like a charm!