[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tsf-dev] TSF process feedback, part 2: evaluating statements
|
Sam,
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?
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).
Without an agreed method of scoring it's not possible
to combine scores to create a meaningful global value.
That said, it's important to remember the limits of this approach:
* Does the testing cover all possible invalid inputs?
There should be a statement specifying what is covered.
* When did those tests actually last run? How old is the report you're
reading?
Again, another statement.
* How do failing tests affect the score? Should it go to zero if a
test failed? (See the related question in the previous section).
Yes.
* Is the validator script doing what you expect? Maybe it has a bug.
Statement covering how the script was tested.
--
Derek M. Jones Evidence-based software engineering
blog:https://shape-of-code.com
