Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://social.polotek.net/users/polotek/statuses/112374067372711817">Marco Rogers (polotek@social.polotek.net)'s status on Friday, 03-May-2024 10:40:03 JST</a><a href="https://social.polotek.net/@polotek" title="polotek@social.polotek.net"><img src="https://gnusocial.jp/avatar/222890-48-20231213201011.webp" width="48" height="48" alt="Marco Rogers" style="position: absolute; left: 0; top: 0;">Marco Rogers</a><div><a href="https://social.polotek.net/@polotek/112373984721479788" rel="in-reply-to">in reply to</a></div></section><article><p>Confidence intervals are great. The important thing is that they should get refined and narrowed over time. As you get further along, you should become more confident about the delivery timeframe.</p><p>I think this practical execution piece is often lacking in estimation processes. If you only deliver a confidence interval once or twice over the course of the project, that's not useful. If the interval never changes, that's not useful.<br><a href="https://tech.lgbt/@risottobias/112373995567079983" rel="nofollow noreferrer">https://tech.lgbt/@risottobias/112373995567079983</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/3030790#notice-6014750">In conversation</a><time datetime="2024-05-03T10:40:03+09:00" title="Friday, 03-May-2024 10:40:03 JST">about a year ago</time> <span>from <span><a href="https://social.polotek.net/@polotek/112374067372711817" rel="external" title="Sent from social.polotek.net via ActivityPub">social.polotek.net</a></span></span><a href="https://social.polotek.net/@polotek/112374067372711817">permalink</a><h4>Attachments</h4><ol><li><article><header><div>No result found on File_thumbnail lookup.</div><h5><a href="https://tech.lgbt/@risottobias/112373995567079983">Carbonara based life form 👽 (@risottobias@tech.lgbt)</a></h5><div> from <span>Carbonara based life form 👽</span></div></header><div>@polotek@social.polotek.net I just know about confidence levels.like it's okay to be honest about "we're gonna need a bigger boat"I don't want them to concretely estimate anything further than a month out (with any kind of accuracy to the day) because far too many things could go wrong by then.we can estimate inch-pebbles.</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Marco Rogers (polotek@social.polotek.net)'s status on Friday, 03-May-2024 10:40:03 JST Marco Rogers
in reply to
Confidence intervals are great. The important thing is that they should get refined and narrowed over time. As you get further along, you should become more confident about the delivery timeframe.
I think this practical execution piece is often lacking in estimation processes. If you only deliver a confidence interval once or twice over the course of the project, that's not useful. If the interval never changes, that's not useful.
https://tech.lgbt/@risottobias/112373995567079983
In conversationabout a year ago from social.polotek.netpermalink
Attachments
1. No result found on File_thumbnail lookup.
  Carbonara based life form 👽 (@risottobias@tech.lgbt)
  from Carbonara based life form 👽
  @polotek@social.polotek.net I just know about confidence levels. like it's okay to be honest about "we're gonna need a bigger boat" I don't want them to concretely estimate anything further than a month out (with any kind of accuracy to the day) because far too many things could go wrong by then. we can estimate inch-pebbles.

Public

Embed Notice

HTML Code

Corresponding Notice