#AT16VIE: Does Agile mean we have no time for testing?

51

Transcript of #AT16VIE: Does Agile mean we have no time for testing?

Page 1: #AT16VIE: Does Agile mean we have no time for testing?
Page 2: #AT16VIE: Does Agile mean we have no time for testing?
Page 3: #AT16VIE: Does Agile mean we have no time for testing?
Page 4: #AT16VIE: Does Agile mean we have no time for testing?
Page 5: #AT16VIE: Does Agile mean we have no time for testing?
Page 6: #AT16VIE: Does Agile mean we have no time for testing?
Page 7: #AT16VIE: Does Agile mean we have no time for testing?
Page 8: #AT16VIE: Does Agile mean we have no time for testing?
Page 9: #AT16VIE: Does Agile mean we have no time for testing?
Page 10: #AT16VIE: Does Agile mean we have no time for testing?
Page 11: #AT16VIE: Does Agile mean we have no time for testing?
Page 12: #AT16VIE: Does Agile mean we have no time for testing?
Page 13: #AT16VIE: Does Agile mean we have no time for testing?
Page 14: #AT16VIE: Does Agile mean we have no time for testing?
Page 15: #AT16VIE: Does Agile mean we have no time for testing?

Smoke Test + Dashboard

Page 16: #AT16VIE: Does Agile mean we have no time for testing?
Page 17: #AT16VIE: Does Agile mean we have no time for testing?
Page 18: #AT16VIE: Does Agile mean we have no time for testing?
Page 19: #AT16VIE: Does Agile mean we have no time for testing?
Page 20: #AT16VIE: Does Agile mean we have no time for testing?
Page 21: #AT16VIE: Does Agile mean we have no time for testing?
Page 22: #AT16VIE: Does Agile mean we have no time for testing?
Page 23: #AT16VIE: Does Agile mean we have no time for testing?
Page 24: #AT16VIE: Does Agile mean we have no time for testing?
Page 25: #AT16VIE: Does Agile mean we have no time for testing?

Alex Schwartz

Source: Lisa Crispin & Janet GregoryAgile Testing: A Practical Guide for Testers and Agile Teams

.

Ingedients - Test Categorization / Taxonomy

Sonntag, 10. Oktober 2010 KW

Page 26: #AT16VIE: Does Agile mean we have no time for testing?

Alex Schwartz

Recipe: The “Tetris Principle” - Test as low as possible

Story: As a customer I can contact the seller of an interesting ad.

Risk/aspect 1Mail is not sentdue to config

problems

Risk/aspectLayout of mail

is crap

Risk/aspect:Wrong maillanguage

Risk/aspect:Javascript problem

in contact form

no automated tests

automated tests

Story Test / UI(Integration)

Manual tests

Story testbelow UI

Story Test / UI(Browser)

Sonntag, 10. Oktober 2010 KW

Page 27: #AT16VIE: Does Agile mean we have no time for testing?
Page 28: #AT16VIE: Does Agile mean we have no time for testing?
Page 29: #AT16VIE: Does Agile mean we have no time for testing?
Page 30: #AT16VIE: Does Agile mean we have no time for testing?
Page 31: #AT16VIE: Does Agile mean we have no time for testing?
Page 32: #AT16VIE: Does Agile mean we have no time for testing?
Page 33: #AT16VIE: Does Agile mean we have no time for testing?
Page 34: #AT16VIE: Does Agile mean we have no time for testing?
Page 35: #AT16VIE: Does Agile mean we have no time for testing?
Page 36: #AT16VIE: Does Agile mean we have no time for testing?
Page 37: #AT16VIE: Does Agile mean we have no time for testing?
Page 38: #AT16VIE: Does Agile mean we have no time for testing?
Page 39: #AT16VIE: Does Agile mean we have no time for testing?

Mein Erfahrung

...

100%

DevOps-Team “Places” bei

Verbesserungen

Fire Fighting

Deployment / Liefern

10 Monate 20 Monate

(mit Cloud)

...

Page 40: #AT16VIE: Does Agile mean we have no time for testing?
Page 41: #AT16VIE: Does Agile mean we have no time for testing?
Page 42: #AT16VIE: Does Agile mean we have no time for testing?
Page 43: #AT16VIE: Does Agile mean we have no time for testing?

Alex Schwartz

Principle: Visibility

www.flickr.com/photos/shannonsturgis/4274202367Sonntag, 10. Oktober 2010 KW

Page 44: #AT16VIE: Does Agile mean we have no time for testing?

Alex Schwartz www.flickr.com/photos/28549294@N05/4273275734

Analogy #1: The Definition of Done (DoD) in a Kitchen

Assume a professional cook in a restaurant kitchen is asked to create a nice meal for a customer.

When it’s DONE?

NO

Sonntag, 10. Oktober 2010 KW

Page 45: #AT16VIE: Does Agile mean we have no time for testing?

Alex Schwartz

Goal: A happy kitchen crew

www.flickr.com/photos/fractalv/1341923133Sonntag, 10. Oktober 2010 KW

Page 46: #AT16VIE: Does Agile mean we have no time for testing?
Page 47: #AT16VIE: Does Agile mean we have no time for testing?

Vorteile von schnellen Feedback

Zeit (MTTR)

Kosten

Kosten Fehler zu korrigieren steigen exponentiell (plus in Stufen)

● Auswirkungen eines Fehlers über die Zeit wächst ebenfall schneller als linear

● Nehmen wir an ein Team ist doppelt so langsam Fehler zu beheben (MTTR):○ doppelter Personalbedarf○ oder doppelt so viele Fehler

zu spät und zu teuer

schnell behoben

Stun

den

Mon

ate

Tage

Woc

hen

Page 48: #AT16VIE: Does Agile mean we have no time for testing?

Vorteile von schnellen Feedback

Zeit (MTTR)

Kosten

Kosten Fehler zu korrigieren steigen exponentiell (plus in Stufen)

● Auswirkungen eines Fehlers über die Zeit wächst ebenfall schneller als linear

● Nehmen wir an ein Team ist doppelt so langsam Fehler zu beheben (MTTR):○ doppelter Personalbedarf○ oder doppelt so viele Fehler

zu spät und zu teuer

schnell behoben

Stun

den

Mon

ate

Tage

Woc

hen

gray team has half of the bug backlog of the blue team

team “blue”

team “gray”

Page 49: #AT16VIE: Does Agile mean we have no time for testing?
Page 50: #AT16VIE: Does Agile mean we have no time for testing?
Page 51: #AT16VIE: Does Agile mean we have no time for testing?