Let’s say you must attend a meeting with your partner in another country. You should calculate and prepare everything for that right? Like what is the best time to wake up, how long the time will take from your house to the airport, and when your plane landed. You have to calculate those things.
imagine that you don’t calculate it very well, you will be late and can’t attend the meeting.
It same as when you will build a website. When your tech team will work, and how long your tech team takes to lunch the website. You don’t want your website to miss the timing you already set, which will mess up your plans. We agree that time estimation is really important for everything.

Lots of companies use story points to set time estimation for each task. but what is the story point?

Atlassian said, Story points are units of measure for expressing an estimate of the overall effort required to fully implement a product backlog item or any other piece of work.

Teams assign story points relative to work complexity, the amount of work, and risk or uncertainty.
Many ways to set the story point like planning poker, T-shirt formula, and many more.
But with story points, we agree that we must have really good calculations to decide the point of each story or item and in the end. There is still a big possibility to get delayed or missing the estimation.
Instead of a story point, Blankon Technology Solutions has its own formula to set the time estimation for each story. We introduce ABO Table.

ABO Table

What is ABO Table?
ABO table is a table library that contains time estimation for each function of the feature. We already worked on lots of different functions or features. Because of that, we can create our own time estimation based on our experience. I will give you an example with our experience, the ABO table will show like this.

So the question is, how can we get the time for each function or features?


Correct, so with our experience that builds lots of websites. Those features are already covered, and we create ABO Table that we can use for the next client with the features or functions that are already covered.

The following question will come like this, how about the function that is new?


Blankon technology solutions haven’t worked on that before.
For functions that aren’t cover yet, we will tell the client that we have to research first about the function that we will work. We give win-win solutions because we can do research for a special cases like that and give the best time estimation to the client so the client can expect that the website doesn’t miss the estimation.

Add Buffer Time

Don’t forget to add buffer time in each function or item, at least 30%. So, when something unexpected happens, we still have time to work on that without ruining the timeline.
If everything is already set up, just create the story map of the product and give time estimation to all of the functions.


The Story point is good but it is still not enough for us to set the time estimation and decrease the delayed time to deliver a product. To get more popular information, check others article in here.