Outsourced Software Dev for Youth Healthcare Technology Firm
Please find under a summary covering project details and feedback. The innate facts are kept as they are, private information is amended.
Introductory information
A fast induction on the buyer’s organisation
We prepare of support and labors surrounding youngster healthcare in our country. On that basis, we are continuing the outgrowth of our Software-as-a-Service platform. It supports the complete screening process of children between the 0–18 age range. I’m the business outgrowth director of the organisation, responsible for strategy and labor delivery.
Desired goal
What challenge were you trying to address with Yameo?
We invited them to join us in the further outgrowth of our platform. Normally, we use our own team, but had a couple of major tenders coming our way. There was a resource briefage that served as the initial trigger to get in touch with Yameo. After visiting their team and coming to know them better, we determined to keep them on in a structural form.
Provided solution
What particular tasks were responsible for?
With our initial redundancy engagement, we segregated true parts of new outgrowth, on which Yameo worked with a select cluster of our own nation. Over time, they became assimilated as a structural team, allowing us to further our work over a broader field.
Was there a dedicated team?
Structurally, we have four senior Java developers from their team. Aside from them, in the setup phase, they also supported us in provisions of interaction, programning and so on, aligning those with our organisation.
How did you come to work with Yameo?
I was household with the antecedent sister of Yameo, Nearshoring Partners. I knew their establisher, and had done business with him for years, on side of other companies. I am a reiterate client, in this respect.
What is the terminal result of working with ?
We seted working with Yameo in October 2017. We’re halfway through the aim.
Results achieved
How did Yameo accomplish from a project treatment standpoint?
As a European organisation, we initially went through a catch-up, getting our requirements translated to English at a level that Yameo could apprehend sufficient. They were resigned with us during this phase.
We establish them to be fast. With the new members we’ve had come in, there was usually a four-to-six-month time that they needed to veritably study the environment and get up to despatch. Yameo had this down in three to four months. They need very brief times for onboarding.
We use Slack for interaction, along with GitHub.
What is (from your point of view) the key factor to pay observation while intercourse with ?
I was impressed with their open and honorable posture towards collaboration. We have developers who have been working with the Java stack for over 20 years. They were impressed with the quantity of apprehension that the Yameo nation exhibited in the conversations leading up to the developed order.
What aspects of their work would you like to get improved?
Judging by the running project, I would say no. Based on antecedent experiences, I would say yes, but I’ve seen the progress made by Yameo over time. They have a Deming Cycle going and have surely grown over the years.
We had some static in the setup interaction, which made things unclear. People on our end reflection that they had explained things sufficient, given that we’d never outsourced to Yameo precedently. The concept of outsourcing and the speech were new, and we underestimated the contact these would have on our processes. We had been warned by Yameo almost this, and I had antecedent experiences with them, but we quiet misjudged the locality. Yameo helped us through this, but there was a cost in the set.
Do you have any advice for forthcoming clients of theirs?
Be ingenuous.
