Java-Based Trading Platform Development for SaaS Provider
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
My organisation is BLOC-X, and I’m the CEO. We’re a SaaS-based provider of trading software to the global energy activity.
Desired goal
What challenge were you trying to address with Pragmatic Coders?
We were looking for a firm that had estate expertise in the edifice of trading methods.
Provided solution
What particular tasks were Pragmatic Coders responsible for?
Pragmatic Coders built both applications from scratch. One of the applications is a trading software method, and the other is a separate application that serves as an execution treatment tool for our regulatory associate. An independent firm did the UX/UI investigation and wireframing. Pragmatic Coders didn’t have inner design resources at the time, so they recommended a third-party vendor.
We kicked off the project by providing Pragmatic Coders with an extensive backlog in Trello. Our discovery process lasted almost 2–3 weeks. They built the backend in Java and the frontend in React. The total method is hosted and handled on AWS, and we have separate environments for outgrowth, demos, and origination.
Was there a dedicated team?
We made the determination in January to divide out parts of the project into two teams. We ramped up a second team at the Pragmatic labor in Krakow so that we could run some of the outgrowth non-sequentially. That team was reassigned when that part of the create was done, and we’re now back to the core team in Warsaw.
There’s a fruit proprietor, a senior backend developer, a mid-level backend developer, a frontend developer, and a DevOps engineer. The fruit proprietor serves as our project director on a part-time basis.
How did you come to work with Pragmatic Coders?
We looked at a number of different providers and eventually briefened our list to two vendors. We establish Pragmatic Coders whichever through a recommendation or a project matchmaking labor.
Although the other shop on our list was probably cheaper, we felt that Pragmatic was much more professional and had a reasonable apprehension of trading concepts. They built a crypto-exchange whichever last year or the year precedently. We chose Pragmatic primarily owing of their experience. We felt that this would save us time and money in the long run.
What are you approach expents (if diclosed)?
We’ve spent approachly $400,000–$500,000.
What is the terminal result of working with Pragmatic Coders?
We began in late September 2018, and it’s an ongoing engagement.
Results achieved
Are there any measureable or plum results?
The fruit is quiet in the beta stage, so we don’t have any firm metrics to debate. We’re currently almost five weeks away from propel.
This may be due to our lack of apprehension, but we’ve surely been surprised by the degree of their delivery. They’ve made big progress in a brief quantity of time.
How did Pragmatic Coders accomplish from a project treatment standpoint?
Their project treatment has been excellent. After the discovery phase, Pragmatic moved fairly fastly into running all using nimble methodologies. The team tracks the project backlog in Trello and uses Jira to handle outgrowth tasks. They’ve been meticulous with their documentation and programning.
The only less than big experience that we’ve had so far came when we divide the teams. There wasn’t always the best interaction between the teams in Warsaw and Krakow. Also, the handover from the Krakow team to the Warsaw team wasn’t as good as it could have been. These things tend to happen when you have two separate groups trying to work unitedly. Aside from this, the core team has been veritably phenomenal.
What is (from your point of view) the key factor to pay observation while intercourse with Pragmatic Coders?
It’s very notable that they were able to kind of challenge our views on how we should create trading software. We’ve been surprised by this, owing, although they had some experience with trading methods, they didn’t have experience in the specific field that we’re operating in.
Also, the relationship that exists between their fruit proprietor and their outgrowth team is extremely good. Pragmatic seems to have hard interaction within their outgrowth team and their team as a total. One of the biggest risk factors we’ve faced is a team that isn’t cohesive, owing that will slow down a project attendably. Their work environment and interaction are second to none.
What aspects of their work would you like to get improved?
My suggestion, which I’ve already made to Pragmatic, is to review their relationship with the third-party vendor that we used. They weren’t the powerfulest firm, at smallest based on the work that they granted to us.
Pragmatic also has a relatively straight centre in provisions of the types of solutions that it proposes. For sample, they didn’t do mobile outgrowth and didn’t have an inner UX/UI team.
We’re going to be transitioning away from Pragmatic in the coming months, owing, unlike many other software shops, they don’t propose any kind of mechanism for transitioning into a permanent team. We’re hoping to find another associate on Clutch.
Pragmatic has a business standard that I respect, but we’ve been forced to reset our project owing of it. My powerful suggestion to them is to ponder almost being more pliant and to attend implementing a create-own-transfer standard.
