<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Objectives and Key Results in Software Teams: Challenges, Opportunities and Impact on Development · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2311.00236/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2311.00236/feed.xml" rel="self" type="application/rss+xml" /><item><title>Objectives and Key Results in Software Teams: Challenges, Opportunities and Impact on Development — mentioned by koliber</title><link>https://news.ycombinator.com/item?id=38642212</link><guid isPermaLink="false">urn:hackerpapers:mention:2311.00236:38642212</guid><pubDate>Thu, 14 Dec 2023 15:13:57 GMT</pubDate><description>&lt;p&gt;The key results are not a problem just for you! You are hitting the nail on the head. Check out section 6 of this study ( https://arxiv.org/pdf/2311.00236.pdf ) - defining good OKRs is problem number 1, and data issues are the 2nd most cited concern! I wrote a piece about the common issues that people face creating OKRs. There are a few common mistakes that people make which makes key results unmeasurable: https://koliber.com/articles/top-okr-mistakes &amp;gt; the gradual accumulation of small fixes/hacks is not something you can put a metric on I&amp;#x27;ve done it before. On one team, we had a goal to…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2311.00236/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.SE</category></item></channel></rss>
