What evidence can you share that demonstrates the impact of the engagement?
Thanks to Clurgo’s involvement, we’ve been able to fulfill our commitments to our core customers. They supported us during a crucial moment when we had an urgent need to ramp up our development team. Development on a complex stack requires time, which we didn’t have, but they really did their best.
Timeliness was also dependent on the individual developer, and we worked on a time and materials contract. In a general sense, they were able to meet estimates. Some developers were better than others, and some consumed more effort than was estimated. This was also due to them working in a new environment and requiring more ramp-up time.
How did Clurgo perform from a project management standpoint?
Project management was done according to our expectations, and communication was really good. They were always sensitive to our feedback, and they applied it on several levels. They also communicated it to the developers, making sure we were all on the same page. Understanding of our constraints, they accepted that we weren’t always able to provide clear guidance.
Clurgo was embedded in our team. Whatever happened, they were receptive to our feedback, and they made sure that each of their people was effective and efficient in their position.
What did you find most impressive about them?
They were always capable of coming up with a list of candidates for the requirements we had. There was a cost to pay in terms of training and learning, but I can’t remember a case of them causing a problem that required us to step up. That was really impressive. There was maybe one case like that, but the technology was really difficult.
Are there any areas they could improve?
In the cases where we identify developers we’d like to keep with us, to continue the collaboration in the longer term, it would help us if Clurgo could manage it. Their developers sometimes have a tendency to be oriented toward short-term projects, then look for new adventures and technologies. That’s understandable when looking at it from the perspective of a younger developer, but we strive for continuity. The less rotation we have, the better.
Do you have any advice for future clients of theirs?
I couldn’t give any advice to companies looking to engage them for fixed-price projects, because we haven’t done that. For someone looking to work with Clurgo on an augmentation basis, it’s important to have proper interviews with the candidates. Clurgo can provide support based on the client’s case.
We also checked to see whether the people we were engaging were available for a duration where it would make sense commercially. If we had a smaller task that wasn’t embedded into the most complex parts of our product, and we were short on capacity, we’d undoubtedly go with the first choice. If we had a topic that required complex, long-term development, like a core component, then I’d really think twice and make sure the person we were engaging was available in the long term.