What evidence can you share that demonstrates the impact of the engagement?
They've met all the deadlines that they've committed to. They said that they’d complete the whole framework within 6 months, and they did. They met that deadline. It's a very complicated software; there's no other in the world like it.
Compared to the previous developers' timeline, I'm very happy. They've been very understanding. I'm probably not the easiest customer—there are always a lot of changes that I need to be made. They've always been very forthcoming, very understanding, and they never lost their patience. All in all, they're a company I recommend to my business partners, as well as my friends.
There are a lot of bugs because of my specifications that might not have been entirely clear from the beginning. As a single person coming up with those things, you don't always think of all the scenarios that might arise, so we've been sorting out bugs. But all in all, I'm happy with the turnaround time. It's been roughly a year now since I appointed them, and we are set to go live with the new system soon.
How did Omertex perform from a project management standpoint?
There are three ways that we communicate. One is Skype, where we deal with quick questions. Another is a platform called JIRA, where you can create workgroups, and everyone can edit a document within the workgroup. I use it to follow the project and to approve certain steps. For example, I'll specify a certain task on that platform, and then the project manager might ask me questions or give me an estimate for that task. I can then respond by saying, "Yes, it's accepted," or provide further clarification.
A similar platform to JIRA is called Confluence. That's where the project as a whole is specified and we manage all the individual tasks. I let the team choose what they want to use—whatever makes the most sense to them to implement our requirements.
What did you find most impressive about them?
I was impressed with the amount of communication. It might seem like too much in some instances, but I'd rather have them ask an extra question rather than assume they have to do it a certain way. Maybe it would come out wrong because my specification was ambiguous or not clear. The intense communication that comes from their side is definitely a point in their favor.
Are there any areas they could improve?
I can't think of anything that they could've done better, except one thing that comes to mind. Halfway through the project, they recommended that I make use of one of their business analysts to see how the workflow came together logically.
The business analyst is basically the translator between the customer and the developer. You've got the customer on one side that speaks one language, and then you've got the developers on the other side that speak an entirely different language. The business analyst is just there to ensure that the customer's intentions are implemented by the developers.
I'm glad they proposed this, even though it was after the project started. It's made things easier for me ever since. I wish they had raised that point from the beginning. I might have been resistant to the idea, but in the end, it was definitely a good proposal from them. It's an additional cost—you have to pay the business analysts as well—but it's definitely worth it.