{"id":902,"date":"2021-02-12T13:50:33","date_gmt":"2021-02-12T18:50:33","guid":{"rendered":"https:\/\/steelray.com\/blog\/?p=902"},"modified":"2021-02-12T14:18:26","modified_gmt":"2021-02-12T19:18:26","slug":"keep-the-deliverable-in-mind","status":"publish","type":"post","link":"https:\/\/steelray.com\/blog\/?p=902","title":{"rendered":"Keep the Deliverable in Mind"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">I had just finished running a quick test on a new Analyzer release. We had released a new version recently, and during the installation, Microsoft Defender SmartScreen (part of Windows) did not love our new installer. It warned you that the setup program wasn&#8217;t to be fully trusted. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Yikes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">I won&#8217;t go into the details, but we had to purchase and configure a higher-security code signing certificate and create a new installer that used it. It was a bit of an ordeal to figure out what to order and how to get it configured correctly, and I immersed myself in those activities.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">I tested the fixed installer and verified that Microsoft Defender SmartScreen had no complaints with the new certificate. No more warning message. I let the developer know the test had passed, and she asked whether this would be a private or public release.&nbsp;&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">I had to think about it for a minute before remembering: <strong>the whole&nbsp;purpose&nbsp;of fixing the certificate is that our latest release has this scary warning<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">So, yes, it had to be a public release. Because it took me a minute to answer, it&#8217;s clear to me that&nbsp;I had lost sight of the purpose of the work. I had worked on fixing the issue while not keeping in mind the end result, the deliverable. I had not asked myself periodically,&nbsp;<em>&#8220;Why does doing this matter?&#8221;<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Keeping the deliverable in mind when working on an activity or project is vital for at least three reasons.<\/p>\n\n\n\n<ol class=\"wp-block-list\"><li><strong>You&#8217;ll get there faster. <\/strong>Distractions are easier to say &#8216;no&#8217; to when the deliverable is front-of-mind.<\/li><li><strong>You&#8217;ll end up closer to the target. <\/strong>It&#8217;s hard to end up in an unintended place when you remind yourself daily of your destination.<\/li><li><strong>You might realize it&#8217;s not worth doing now. <\/strong>Suppose you have a hard time coming up with a deliverable, output, or purpose of the activity. If it won&#8217;t matter to anyone or anything, isn&#8217;t it taking up a more deserving activity&#8217;s time slot?<\/li><\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">It&#8217;s essential for teams that <strong>everyone has the same definition of the deliverable<\/strong>;&nbsp;they need to be on the same page.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Concerning the certificate and code signing: even though it&#8217;s a huge pain, it&#8217;s an excellent thing. You want to have a high level of trust when installing anything on your computer. We want you to feel confident that the installer you&#8217;re running came from us.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Be Safe!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I had just finished running a quick test on a new Analyzer release. We had released a new version recently, and during the installation, Microsoft Defender SmartScreen (part of Windows) did not love our new installer. It warned you that the setup program wasn&#8217;t to be fully trusted. Yikes. I won&#8217;t go into the details, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12,4],"tags":[],"class_list":["post-902","post","type-post","status-publish","format-standard","hentry","category-project-management","category-teams"],"_links":{"self":[{"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/902","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=902"}],"version-history":[{"count":4,"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/902\/revisions"}],"predecessor-version":[{"id":908,"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/902\/revisions\/908"}],"wp:attachment":[{"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=902"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=902"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=902"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}