For years, software engineering teams have chased after a way to measure their efficiency with hard metrics that truly help them improve—without making developers feel spied upon. Finally, we’re getting somewhere.
Any developer knows the pain or potential pain of being measured against dubious metrics like lines of code written or number of pull requests merged that our industry has been known for historically. And any engineering manager knows the backlash and distrust such measures can instill in their team.
[ Also on InfoWorld: Why software engineering estimates are garbage ]
But when boards of directors, engineering leaders, and developers alike all want to know if a process is working, if the team is efficient, and how to be better, we need a way to measure the work that’s being done.
To read this article in full, please click here
InfoWorld
