[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tsf-dev] TSF process feedback, part 2: evaluating statements
|
Hi Derek,
Props for being the only person so far to reply to these messages.
On 22/04/2026 20:39, Derek M Jones via tsf-dev wrote:
For individual statements, it can be nice for an expert to record how
close we are to achieving some goal, by putting e.g. 0.5 against the
statement to show that we're halfway there.
Given that 33% of estimates are within a factor of two,
and 95% within a factor of 4
https://shape-of-code.com/2024/03/10/what-is-known-about-software-
effort-estimation-in-2024/
does any claim of being half-way there mean anything?
That is a fair point.
then my score must be 0.0. The statement says all the docs are in Git,
I know for a fact they are not, and so I'm completely confident that the
statement is false. The TSF docs don't make it clear which is the right
interpretation at present.
The answer is 0.
I agree on this, FWIW. Historically it's not how we've always done
scoring internally though. This suggests that for the scoring to be
effective, as you observe below, TSF might need to specify what the
score means in more detail.
Lesson: Agree what the scores mean within your team!
This means that scores are different across teams/projects, which makes
them useless for anything other than an indicator of team
progress (which is not the purpose of these scores).
Without an agreed method of scoring it's not possible
to combine scores to create a meaningful global value.
Sam
--
Sam Thursfield (he/him), Software Engineer
Codethink Ltd. http://www.codethink.co.uk/
