//

Agile Testing by Example-driven Development

13.10.2009 | 2 minutes of reading time

Agile Testing Days: The Missing Link for ATDD and Example-driven Development by Gojko Adzic

This posting will be a small experiment using Twitter. As Gojko’s session was one of the most commented ones on Twitter I just distilled this blogpost out of all the corresponding tweets. One nice effect of this is that the re-tweets already show which topics have been seen as the most important ones. So have fun with “Agile Tweeting”!

dwhelan: From Sources of Power: “only 34% of commander expectations are met; yet everyone thought they understood” #agiletd @gojkoadzic

ThomasJaspers: The key question you have to ask more often in sw development: why #agiletd @gojkoadzic

dwhelan: Requirements are often given to us as a solution to an unknown problem. @gojkoadzic #agiletd

dwhelan: We need to ask why when faced with requirements to drive to real business need. @gojkoadzic #agiletd

ThomasJaspers: Challenge requirements especially if they come in the form of a solution @gojkoadzic #agileTD

dwhelan: Challenge requirements right away with senior people and stakeholders in the room – involve whole team @gojkoadzic #agiletd

dwhelan: To get access to senior people that are very busy – schedule regular meetings as appointment in their calendar. @gojkoadzic #agiletd

ThomasJaspers: How can I make this sound too dangerous for a senior stakeholder to miss? Specification Workshops @gojkoadzic #agiletd

emadb: Requirements are often used as a solution to unknown problem #agileTD @gojkoadzic

dwhelan: If you want busy senior people to attend your meeting. Brand it to make it dangerous if they don’t attend @gojkoadzic #agiletd

ThomasJaspers: Distil the specification -focus on what, not on how @gojkoadzic #agiletd

ThomasJaspers: Avoid the telephone game: Build and evolve the ubiquitous language! Translation hurts, build a common lang in the team @gojkoadzic #agiletd

testobsessed: Loving @gojkoadzic’s session at #agiletd. Great stuff.

dwhelan: Clever: “acceptance tests” should be minutes from specification workshops @gojkoadzic #agiletd

ThomasJaspers: thanks for a great session 🙂 @gojkoadzic #agiletd

testobsessed: Nice distinction from @gojkoadzic: stories are the scope; acceptance tests are the specification. #agiletd

pekkaklarck: One of the highlights of the conference! RT @testobsessed: Loving @gojkoadzic’s session at #agiletd. Great stuff.

ehsavoie: RT @testobsessed: Nice distinction from @gojkoadzic: stories are the scope; acceptance tests are the specification. #agiletd

rainbowbreeze: Requirements are often used as a solution to unknown problem #agileTD (RT @emadb @gojkoadzic)

ohnlockhart: RT @testobsessed: Nice distinction from @gojkoadzic: stories are the scope; acceptance tests are the specification. #agiletd

baloss: Requirements are often used as a solution to unknown problem #agileTD (RT @emadb @gojkoadzic) (via @rainbowbreeze)

share post

Likes

0

//

More articles in this subject area\n

Discover exciting further topics and let the codecentric world inspire you.

//

Gemeinsam bessere Projekte umsetzen

Wir helfen Deinem Unternehmen

Du stehst vor einer großen IT-Herausforderung? Wir sorgen für eine maßgeschneiderte Unterstützung. Informiere dich jetzt.

Hilf uns, noch besser zu werden.

Wir sind immer auf der Suche nach neuen Talenten. Auch für dich ist die passende Stelle dabei.