How to Measure Productivity as a Developerby@bobhacks

How to Measure Productivity as a Developer

tldt arrow
Read on Terminal Reader🖨️

Too Long; Didn't Read

Can we measure developer productivity, and are we really seeing value from these metrics? How developers and their employers benefit depends on how productivity is assessed. Inputs (think: time invested) are pretty easy to measure but not very useful to measure productivity. “Classic” output measurements are pretty disastrous. Gauging work output based on lines of code or amount of pull requests is very similar to measuring a restaurant’s success by the amount of leftover food they have at the end of a night. Plus, most of these metrics can easily be manipulated by the developer. Measuring productivity is further complicated considering that software development is both an individual and team sport. Development velocity and agility are discussed as two productivity measures that have the potential to overcome these problems. Paired with developer empowerment, allowing developers to work on their own schedules, increased developer productivity is almost guaranteed.

Companies Mentioned

Mention Thumbnail
Mention Thumbnail

Coin Mentioned

Mention Thumbnail
featured image - How to Measure Productivity as a Developer
Metabob HackerNoon profile picture

@bobhacks

Metabob

About @bobhacks
LEARN MORE ABOUT @BOBHACKS'S EXPERTISE AND PLACE ON THE INTERNET.
react to story with heart

RELATED STORIES

L O A D I N G
. . . comments & more!
Hackernoon hq - po box 2206, edwards, colorado 81632, usa