How ScootAPI collaborates on roadmaps and sprints in Fibery

Product company 🚀

11-50 ppl 🎩

Transportation Software 👻

Switched from Airtable 😎

Templates used in this customer story

Software Development Product Management Meetings

ScootAPI helps local Entrepreneurs to launch E-scooter sharing businesses. 🛴

Our product is a software fleet management system for Sharing Businesses like Lime, Bird, TIER, VOI. White Label App + Admin Panel + Supply of e-vehicles.

What do you use Fibery for?

We use Fibery to manage the Software Development process of our product, as well as for time tracking, meetings, OKRs, Hiring, Customer Support, and Finance.

Here is how our workspace setup looks like. 👇

Why did you switch to Fibery and what tools did it replace?

We used Airtable for almost 1.5 years to manage our Software Development process.

Currently we use Fibery to manage almost all our processes, including Software Development, Product Management, Hiring, OKR, Customer support, and many more.

Our documents are stored in Google Docs. We started to migrate them to Fibery but it takes some time. Since we are more focused on the development now, the wiki is not so complete, but we will get to it soon.

Now spill the tea: How does your Product Management process look like?

How do you scope & plan development?

We started from smaller chunks using 2 weeks Sprints and now moved to Kanban. For high-level product planning, we use Quarter Roadmaps.

Roadmaps help us see the product goals and be flexible on a short distance. Kanban and Quarter Roadmap help us deliver fast and get early feedback from our customers.

Here is how the Quarter Roadmaps overview looks like. 👇 Each roadmap has state, start and end dates, and linked Sprints.

We can also drill down to the specific features planned for this quarter and check what tasks still need to be completed and what their priority is.

How do you track and analyze progress?

We use boards to track all our activities. We haven’t come to charts at the moment but we have plans to do it as soon as the development time becomes more predictable.

Here is how the Current Sprint board looks like. It shows all the Tasks and Bugs by state, as well as their importance from Low to Critical 🔥.

Each person can also check only tickets assigned to them.

We also track our development time in Fibery. Here is how the Time Log Report looks like 👇

How do you store and organize your support tickets?

We have a separate Customer Support space for that. Support tickets are connected to development tickets, features, and our partner accounts.

Here is a simple Kanban board with all the tickets by state 👇

As we have several partner accounts that we need to support, we also have a board that shows tickets by account and state.

Do you store your meeting notes in Fibery?

Yes, in our team we have weekly sync calls, and we store meeting notes in Fibery in a separate Meetings space.

It's convenient that we can link parts of meeting notes to actual features and tasks that we discussed.

We are also planning to run Retrospectives soon, and store them in Fibery as well.

Praise time: What is your favorite Fibery feature and why?

Flexible domain helps us to manage all parts of the business. We can cover almost every process in the company: OKRs, Product Management, Software Development, Customer Support, HR, Finance.
Reports is a significant feature — it really helps us to see what happens in different processes. We use it in Software Development and Finance, and also for time tracking.
We automate some parts of the process in the financial area and in Software Development. Automation Rules allow us to save time on routine tasks.
We use Fibery API to build the Customer Support Feature in our admin panel. Customer support tickets are displayed in our admin panel and our clients can keep track of the progress while the ScootAPI team manages it through the Fibery interface. We use Fibery as a backend!
Smart folders are great! They do help us to organize the data in a structured way automagically.
Permissions management came to a new level with Fibery! We can limit the access only to what each user should see and manage. It’s very flexible in terms of customizing user groups.

Criticism time: What you don't like/lack in Fibery?

Dashboards are a must-have for us. Currently, there is no entry point for the whole picture and we need to switch between different views. A dashboard will help to put different widgets like charts, filtered lists of tickets, or anything else in one place. It will save time and will allow us to see the whole product status.
Integration with Google Calendar and ability to create events from Fibery. We have many calls and it would be great to keep them in sync with the calendar in Fibery. This integration will help us to link data to concrete meetings. It is not a must-have tho — it is nice to have :)

Share 3 Software Development practices that you’re following

Being a remote startup, we are sticking to the Kanban process and trying to perform as fast as we can.

Here are the best development practices that we are following:

Three-month roadmaps allow us to set achievable yet ambitious goals — that’s enough time to build something great. We will experiment with that and maybe will switch to a shorter time period for our roadmaps.
Fail fast. We deliver as fast as we can and try to get feedback as early as possible. We release features to a small number of clients to verify and test them. After that, we do adjustments and move them to GA.
Everyone in the team is responsible for taking the lead on a feature and moving it to a release stage. We do rely on our engineers' experience and ambitions to make a delivery from idea to production.
Code reviews and sync-ups are a must. Sometimes you want to save your time but investment in your process is a strategic decision that makes the overall product quality much better and your team more organized.