AgileEngine

Introduce your business and what you do there.

I was the director of consumer engineering for LivingSocial at the time of working with AgileEngine.

What challenge were you trying to address with AgileEngine?

The company was looking for a way of improving its A/B testing in order to allow for tests to be executed across consumer web and native mobile applications. We had some goals around response time and the ability to handle certain loads and concurrency. We hadn’t worked with any other companies for A/B testing in particular, but we did have some other engagements with outside consulting agencies, which didn’t result in a happy outcome, in general.

What was the scope of their involvement?

AgileEngine worked with our internal team of developers to determine requirements. They performed most of the development work for a new A/B testing engine.

The interface was developed as a standard API endpoint and the backend was a Scala application. The technology was chosen in order to meet the requirements of response time and handle the concurrence of different loads. In retrospect, I think it was a solid choice but it did add some obstacles.

While we did have Scala in our stack, we were mostly a Ruby on Rails shop, so there was less familiarity with the code base on our end. This is something which could have been averted through stricter requirements, but AgileEngine was able to deliver a strong solution which met the specifications while overcoming some communication difficulties and meeting the terms dictated to them.

We also dictated some of the expectations around what the interface would look like. Throughout the process, we talked about those requirements and adjusted as necessary.

How did you come to work with AgileEngine?

Alex Kalinovsky, their CEO, reached out to our VP of engineering at the time, who was exploring the idea of potentially doing some work. I believe they had met previously and Alex followed up. At least a part of their team was based in the Washington DC area, so it made sense to use them. Most of the developers were based in Ukraine, but they were able to adjust their schedules.

How much have you invested with AgileEngine?

The cost of their work was in the mid-5-figure range.

What is the status of this engagement?

We started working with AgileEngine in the middle of 2014; I left the company in March 2015. We had an on-and-off engagement over the course of several months. The work was delayed in part by some communication issues and the shifting ownership of the project. Overall, we ended up satisfied with the results.

The engagement ended around April or May 2015 and I doubt that the product is still in use. The company has either integrated or shut down anything that didn’t meet their requirements.

Could you share any evidence that would demonstrate the productivity, quality of work, or the impact of the engagement?

AgileEngine ended up delivering a solid solution. The process was somewhat marked by the changing of their contacts over the course of the engagement.

I left around the time that the engine was being implemented, so I didn’t really see the outcome in terms of its impact on our business or a measurable return on investment.

How did AgileEngine perform from a project management standpoint?

The communication dropped a couple of times but I don’t think it was AgileEngine’s fault. They persevered through that and were able to deliver a solid solution.

There were no real communication barriers and they did their best to minimize the time zone difference. They were able to adjust their schedule and worked relatively late at night on their time, so I had no issues on that front. The primary tools for communication on a day-to-day basis were JIRA and email. We also had stand-ups via Google Hangouts.

What did you find most impressive about AgileEngine?

One thing which separates them from the rest is Alex’s leadership, his willingness to go above and beyond, and his eagerness to deliver top-quality results to customers. He really stands out compared to other contractors I’ve worked with.

Are there any areas AgileEngine could improve?

They could have made it clearer that the shifting leadership on our side would be a problem and be more explicit on how that would impact the delivery of the project.

What tips or recommendations could you share that might increase the likelihood of success with AgileEngine?

Just as with any other contracting engagement, make sure that there’s a clearly designated owner of the project, a single point of contact, and regular check-ins to make sure everything’s on track. This is not particularly applicable to AgileEngine but to contracting engagements in general.

Introduce your business and what you do there.

I am the director of software development for Needles Inc. We are a legal software management company providing lawyers and the legal community with elaborate software that allows them to manage daily arrangements such as cases, clients, and court dates.

What challenge were you trying to address with AgileEngine LLC?

The company was significantly understaffed when I arrived. The developers had little experience and the group suffered from lack of budget to hire new people, which led us to collaborate.

What was the scope of their involvement?

I like to be in touch with what’s happening instead of treating them as a vendor. I’d give AgileEngine requirements, work with them as if they were a remote part of my team, engage in day-to-day activities, and then they’d deliver the product. We had a team of 15 people, including developers, several testers, team leads and a test lead.

AgileEngine has developed the core force behind the software process. They created our calendar along with customization features for workflows and screen layouts. We also built a custom web API and introduced the security module into the software.

We would give AgileEngine requirements, and they would voice any questions or clarifications, which led to a good feedback process.

We used NHibernate and RESTful APIs. AngularJS was used for building the web interface of the software. NUnit was used for unit testing, and JIRA for tracking purposes.    ​​​​​​​

How did you come to work with AgileEngine LLC?

Alex Kalinovsky [CEO, Agile Engine] was the first person I reached out to because he was a coworker of mine. We chose AgileEngine, despite initial vendor concerns, because they were very oriented towards showcasing expertise in their team and Alex was good at selling himself. He fulfilled every promise he made during the initial presentation.

Many companies we looked at had a black-box feel, and when we would hand them requirements, we wouldn’t find out until the end if our expectations were met.

With AgileEngine, it was like working with remote members of our own team because of excellent integration. The process was seamless as far as project management goes. There was an honest interest from their side in making our company’s product work, rather than simply getting our business and making money.

We also chose AgileEngine because they allowed us to choose our resources. Their recruiting team would present developers or testers to me, who I would then interview and decide if they were the right fit. They did a good job of supplying high-quality, talented developers who worked well within our management style and with our team. We found that almost everyone who passed AgileEngine’s prescreens were people we could hire.

How much have you invested with AgileEngine LLC?

We’ve spent around $2 million.

What is the status of this engagement?

We started the project in September 2013, and the work is ongoing.

Could you share any evidence that would demonstrate the productivity, quality of work, or the impact of the engagement?

AgileEngine built off of the software already in place, but they greatly improved performance during the process. Their customizations and restructuring of the code made it work fast and reduced the number of defects. They built automation into the process, so our software was faster and more stable.

How did AgileEngine LLC perform from a project management standpoint?

We communicated through Skype and TeamViewer, and I also traveled to their office to meet all the people we were working with. We interacted multiple times during the day, as if we had a local team.

What did you find most impressive about AgileEngine LLC?

The recruitment process, interactivity, collaboration, project management, and organization impressed me. I never felt left out of the process.

This was our best experience working with contractors. Other groups mainly tried to sell us services to make money, but AgileEngine provided a balanced process and remained honest about meeting expectations. I felt like I was working with a partner who was genuinely interested in the project. From a long-term perspective, AgileEngine provided us service that allowed us to move forward, and have invested in us as much as we have in their services.

Are there any areas AgileEngine LLC could improve?

Of all the experiences I’ve had with other vendors, this was the most positive and least conflicting one. The process didn’t go very well when we were initially hiring developers for the team because of delays, but we were able to staff everyone we needed after we worked that out.

What tips or recommendations could you share that might increase the likelihood of success with AgileEngine LLC?

Be open. The company is interested in keeping your business. There is a lot of experience and knowledge in the management team, so, if there is a project or some problem to be solved, there will be people within AgileEngine who can suggest a better approach. I did a bit of listening and got different opinions, and I’m glad I did.

Introduce your business and what you do there.

I’m the product and project manager for a small startup. We’re developing a unique authentication solution that enables online trust and privacy.

What challenge were you trying to address with AgileEngine?

We needed help with building our initial product.  We have 4-5 people on our core team but needed additional resources to meet a milestone we had. Because we’re just getting started, we wanted to find a balance between affordability and top-notch quality.

What was the scope of their involvement?

AgileEngine acts as an expansion of our team. They provide staff augmentation, and we work together on a rolling basis. Their team has provided a couple of developers — app and frontend — and designers.

What is the team composition?

I work with an account manager via biweekly meetings. She ensures that the engagement is running smoothly.  We initially had a project manager, but it made more sense for us to do that ourselves. So, we eliminated that role and took over running daily scrums ourselves. On a day-to-day basis, we are working with two developers and a designer.

How did you come to work with AgileEngine?

Our startup founder learned about Agile Engine while working for a prior employer. He was impressed by the capabilities they offered, so he kept them in mind for maybe later. When he found himself in a place where he needed to extend his own team, he went directly to Agile Engine to see if they could help.

What is the status of this engagement?

Our partnership began in October 2019 and is ongoing.

What evidence can you share that demonstrates the impact of the engagement?

We’ve really made an effort to help AgileEngine feel that they’re a part of our team and not just contractors. Instead of telling them what to do, we ask for their input. They’ve been great at speaking up whenever they hear or see something that could be better. Their team is invested in our success and excited about what we’re doing. They provide feedback on a daily basis.

As a startup, we have a longer-term vision and shorter-term milestones that come and go. We have to take advantage of opportunities as they come up. It’s sometimes frustrating or difficult to keep a stable product, and Agile Engine has been extremely adaptive to that. They proactively meet our requirements and pivot when we need them to.

How did AgileEngine perform from a project management standpoint?

The ease of staff integration was pretty seamless. They initially presented a specific agile methodology for how they operate, but we ended up developing our own that's works for the blended team.  We use Figma for prototyping, Jira for managing tickets and user stories, Slack for communication, and GitHub for managing code.  Our daily standups happen using Google Hangouts since our team is distributed across multiple locations and countries. 

What did you find most impressive about them?

In general, their team has been really engaged and excited about what we’re doing. They continuously bring that enthusiasm to daily meetings. They’re excited about discussing what they’re working on and providing constructive feedback. That is different from what I've experienced with other contractors. Others want everything spelled out, but AgileEngine is actively engaged in the problem. They help us solve issues rather than just taking orders on what needs to get done.

Are there any areas they could improve?

I can’t think of anything. We don’t have any reservations about what they’re doing for us at all.

Do you have any advice for potential customers?

Their team provides a framework for operation. You can use their model as is, or if you think something would work better, they’re perfectly happy to engage in any manner you’d like. Don’t be afraid to ask because they’re flexible and willing to evolve to what your needs are.