Videology's SVP of Engineering asks: 'How much pain does your dev team cause?' - Technical.ly Baltimore

Dev

Oct. 6, 2016 9:39 am

Videology’s SVP of Engineering asks: ‘How much pain does your dev team cause?’

During Baltimore Innovation Week, Anand Natrajan spoke of how to create a culture where engineering teams produce both high velocity and high quality work.

Can your dev team have both high velocity and high quality?

(Presentation screenshot)

Full Disclosure: Technical.ly organizes Baltimore Innovation Week, during which this event took place. The event was sponsored, in part, by Videology, though that is unrelated to this report.
To make a great software business, you must find that “special happy place” when the engineering and sales teams are in sync.

“You want your developers on a product cycle, not solving business critical issues,” said Anand Natrajan, a head of engineering for Videology, the McHenry Row-based adtech company that is among Baltimore’s vaunted Ad.com diaspora.

Cultivating that kind of team environment becomes self-fulfilling: great dev teams celebrate high quality, which they do at greater velocity when it becomes a point of proactive pride, not a response to broken systems, said Natrajan, a personable four-year veteran of the company. He was among a dozen highlighted speakers at the Baltimore Innovation Week Presented by 14 West Dev Talks, an afternoon of case studies from prominent Baltimore engineers. Held at Motor House on North Avenue, the event was presented by Natrajan’s firm Videology and cybersecurity powerhouse Tenable Network Security.

To track success in building out that product cycle, Videology follows a host of key metrics. From 2015 to projections through the end of 2016, their team has cut the number of high-urgency incidents they’ve had to handle by half and so their product releases have jumped by 74 percent, he said.

It’s easy to see why. In July 2015, the Videology team spent 3,200 hours on fixes, the equivalent of 20 full-time people. This July, that total was 1,400 hours, or fewer than nine people, he said.

The question of how is trickier, of course. Natrajan noted it’s largely a question of culture: the dev team has to understand that its role is to support the overall business.

“How much pain does your engineering team cause?” he said.

That culture comes with keeping a dev team happy (more about work-life balance than keg parties, he said), expecting excellence and, yes, tracking thoroughly what your team is working on.

Advertisement

-30-
LEAVE A COMMENT

Advertisement

Baltimore Innovation Week 2016: 70 events and 10K attendees

10 ideas from Baltimore leaders on how tech can have a voice at City Hall

Making video games is more empowering than playing them

SPONSORED

Baltimore

How Think|Stack and Year Up are cultivating local tech talent

Baltimore

Terbium Labs

Analyst

Apply Now
Owings Mills, Maryland

Mind Over Machines

Consultant (Software Developer)

Apply Now
Baltimore

Protenus

Data Engineer

Apply Now

When violence struck at #BIW16, here’s what one Baltimore native reflected on

Here are the winners of the 4th annual Baltimore Innovation Awards

A crew from across the country came to tour Baltimore’s tech scene

SPONSORED

Baltimore

Let these free workshops help your business really take off

Baltimore

Protenus

Front-End Developer

Apply Now
8 Market Pl, Suite #402, Baltimore, MD, 21202

PaRaBaL

Development Support Engineer

Apply Now
8 Market Pl, Suite #402, Baltimore, MD, 21204

Parabal Inc.

Enterprise Mobility Engineer

Apply Now

Sign-up for regular updates from Technical.ly

Do NOT follow this link or you will be banned from the site!