Agile Sutra "Do more by doing less, Prevent rather than detect"

1,936 views

Published on

STAG Software presented a webinar on Mar 14, 2013 on the topic - Agile Sutra "Do more by doing less, Prevent rather than detect". The webinar was hosted by T Ashok, Founder & CEO, STAG Software and Architect of HBT.

The webinar outlines how HBT (Hypothesis Based Testing) can enable you to "do more by doing less" via enhanced defect prevention ability rather than find more.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,936
On SlideShare
0
From Embeds
0
Number of Embeds
393
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Agile Sutra "Do more by doing less, Prevent rather than detect"

  1. 1. Agile Sutra "Do more by doing less, Prevent rather than detect"T AshokFounder & CEOSTAG Software Private Limited in.linkedin.com/in/AshokSTAG ash_thiru
  2. 2. Sutra An user story is like a "sutra" - an aphorism, that needs to be delved into detail to understand its entirety. And this is needed if you want to test well.© 2013 STAG Software Private Limited. All rights reserved. 2
  3. 3. The Details of “How-To” ... the act of breaking the "big" into "small" (user stories) makes one forget about who the end user is and what they value. BIG Picture & Goal Setting Hence it is necessary to think from the end users perspective as what they do and how the user story fits in the end user flow and how non-functional attributes of the larger flow matter to the user story.© 2013 STAG Software Private Limited. All rights reserved. 3
  4. 4. To Do Less - “Stay Focussed” Identify Cleanliness Criteria END USER What EXPECTATIONS will impede this? CLEAN Potential Defect User Story Types Extract What BEHAVIOUR to look for? CONDITIONS Test Cases© 2013 STAG Software Private Limited. All rights reserved. 4
  5. 5. Delivering a “Clean” User Story Focus on “Clarity” BIG PICTURE & EVALUATING ASSESSMENT GOAL SETTING Clarity in doing Clarity of outcome Clarity of purpose What do the users What tests need to be done? expect of the story and How clean is it? What are the scenarios/cases? of the system? What-to-Test & Testing Effectively & Objective assessment Test-for-What Efficiently of cleanliness© 2013 STAG Software Private Limited. All rights reserved. 5
  6. 6. Delivering a “Clean” User Story How to ? Application of HBT} } BIG PICTURE & Potential Cleanliness 1 GOAL SETTING Defect Criteria Clarity of purpose Types UNDERSTAND. Question. Identify situations. PREVENT. Do More. Do Less. EVALUATING Quality Test 2 Test Types Clarity in doing Levels Scenarios Strategy Design ASSESSMENT Execute Assess 3 Clarity of outcome Execution & Analysis© 2013 STAG Software Private Limited. All rights reserved. 6
  7. 7. The Details of “How-To” What is the BIG Picture?© 2013 STAG Software Private Limited. All rights reserved. 7
  8. 8. The Details of “How-To” What is the BIG Picture? ( Contd...)© 2013 STAG Software Private Limited. All rights reserved. 8
  9. 9. The Details of “How-To” Goal Setting: End User Expectations Properties© 2013 STAG Software Private Limited. All rights reserved. 9
  10. 10. The Details of “How-To” Business Goal -End User Expectations - Cleanliness Criteria© 2013 STAG Software Private Limited. All rights reserved. 10
  11. 11. The Details of “How-To” Technical Goal - Potential Defect Type(PDT) / Test Type© 2013 STAG Software Private Limited. All rights reserved. 11
  12. 12. HBT Quality Levels, Cleanliness Criteria- Test Types User Story Combinations of User stories Use cases© 2013 STAG Software Private Limited. All rights reserved. 12
  13. 13. HBT Overview SIX staged purposeful activities, powered by EIGHT disciplines of thinking SIX Stages of DOING S1 S1: Understand expectations S6 S2: Understand context S3: Formulate hypothesis D1 S4: Devise proof S5: Tooling support D8 D2 S6: Assess & Analyse EIGHT Disciplines of Thinking D1: Business value understanding S5 D7 Core Concepts D3 S2 D2: Defect hypothesis D3: Strategy & Planning D4: Test design D5: Tooling D6 D5 D6:Visibility D7: Execution & Reporting D4 D8: Analysis & Management Uses 32 Core Concepts S4 S3 For Problem solving - Techniques, Principles, Guideline Click here to know more about HBT. http://stagsoftware.com/blog?p=570© 2013 STAG Software Private Limited. All rights reserved. 13
  14. 14. Outcomes Increased awareness of feature Testers &Developers know in depth about the feature during discussions Increased TC (20x), focus on details & improved implementation clarity Significant coverage increase Initially test cases focused only functional aspects, expanded to cover non-functional aspects. Sensitise & Prevent HBT highlights potential defects to the developer that can be taken care in the earlier stages of development© 2013 STAG Software Private Limited. All rights reserved. 14
  15. 15. "Do more by doing less, Prevent rather than detect" Agile Sutra Connect with us... @stagsoft blog.stagsoftware.com HBT is the intellectual property of STAG Software Private Limited. STEMTM is the trademark of STAG Software Private Limited.© 2013 STAG Software Private Limited. All rights reserved. www.stagsoftware.com

×