AgileTesting

RT @g33klady: Get QA involved as far upstream add possible, when designs are created #StarWest #agiletesting

— Sharon Robson (@SMRobson)2013-10-02 20:23:31

RT @g33klady: Get QA involved as far upstream add possible, when designs are created #StarWest #agiletesting

— Elizabeth Zagroba (@ezagroba)2013-10-02 19:26:39

RT @g33klady: Get QA involved as far upstream add possible, when designs are created #StarWest #agiletesting

— Claire Moss (@aclairefication)2013-10-02 18:42:18

Dev and qa pair testing! It's awesome and builds rapport between us dudes! #agiletesting #StarWest

— Hilary aka H-Bomb (@g33klady)2013-10-02 18:36:36

RT @g33klady: Get QA involved as far upstream add possible, when designs are created #StarWest #agiletesting

— mindfulcoder (@MindfulCoder)2013-10-02 18:34:38

Maybe write test cases with the devs as a way to review stories? #StarWest #agiletesting

— Hilary aka H-Bomb (@g33klady)2013-10-02 18:34:20

RT @g33klady: Get QA involved as far upstream add possible, when designs are created #StarWest #agiletesting

— Michael Larsen (@mkltesthead)2013-10-02 18:30:19

When stories are estimated it must include testing. And buffers fit bug fixing and retesting #agiletesting #StarWest

— Hilary aka H-Bomb (@g33klady)2013-10-02 18:29:18

User story augmentation - acceptance criteria and pictures or wireframes. Before the iteration begins #StarWest #agiletesting

— Hilary aka H-Bomb (@g33klady)2013-10-02 18:28:04

Before iteration begins have user stories defined - it's a placeholder for a conversation. #agiletesting #StarWest

— Hilary aka H-Bomb (@g33klady)2013-10-02 18:26:29