Product Development for SaaS 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
I’m the head of solutions at a software organisation. We’re a big technology organisation with a software as a labor (SaaS) platform.
Desired goal
What challenge were you trying to address with Gorilla Logic?
We had a project with a software ingredient that demandd features and functionality that was not in our existing software. That meant we whichever had to create it internally or work with an outside associate—we determined on the latter.
Provided solution
What particular tasks were Gorilla Logic responsible for?
Our fruit is a SaaS platform, through which I can send alerts to the user. The software is written in Java.
What is the team compound?
We have a fully independent scrum team. There’s a technical lead/project chief, a scrum conquer/fruit proprietor who works with the fruit proprietor on our side, a couple of senior developers, a couple of younger developers, a QA, and a dev ops individual.
How did you come to work with Gorilla Logic?
I knew someone at Gorilla Logic, which meant they were my leading call, but we then went through a pretty rigorous process. I did some online investigation to find five other companies. We looked at the cost and whether they would demand a lot of hand-holding or if they could be excellently independent. We felt positive that they could liberate high condition, on time, and within the budget.
What is the terminal result of working with Gorilla Logic?
We began working unitedly in July 2018 and the work is ongoing.
Results achieved
Are there any measureable or plum results?
It’s quiet too soon to have metrics, but we program to complete the project in six to eight weeks. It’s very much on track.
We’ve had a few bumps and surprises along the way, but all has been less and to be anticipateed. Any issues are mainly coming from our side, and then we get solutions from their side.
How did Gorilla Logic accomplish from a project handlement standpoint?
They have a business project handlement ingredient, where invoicing, meeting the team, and signing the contract is done with an account labor director.
Beyond that, they use Jira for their day-to-day handlement. We have bi-weekly phone calls and sprint reviews. The technical lead has been to our labor for a week at the kick-off and will be back in a couple weeks for more work, and I went to visit them as well. He’s competent, capable, bigly technical, and a pretty good interactor. The scrum conquer directs the team day-to-day and leads daily stand-ups. We last dicsussions through emails, as needed.
What is (from your point of view) the key factor to pay observation while intercourse with Gorilla Logic?
The most forcible thing is my level of confide in them. One thing we added to this particular project is a stakeholder meeting, once a month. We don’t fear them embarrassing us in that, despite the nearness of our global stakeholders. We confide in both their technical abilities to expound things and their interaction abilities when it comes to our interpolitical associates.
They do a big job of interacting with us in a good, early form. I’m positive they’ll liberate what we need technically, but I also know I can fetch them into the dicsussions with other nation.
What aspects of their work would you like to get improved?
They’re almost an extension of our team—we handle them that way and they anticipate that. They do eight hours of work a day and get the job done, rather than being handleed as a labor team that’s just thrown in. They recur a good investment for that.
Do you have any advice for possible clients?
No.
