Could you share any evidence that would demonstrate the productivity, quality of work, or the impact of the engagement?
We have just launched the new feature set, so there is no customer data for its adoption. From a competitive standpoint, it has allowed users to visualize their swing without shooting video or having a reference point. This is quite important, since, looking at all analyzers in this space, our feature is something which every customer wants to have.
How did Zco perform from a project management standpoint?
I would give them a 7/10 in this area. The team was communicative, they were upfront about challenges, escalations, and obtaining detailed requirements. I would like to see Zco do more long-term project planning. We were given milestone dates, but we didn’t know when the project itself would end, until we got closer to the finish.
The development team is in India, but we did have overlap times early in the morning and late at night. Interfacing more frequently would be good. The project manager was based in New Hampshire, which made it easy to get in touch, but we also needed to talk directly with technical leads, who were based in India. We had to wait for a day or at least a couple of hours for this purpose.
We used Basecamp for communication, which was Zco’s tool of choice. We entered commentary, screenshots, and builds into it. Towards the end of the project, when our own QA team became involved, we reported bugs in our JIRA project, and invited Zco to it. They used that as a reference.
What did you find most impressive about Zco?
Skillset-wise, Unity development isn’t exactly known or adopted by most developers, which gives Zco a unique advantage. Their rates were good, based on the bids we looked at and compared to hiring a full-time resource or a U.S. contractor for the same type of development. The quality was very good for the price, so it worked out from a business perspective.
Are there any areas Zco could improve?
Towards the end, when we were doing bug fixes, having Zco be more involved when sending builds would have been good. They were integrating their code into our own, so sometimes things would break. Although they weren’t as familiar with it as us, taking more time to understand what broke and fixing it on their end, versus sending it over to us and having our team fix it, would have saved us a bit of time, and would have sped things up a bit.