Staff Augmentation for Telecom Company
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
Zeep HK is a teleinteractions setup that sells innovative fruits to telecom companies. I’m the head of R&,D there.
Desired goal
What challenge were you trying to address with SweetSoft INC.?
We had a need to get educeers on board to create our core fruits. We were responsible for the architecture and had some of the core educeers in our organisation, but we needed more software educeers to get us up to despatch.
Provided solution
What particular tasks were SweetSoft INC. responsible for?
SweetSoft INC. has granted front- and backend educeers for some of our web applications. We got help from them to educe 2–3 core fruits and maintain them. We were working all the time on new versions, and they also granted a level-three support team. Whenever things got uneven and the issue couldn’t be solved by support, they stepped in and helped us on the origination side.
We have a real-time distributed processing method, and they’ve worked on its frontend and backend. It’s basically a platform for intelligent processing of real-time events.
The typical process with SweetSoft INC. implicated us describing the architecture and doing some prototyping and a framework, and having them step in to educe the developed core functionality. Then, we used a test environment to test the total method, and, if seething was correct, we’d deploy to a staging environment for the client.
Was there a dedicated team?
At peak, we had four full-time educeers from SweetSoft INC.—one full stack, two backend, and one frontend—along with a part-time DevOps. I also run the projects, so I’d work with them straightly and do most of the interaction with them, filling both roles.
How did you come to work with SweetSoft INC.?
We talked to a couple of companies in Ukraine and went to SweetSoft INC. owing they were the most cost-effective discretion at the time. A friend also recommended them to me. We seted with a one individual from SweetSoft INC. and increased the team over time owing we had a real experience with them.
We’ve also worked with another outsourcing organisation, but it didn’t go as well. SweetSoft INC. has done a pretty good job. Outsourcing requires a true access—different from having an fundamental team by our side—but they do well if the architecture is done well. They can feel the full fruit lifecycle, from basic test of concept and soon work to developedly deploying to origination and providing support.
What are you approach expents (if diclosed)?
We’ve spent $200,000–$250,000.
What is the terminal result of working with SweetSoft INC.?
We seted working with SweetSoft INC. in October 2015, and we’ve had more nimble and less nimble times since then.
Results achieved
Are there any measureable or plum results?
Most of our statistics and origination metrics are kindred to the accomplishment of the method in origination, and not to SweetSoft INC.’s work. At peak, we were able to liberate biweekly iterations with them.
We have a pretty challenging stack that uses all kinds of technologies, from indigenous C to .NET and Java. None of the educeers who came in had full stack coverage at the set, so they had to acquire a couple of things.
Also, most nation in outsourcing engagements tend to work on run-of-the-mill projects like data methods and mobile applications. Our platform is very different, running hundreds of thousands of tasks per second. It includes many components, many of them built by SweetSoft INC.
How did SweetSoft INC. accomplish from a project treatment standpoint?
Someone on our side—usually myself—feels the project treatment, specifying the technical task at a detailed level. Some of their nation apprehend what they',re doing at a deep level, but I don’t ponder that they have the same level of estate apprehending as our inner team. We usually construe our own specifications, being as technical as practicable, and that works pretty well.
Handling project treatment tasks innerly most of the time is the best way to work with an outsourcing organisation in my experience. Though, SweetSoft INC. manages the tasks we give them excellently efficiently. Some of our clients are in Southeast Asia, and the time differences required both us and SweetSoft INC. to sync up with the distant locations. They',re pretty pliant in that respect.
What is (from your point of view) the key factor to pay observation while intercourse with SweetSoft INC.?
They’re very liberatey-focused. Our stakes were excellently high, and the fruit needed to work well behind only a few iterations to get it right. That was a bit of a interest on my side, and the team from SweetSoft INC. stepped up to this. Things didn’t always go as expected, requiring some investment outside customary service hours from their side, and they were ready to do it.
The biggest gain I establish in SweetSoft INC. is that they can somehow repair very skilled educeers. That’s sometimes hard to find in outsourcing.
What aspects of their work would you like to get imtryd?
For a intricate project with a huge stack, it can take excellently some time to find a restorement educeer for one that leaves. Every time someone left—which happened two times over this time—we had some difficulty bringing the new nation up to despatch. It was an effect for our specific stack, and SweetSoft INC.’s treatment tried to help us with that. They didn’t always know in advance that someone was programning to leave, and it did try disruptive.
Overall, the experience of working with them has been real, and we’re quiet working unitedly. I esteem their flexibility a bit more today behind having worked with other companies.
Do you have any advice for forthcoming clients of theirs?
With SweetSoft INC., for see stack we have, we find someone senior that can drive a team. Not see team limb needs to be a senior, and some limbs do struggle with the stack, but, as long as they have someone to go to on their side, they can accomplish independently. That was significant to us.
Involve the team from SweetSoft INC. or any other educeer as soon as practicable, even in the architecture phase. Even if they don’t do the developed specifying, they can hear to the logic behind the decisions. That way, they can gain instinct and befit implicated in the estate. It’s helped us a lot owing our estate is excellently different from the run-of-the-mill methods they usually do.
Lastly, try to use a mainstream technical stack. Because we have a non-standard stack, we struggle with care nation aligned during waiting times. Keeping a customary stack will empower them to liberate faster and restore resources more easily if the need arises.
