What evidence can you share that demonstrates the impact of the engagement?
There are two major impacts of the engagement. First, we really love the scrum philosophy they utilized. Bright IT did a great job of implementing this methodology. Second, the stability and performance of the ticket platform is much more reliable and has a higher performance level.
Both the features on the backend and the usability on the frontend were built according to our requirements. It’s easy to build anything the way they’d want it. However, it’s important to understand the market that the solution will is being produced for.
An e-commerce marketplace for airline companies works differently than a ticket platform. Bright IT really took the time to understand the requirements of our market and target group. They did a great job of creating a custom design and UI, instead of just using a template.
How did Bright IT perform from a project management standpoint?
We had an organizational structure in place where communication occurred on the C-level, meaning our CMO with their acting CTO. There was also a scrum master who guided the project management. Our teams used modern communication tools like Slack. The flow of communication was pretty good.
Bright IT is a very service-oriented company. They try to please everyone as much as they can. But sometimes, someone has to communicate when something isn’t working. In my opinion, they were too service-oriented and friendly at times.
What did you find most impressive about them?
Bright IT had genuine commitment throughout this engagement. I could tell they weren’t just mercenaries who’d do whatever it took to complete a job because it was well-paid. Rather, they had a true dedication to our cause and implemented this extra step beyond a transactional partnership.
I could really sense that they had a sincere interest in our platform's success. They didn't cash out and jump ship because they didn’t care if the platform was worked or not. This attribute really makes them stand out.
Are there any areas they could improve?
No, there are no necessary areas for improvement. However, I would’ve liked if they’d stood up and clearly communicated their opinion at times. Of course, this possesses the risk of their team overdoing tasks by requesting to have a say in matters. And maybe the communication regarding the handover could have been better - on both sides. Other than that, I’m really happy with how they did.
Do you have any advice for potential customers?
I’d advise them to take the time to understand their objectives. Jumping right into a project and then later figuring it out is ineffective. Their briefing with Bright IT should be short and goal-oriented. However, if essential information is missing, that'll cause misunderstandings down the road. The clearer they are and more time they take to really explain everything from the scope to the model to revenue expectations, the more helpful Bright IT will be.
I’d also advise a potential customer to provide one person as their company’s sole communicator. This person should handle the correspondence between the Bright IT’s scrum aster and the company. The more people you have talking with each other, the more misunderstandings will be avoided.
I’d really empower this liaison to be the decision-maker for quick decisions. If there are severe, far-reaching decisions, this person should check and then close the loop with Bright IT. There’s nothing worse than postponing decisions.