bajsicki.com/public/posts/realistic-deadlines/index.html

178 lines
5.9 KiB
HTML

<!DOCTYPE html>
<html lang="en-us"><head><script src="/livereload.js?mindelay=10&amp;v=2&amp;port=1313&amp;path=livereload" data-no-instant defer></script>
<title>Realistic deadlines - phil@bajsicki:~$</title>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover">
<meta name="description"
content="Recently a wrote an after-action report on a project that failed to materialize for a number of reasons. The details are irrelevant - whether it worked or not would be an afterthought given its consequences in other places. ">
<link rel="canonical" href="http://localhost:1313/posts/realistic-deadlines/" />
<link rel="icon" href="http://localhost:1313/images/logo_w.png" />
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/modern-normalize/1.1.0/modern-normalize.min.css" crossorigin="anonymous" referrerpolicy="no-referrer" />
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
<link rel="preload" as="style"
href="https://fonts.googleapis.com/css?family=Noto+Serif+SC|Noto+Emoji&display=swap" />
<link rel="stylesheet"
href="https://fonts.googleapis.com/css?family=Noto+Serif+SC|Noto+Emoji&display=swap"
media="print" onload="this.media='all'" />
<noscript>
<link rel="stylesheet"
href="https://fonts.googleapis.com/css?family=Noto+Serif+SC&display=swap" />
</noscript>
<link rel="stylesheet" href="/css/hugo-tufte.min.css">
<link rel="stylesheet" href="/css/hugo-tufte-options.min.css">
<link rel="stylesheet" href="/css/hugo-tufte-override.css">
</head>
<body>
<article id="main">
<header class="brand">
<h1>phil@bajsicki:~$</h1>
<p class="subtitle"></p>
<nav class="menu">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/about/">About</a></li>
<li><a href="/posts/">Posts</a></li>
</ul>
</nav>
<hr />
</header>
<section>
<h1 class="content-title">Realistic deadlines</h1><span class="content-meta"><p class="author">[Phil Bajsicki]</p><p class="date">2022-09-30</p><span>3 min read&nbsp;</span><a href="http://localhost:1313/tags/projectmanagement">projectmanagement</a>&nbsp;<a href="http://localhost:1313/tags/work">work</a>&nbsp;<a href="http://localhost:1313/categories/business">@business</a>&nbsp;</span></section>
<section><p>Recently a wrote an after-action report on a project that failed to materialize for a number of reasons. The details are irrelevant - whether it worked or not would be an afterthought given its consequences in other places.</p>
<p>One of the key skills of a great project manager is to set realistic timelines. If this imaginary PM sets them badly, it is very easy to see how this can rapidly snowball.</p>
<p>Suppose you have two projects, both happening in parallel, and a delay of one day - let&rsquo;s say something broke and requires fixing.</p>
<p>It means you&rsquo;ll only spend one day catching up on the project that was delayed, but also you&rsquo;ll also incur an additional day&rsquo;s delay on the other project, because you were busy cleaning up the mess.</p>
<p>That&rsquo;s a two day delay, from a single project&rsquo;s issue.</p>
<p>Now, if you have multiple projects, this snowballs to the point where each additional project carries its own penalty in the same way.</p>
<p>Imagine if a company has 10 projects they are working on, and someone gets sick for a few (let&rsquo;s say 3) days. If there is little capacity for someone else to pick up the slack, that&rsquo;s&hellip;</p>
<ol>
<li>A three day delay on the first project.</li>
<li>A six day delay on the second project.</li>
<li>A nine day delay on the third project.</li>
<li>A twelve day delay on the fourth project.</li>
<li>A fifteen day delay on the fifth project, and so on.</li>
</ol>
<p>To keep things moving, it is not at all necessary to &lsquo;speed things up&rsquo; or &lsquo;crunch&rsquo; or other inhumane things. The simple, natural and most Zen solution is to <em>take these delays into account.</em></p>
<p>For each additional project that you take, add a few days time to the deadlines of <strong>all</strong> projects.</p>
<p>So that if someone is sick and out, that&rsquo;s not a problem. They can come back when they&rsquo;re all good and ready, and everything is still perfectly on time.</p>
<p>If you add a week&rsquo;s time for each additional project you&rsquo;re working on, you&rsquo;re easily safe, on time, and with no additional issues. And what I mean here is, for EVERY project add (number-of-projects x 1week) on top of the expected timeline to completion.</p>
<p>Of course, this can create issues when you sell to customers that want the shiny thing &rsquo;now now now,&rsquo; but if they&rsquo;re flush with money&hellip; hey we have time to spare on additional work for a pretty penny too!</p>
<p>Work that we wouldn&rsquo;t be able to accept if we were promising tight deadlines and crunching to meet them.</p>
<p>A better opportunity comes along sooner than expected. Take it easy.</p></section>
<section><footer class="page-footer">
<hr />
<div class="previous-post" style="display:inline-block;">
<a class="link-reverse" href="http://localhost:1313/posts/saas-business-foss/?ref=footer">« Some thoughts on SaaS and business applications of...</a>
</div>
<div class="next-post", style="display:inline-block;float:right;">
<a class="link-reverse" href="http://localhost:1313/posts/call-it-a-day/?ref=footer">On the value of calling it a day (and how to get... »</a>
</div>
<ul class="page-footer-menu">
</ul>
<div class="copyright">
<p>
©2024 Phil Bajsicki
</p>
</div>
</footer>
</section>
<section><nav class="menu">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/about/">About</a></li>
<li><a href="/posts/">Posts</a></li>
</ul>
</nav>
</section>
</article>
</body>
</html>