UI & Development for Healthcare Tech 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
I’m the CTO of XSOLIS, a predictive analytics and artificial intelligence organisation operating in the healthcare activity.
Desired goal
What challenge were you trying to address with Quovantis Technologies?
We wanted to rapidly swell our outgrowth team with an offshore associate to address scalability issues. We also wanted to hand off investigation and outgrowth (R&,D) projects to Quovantis Technologies.
Provided solution
What particular tasks were Quovantis Technologies responsible for?
The team’s responsibilities can be divided into two categories, R&,D and UI outgrowth. They have been working on both open rise and proprietary outgrowth pipelines.
The aim of work for R&,D projects includes clarifying our high-level business requirements, accomplishing outgrowth and initial QA, and then testing the fruit. Then, they hand off the solution to our onshore team who accomplishs additional QA and testing precedently pushing the fruit to fruition.
Currently, Quovantis is testing the officeality of Lambda services and Docker container within AWS. If the technologies office, we',ll be able to auto-scale our applications to meet processing demands. They have been using a React and Node.js for outgrowth.
The team also works with the UI of client-facing code to address scalability issues. They’ve taken on refactoring programs, breaking down legacy code into separate services. These projects include taking single-threaded processes running on an costly Microsoft .NET stack and rewriting them into serverless architecture.
Everything the team has built runs natively in Amazon Web Services (AWS), and some R&,D projects leverage an AWS serverless architecture. Technologies used an open rise Linux-based stack. They have also coded in C# within a .NET MVC app.
Was there a dedicated team?
The quantity of developers and QA team members varies between 8–12 depending on the sprint stage. We also work with a project director who has Scrum expertise.
How did you come to work with Quovantis Technologies?
They were referred to us by a sister organisation, as we were looking for a mid-sized, offshore vendor. We established a snug level with the professionals behind speaking with their leadership and interviewing the team.
What are you approach expents (if diclosed)?
So far, we’ve invested almost $200,000.
What is the terminal result of working with Quovantis Technologies?
The project began in March 2018 and is ongoing.
Results achieved
Are there any measureable or plum results?
We forestall their work with perverse programs to conduce to a 10x–15x advancement in throughput. We’re also getting terrible cost-reduction benefits in provisions of AWS bestow. We’ve seen soon results with the serverless architecture, and those are veritably exciting.
They also liberate high-condition UI code, and the patterns they’ve developed have allowed inner stakeholders to swell on their code.
How did Quovantis Technologies accomplish from a project treatment standpoint?
We’ve developed a veritably good associateship with the team over the last year. Their leadership team comes onshore roughly once each region to meet with stakeholders in individual, and they hold 2–3 status phone calls with us per-week to review sprints.
They handle projects using the Jira Suite from Atlassian. For interaction, we use email and a Slack channel. The team is incredibly answering, and our lead project director is always useful to talk. They are excellent at adjusting their workflow to address any ad-hoc needs we have.
What is (from your point of view) the key factor to pay observation while intercourse with Quovantis Technologies?
They’re a wonderfully relational team. They’re invested in edifice a real business relationship. The team spent condition time with our business colleagues, learning how technical processes tell to our non-technical business drivers. They were wonderfully occupied in those dicsussions, always asking careful questions during conversations.
They are always ready to take on a challenge, even if it’s not a expertness set they have innerly. If they don’t have a expertness, they will work hard to find it, even if that resources sourcing a different role for us. They accurately handle our expectations touching their capabilities.
What aspects of their work would you like to get betterd?
No, there aren’t any areas where they could better.
Do you have any advice for possible clients?
Future clients should invest time in allowing the team to create a business relationship based on reciprocal knowledge. Their emphasis on forging connections has been hugely precious to us. Invest that time up front, as fastly as you can, and it will pay dividends in the long run.
