What evidence can you share that demonstrates the impact of the engagement?
The end-client was extremely satisfied with the use cases set up by Akira, so it was definitely a success. On the proof-of-concept side, the customer really liked the implementation.
Before we engaged them, we weren’t sure if this would mean something that could work in a customer environment. But, in collaboration with Akira, we demonstrated that this was something that was possible, and received more business with the customer as a result of this project.
How did Akira Analytics perform from a project management standpoint?
Even though we didn’t have a dedicated project manager, we used Jira. The team was self-managing and were diligent in ensuring that Jira statuses stayed up to date, documenting their activities on the platform. This helped immensely on the project management side.
We had daily phone calls with them, where we reviewed what they’d done the previous day, and the action plan. We discussed any impediments that might have appeared and how to resolve them.
I felt that the communication was good, even though there were some challenges that came up—some technical, and some access-related. We were able to resolve them in a timely fashion.
What did you find most impressive about them?
They have in-depth knowledge when it comes to DevOps, big data, and technical things. It’s not just one tool; they have knowledge of the entire ecosystem—different DevOps tools and big data ecosystems. This is where they distinguished themselves from other competitors. There are a lot of people out there, and a lot of buzzwords like “DevOps” and “big data”. We don’t often come across teams that know a whole lot about these things.
Are there any areas they could improve?
During the project, I felt they had a small team. I don’t know what the scene is now but having more people would’ve helped. At times, it felt that some of them were putting too much effort in; having more people might have alleviated that pressure.
Do you have any advice for future clients of theirs?
Clients should discuss their approach upfront and agree on what they’re attempting to do. Before implementation, they should do some requirements gathering, and make sure both parties are on the same page.
I felt they were fairly technical people, and technical people tend to come up with solutions, which a business might not want sometimes. It’s better to collaborate, come up with a proper scope, and agree on the approach beforehand.