DockYard Development review by Mass Transit Agency at Qualified.One

DockYard reviewed by Mass Transit Agency

DockYard provided Development for Mass Transit Agency with approximate budget = $200,000 to $999,999.

The internal team is satisfied with DockYard’s development work and the general feedback has been positive so far for the API. Communication is effective and they’re unique in their level of technical skill, however, they could work on having engineers available for onsite work.

Review summary:

DockYard mainly assists with revamping an API that’s used by third-party developers on customer-facing technologies. They’re addressing several issues with four engineers that support the internal team, remotely.

Mass Transit Agency, Head of Engineering for Customer Experience

API Dev for Major Mass Transit Agency

Please find below 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 engineering for a major metro method in the United States.

Desired goal

What challenge were you trying to address with DockYard?

We had separate big projects for revamping all that has to do with our client-facing technology. We knew that with this much work, we could use all the help we could get.

Provided solution

What particular tasks were DockYard responsible for?

We’re working on a new website and software that powers predictions for train arrivals, digital signage, and SMS notice for labor disruptions. Most of the work was almost helping us instrument an API that we make useful to third-party developers so that they can create applications that help our riders find out where their vehicles are or get information almost schedules and such.

Currently, we have an older rendering of the API and there are below 100 different applications that use it for whichever iOS or Android or some type of website. There were separate instrumentations that were hard to do and circumstances almost how frequently the API could be used, as it is costly to run. The new rendering of the API will address some of these concerns. With DockYard’s help, we’re wrapping it up and are almost to put it out there for use.

What is the team dynamic?

We worked with four dedicated engineers over the order of our engagement who innately became part of our team.

How did you come to work with DockYard?

They are a pretty well-known organisation, so we reached out to them.

How much have you invested in them?

We have spent more than $200,000.

What is the terminal result of working with DockYard?

We began working with them almost December of last year and the work is ongoing.

Results achieved

Are there any measureable or plum results?

The general feedback we have accepted has been real and our team is lucky with the outgrowth they have done.

How did DockYard accomplish from a project treatment standpoint?

We’re lucky with the level of interaction we’ve accepted so far. We mainly use Slack, phone calls through Google Hangouts, and we may meet in individual but this is very infrequent.

What is (from your point of view) the key factor to pay observation while intercourse with DockYard?

We like their technical expertise, they’re knowledgeable in what they do.

What aspects of their work would you like to get improved?

The engineers that they had were all distant, which was a possible challenge. Our preference and a recommendation for them would be to try and get engineers who could work with our team onwebsite.