News for hackers. Stuff that matters.
Re:Objections are goals by slavik81 on Wednesday October 10, 2018 @09:13AM (#18184491)
The stated goals are not tied to any business value. This is putting the cart before the horse. TCR is a means to an end, not an end itself.

Dale's essay on "Resistance as a Resource" is very good, but this is not how I would apply it.

Re:Objections are goals by asplake on Wednesday October 10, 2018 @10:30AM (#18185160)
Right. I designed a workshop/coaching game 15-minute FOTO (from obstacles to outcomes) [1] which does a similar “flip” from the negative to the positive; however by construction the input obstacles are with respect to some kind of objective. 4-Oh if you like - objective, obstacle, outcome, more outcomes. See also the classic coaching model GROW (Whitmore)

[1] https://www.agendashift.com/15-minute-foto

Re:Objections are goals by AstralStorm on Wednesday October 10, 2018 @09:28AM (#18184599)
Indeed, specifying alternatives and business impact is important.

Sample comparable (not exclusive) technique would be design by contract with automatic verification. Likewise just not testing or limiting scope of tests or prioritizing tests differently for different modules.

If you say that writing tests first is superior, you have to show why and how much. And preferably with not anecdotal evidence.