{"id":716,"date":"2019-04-11T07:50:04","date_gmt":"2019-04-11T11:50:04","guid":{"rendered":"https:\/\/treehousetechgroup.com\/?p=716"},"modified":"2021-05-20T11:24:02","modified_gmt":"2021-05-20T15:24:02","slug":"software-team-productivity","status":"publish","type":"post","link":"https:\/\/treehousetechgroup.com\/software-team-productivity\/","title":{"rendered":"Software Team Productivity"},"content":{"rendered":"\n

The following piece is from the Director of Operations at Treehouse Technology Group, JD Roger<\/em><\/p>\n\n\n\n

Software team productivity is an inherently difficult thing to put metrics \u2014 at least, quantitative metrics \u2014 around. Lines of code, bug rates, etc., are not necessarily good indicators of how well or poorly your software team is doing, especially if they are working on very complex problems. At Treehouse, we work hard to use metrics that give us the best indicators possible to ensure we are making rapid progress for our clients. Some of the key metrics we monitor internally are:<\/p>\n\n\n\n