{"id":601,"date":"2011-05-25T07:15:06","date_gmt":"2011-05-25T07:15:06","guid":{"rendered":"http:\/\/mikekuphal.azurewebsites.net\/?p=601"},"modified":"2011-05-25T07:15:06","modified_gmt":"2011-05-25T07:15:06","slug":"agile-planning-remaining-work-hours-completed-work-hours","status":"publish","type":"post","link":"https:\/\/mikekuphal.com\/?p=601","title":{"rendered":"Agile Planning: Remaining Work Hours > Completed Work Hours"},"content":{"rendered":"<p><a href=\"https:\/\/mikekuphal.com\/wp-content\/uploads\/2013\/12\/80done.gif\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image:none;padding-left:0;padding-right:0;display:inline;float:right;padding-top:0;border-width:0;\" title=\"80Done\" border=\"0\" alt=\"80Done\" align=\"right\" src=\"https:\/\/mikekuphal.com\/wp-content\/uploads\/2013\/12\/80done_thumb.gif\" width=\"240\" height=\"240\" \/><\/a>Teams I Scrum Master do not track completed hours.&#160; Remaining work hours are the ticket.&#160; That is where the real information is held.&#160; This is not an easy transition for the Project Manager in all of us.&#160; Even for the team members, many of whom have been asked to track completed work hours for years and years, it can be difficult to give up the mentality of reducing a bank of hours predefined prior to the task starting.&#160; <\/p>\n<p>So you ask: by tracking completed hours, don\u2019t you simply subtract the completed hours from the original estimate and then you have Remaining work hours anyway?&#160; No.&#160; The only way that would be true is if all the original estimates were perfect from the start.&#160; That simply isn\u2019t true, and contrary to Agile thinking where you expect change, embrace it actually.&#160; <\/p>\n<p>Statements like \u201cI am 80% done\u201d go away.&#160; Any experienced Project Manager will cringe at the sound of that statement as we all know the PM truism that it\u2019s that last 20% that seems to take longer than that first 80% reportedly done did.&#160; The remaining hours are all you hear about and doesn\u2019t that really tell the story you want to know anyway, mainly: how long until the work is done?<\/p>\n<p>A big question I have heard regarding this switch is: \u201cIf we don\u2019t track actual hours, how do we ever know if our estimates are getting better?\u201d&#160; Scrum\u2019s answer: the Velocity metric will take care of that.&#160;&#160; It really isn\u2019t about being ultra accurate estimation wise, but instead it\u2019s more about sizing tasks well to allow for achievable Sprint goals when picking tasks to commit to for the upcoming sprint.&#160; Tracking actual completed work hours does not directly help with that goal what so ever.<\/p>\n<p>When the team switches to reporting just Remaining work hours, they also need to switch their mentality to one that has them reevaluating how much work is left on the task at least once a day and updating the task to reflect this info.&#160; It\u2019s important to stress that the tally can go up\u2026 it\u2019s not a number to decrement only (an old habit of completed hours reporting that can be hard to break). <\/p>\n<p>Next up in this series, the importance of making it E-A-S-Y for the team to update Remaining work hours at any time.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Teams I Scrum Master do not track completed hours.&#160; Remaining work hours are the ticket.&#160; That is where the real information is held.&#160; This is not an easy transition for the Project Manager in all of us.&#160; Even for the team members, many of whom have been asked to track completed work hours for years &hellip; <a href=\"https:\/\/mikekuphal.com\/?p=601\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Agile Planning: Remaining Work Hours > Completed Work Hours&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,5],"tags":[],"class_list":["post-601","post","type-post","status-publish","format-standard","hentry","category-agile","category-scrum"],"_links":{"self":[{"href":"https:\/\/mikekuphal.com\/index.php?rest_route=\/wp\/v2\/posts\/601","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mikekuphal.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mikekuphal.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mikekuphal.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mikekuphal.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=601"}],"version-history":[{"count":0,"href":"https:\/\/mikekuphal.com\/index.php?rest_route=\/wp\/v2\/posts\/601\/revisions"}],"wp:attachment":[{"href":"https:\/\/mikekuphal.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=601"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mikekuphal.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=601"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mikekuphal.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=601"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}