[
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
Thank you for getting involved. I've read and appreciate all of your
mails to this list, and now have a bit of time to respond to some of the
points you've raised...
On 2026-04-22 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?
I think it does mean something, i.e. the SME believes we've started,
we're not finished, and apparently thinks we still have approximately as
much to do as we've already done.
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.
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).
We would like to improve the scoring, to make it more useful, so
suggestions for improvement are very welcome and I think you may be
well-placed to make some :-)
br
Paul
