Introducing Qwiet AI AutoFix! Reduce the time to secure code by 95% Read More

Number of lines of code. Number of commits. Number of bugs caught. Such are the old metrics of development. All very macho, all very developer bro—and all not terribly effective. These days, development is about quality, not quantity. It is about closing the gap between development and business, so technology solves tangible problems.

At cdCon in Vancouver, I recently discussed this topic with fellow technologists and product managers from JP Morgan, Roku and DeployHub. Everyone came to the discussion with different experiences and different business needs, but when it came down to the process of defining the role of developers and making them more productive, there were key themes and rules of engagement we all agreed on.

Top view Business developer hand using Kanban board framework on virtual modern computer

Rule 1: Time to get a framework.

As someone who spent more than 12 years in development, I get it. What works is what works is what works. And with schedules and budgets always tight, most developers don’t have the luxury to mess around with ideation. At the same time, there is a big difference between working hard and working smart.

Working smart is something I learned the hard way. After one-too-many experiences going off into a black box for months and coming back with what I thought was