: Gojko left the Soviet Secret Service to take on tougher challenges in software development, leaving only a Bond-villain accent. @GojkoAdzic
@michaelbolton: Why are we so quick to judge others' opinions about testers, when we can be awfully quick to do that ourselves? @GojkoAdzic
:oops I'm not sure what they're advising us to do here but I think my wife would get mad." @gojkoadzic http://yfrog.com/h3durapj
: @GojkoAdzic shows pie chart of what's in software development. 90% is "mistrust"; 10% "other things"
: lack of trust leads to lots of bureaucratic change mgt policies – we don’t trust ppl to talk to each other @gojkoadzic
: "We have horrible bureaucratic processes in companies b/c we don't trust people to talk to each other." @gojkoadzic
: @GojkoAdzic Tracing a requirement thru development: elapsed time of one year for 10 minutes of coding; lots of process cruft.
: Independent testing is there so that when you don’t catch the bug, people can blame you. “Alibi Generators” @gojkoadzic
: Elements of process cruft are "alibi generators." @GojkoAdzic
@lisacrispin: Independent testing is there so that when you don’t catch the bug, people can blame you. “Alibi Generators” @gojkoadzic
@lisacrispin: Big bank mission critical project releases every 2 weeks, zero bugs in production. @gojkoadzic has many ex. of fantastic qual.
@lisacrispin: "Don't tell testers how to test" ignores the range of testing knowledge in all team members. Need teaching, learning. @gojkoadzic
: "Why don't we teach people who don't know enough about testing how to do testing better?" @gojkoadzic
: @GojkoAdzic Why don't testers bother to teach the rest of the organization about testing? Me: Maybe the testers need help too.
: I'm somewhat concerned that @GojkoAdzic is referring to tests as something you write, rather than testing as something you do.
@lisacrispin: Writing tests after development doesn’t make any sense. You catch problems just by writing tests. @gojkoadzic
: Change the way you capture tests so other people can give feedback on what you are testing & what is missed. #readable @gojkoadzic
@lisacrispin: @michaelbolton I think @gojkoadzic is talking abt tests that tell us what to code, as opposed to the testing we do after coding
: To deliver software faster, we need to make quality everybody's problem, not just the testers. @gojkoadzic
: Me: Specification by example is a fine thing to do. Let's make sure that we see that as /only one/ testing approach. @GojkoAdzic
: I wish @GojkoAdzic would be specific about what he means by "test automation". I think he means "checked examples".
@lisacrispin: Quality is at the intersection of everyone's problems. http://yfrog.com/gzjsyscj @gojkoadzic
: Me: There are many, many aspects of test automation. To me, it's /any use of tools to support #testing/. @GojkoAdzic
@lisacrispin: I think @gojkoadzic means "Specification by example", but it's a good pt, we need consistent terminology
@lisacrispin: When everyone thinks about quality, and devs do the automation, automation won’t fall behind. @gojkoadzic frees time 4 exp. Testing
@gojkoadzic keynote presentation at #stareast He presents much like I do. Topic is relevant. Needs more concrete examples.Loving
@lisacrispin: When programmers automate the tests, there is time for testers to do more imp. stuff http://yfrog.com/gzuy7szj @gojkoadzic
: When programmers own automation, testers: advise what needs to be tested, critical manual test, other important stuff @gojkoadzic
: Me: Everyone *already* cares about quality. A more serious problem: they care about their own notion of quality. @GojkoAdzic
@lisacrispin: Examples from Sabre, other co's on how having everyone own quality built trust, solved automation pblms @gojkoadzic
: @GojkoAdzic suggests more pairing as way of changing the culture, increasing level of trust. I agree.
: Through collaboration/pairing, you dramatically increase level of trust, which will change the culture. @gojkoadzic
@lisacrispin: @gojkoadzic told story of when a good tester took over testing work from pgmrs, they lost quality culture
: As long as you have "tester" or "qa" titles, others less likely to own quality. Change titles. @gojkoadzic I agree it can help.
: Good stuff from @GojkoAdzic: emphasize in order 1) making sure right work gets done; 2) teaching others to do it; 3) doing it.
@lisacrispin: If you do everything urself nobody else knows how to do it. So do this. http://yfrog.com/gzq3egpj @gojkoadzic
: Testers: Focus on ensuring the right testing gets done, not just doing all the testing. @gojkoadzic
@lisacrispin: Change the name so testers are ppl who ensure the right testing gets done, not ppl who do all the testing. @gojkoadzic
: Look for @gojkoadzic books, specification by Example, and Bridging the Communication Gap, for more info & case studies.
: Many good cultural re-framing ideas from @gojkoadzic
: I've been coaching on most of what @gojkoadzic suggests for years. Awesome! Collaborate, break roles, whole team quality focus.
: Me: A language question: why do we need to make quality everyone's /problem/, rather than everyone's /joyful task/? @GojkoAdzic
Gojko says automation should be a small part of the work. Buwalda says 5% is max on automation (in stable situation)
: @GojkoAdzic doesn't give "an answer" to a questioner's problem, but *offers examples & suggestions that might help*. #Credibility
@lisacrispin: I highly recommend @gojkoadzic's new Specification by Example book. Real life case studies show - you CAN do this.
n : *Measurement* is the art and science of making reliable observations, says @jerryweinberg, and I agree.
More to follow as the conference progresses