Could you share any statistics or metrics from this engagement?
The feedback from our own engineers was that Espeo Software's team was very flexible in adapting to existing software development methodologies. This was important for the team they were working with. Espeo Software also had great technical expertise, which allowed them to become involved quickly without too much overhead. They were committed to what they promised and delivered on that.
I was not involved with the work on a low level, but I'm sure that any challenges they came across were solved in a collaborative way. Espeo Software was part of a 20-person team, so there was a lot of collaboration between them and the rest of our resources.
How did Espeo Software perform from a project management standpoint?
We have an on-site engineering manager in Poland. We also have a project manager in charge of the work in terms of releases and scope. We also have a US-based product manager who is in charge of translating business requirements into technical stories which are added to our JIRA backlog. Based on the feedback they received, Espeo Software integrated well into our process.
We started the engagement completely on-site, with Espeo Software's engineers working with ours from Monday to Friday. After a two-month period, we started letting them work off-site for two days a week. In the end, Espeo Software's team only came to our office for review meetings, planning, and retrospectives for one day a week. The communication was constant, regardless of Espeo Software's location.
What distinguishes Espeo Software from other providers?
The good technical expertise on Espeo Software's team is the first thing I'd highlight. They adapted to our business and development models quickly. "Local" is also a keyword.
Is there anything Espeo Software could have improved or done differently?
There's always room for improvement. Espeo Software could have more diversity in terms of projects, but this will come as they grow their team.