How to make sure the times are as initially anticipated?

Long story short. Our credo is to provide the clients with predictable service in a manner they have never experienced before.

While doing dozens of projects we've discovered that business actually evaluates predictability over other parameters of development process including speed. As a team with a high level of engineering maturity culture we've adopted some best practices to show outstanding transparency, consistency and predictability of our work. Spoiler: we succeeded with it and our way of work usually causes wow effect. Let us introduce some basic tools we use in our day-to-day work.

  1. Reliable Scrum for fixed scope projects. It's very simple and lightweight addon that turns the weakness of unpredictability of Scrum into a strength of knowledge of the chance to hit the deadline and the project health. It requires almost 0 efforts to set up and maintain and provides extremely valuable insights and data to manage project. Actually you don't need estimates to start using this spreadsheet. See attached 1 and 2. It's amazing tool and we encourage you to use it even if you have someone else to work with on your project. And please don't just trust our words but test them instead. We are available for a quick call to show you how this tool works.

  2. Delivery time forecasting to answer the question "when this feature will be ready?". It is a common need for business to know the date when some work item is going to be finished (marketing campaigns, external commitments, etc). However traditional estimation tends to be not robust and accurate enough in a bad way, so we are using historical data forecasting instead. See attachment 3. Can you imagine the service that hits the deadline for 9 out of 10 tasks without heaving huge buffers to mitigate risks? Here it is. And again, with no time spent on estimation.

As you can see we are trying to avoid estimations where possible, as this is not a trivial skill. Even a top developer can be not so good in estimations. Personally our project managers like estimations and spent a lot of time to become good at doing it. Also we teach and coach developers how to provide accurate estimates. And because we are good with it we recommend everyone to stay out of this and use historical data forecasting instead. If you are interested in robust estimates we suggest reading a book of Steve MacConnell "Software Estimation: Demystifying the Black Art (Developer Best Practices)". With this knowledge you will be able to validate incoming proposals/estimations and recognize unrealistic ones.

And of course we do care about the development speed. Moreover, as we don’t really concerned about fitting estimations we are focused on getting the work done ASAP instead. And usually Kanban is a basement for effective development process. The idea behind this method is to establish the flow to ensure that a single work item can be delivered as fast as possible. Then just put suitable portion of features into the system and track the progress.

And we are damn good at implementing Kanban.

As a conclusion we would like to say that comfort and safety of our clients is our priority. So we do business under the banner of sincerity to ensure outstanding transparency of our work and the progress of the project.

Our project managers used to run the projects with a budget more than $1M per year for companies like eBay, Amazon and other industry leaders. We really believe that we have skills to help you with your project.