Marc Firestone Life Insurance: 7 Sports That Make Getting Life Insurance Hard (or impossible!)
Manual Testing in Scrum is Hard (But Not Impossible)
-
Upload
lesley-wallace-csm-sa -
Category
Software
-
view
436 -
download
1
Transcript of Manual Testing in Scrum is Hard (But Not Impossible)
Lesley’s Q&A for you
• How many are developing software using Scrum?
• How much testing automation is being used?
• Do you find it difficult to test within a Sprint?
Automation is the best way to solve this!
Who is responsible for Quality?
A) QA Team MemberB) DevelopersC) Business AnalystsD) Product OwnerE) All of the above
“Everyone in the team is responsible for building in quality. . . ANYONE can be a tester, and everyone should create tests.“ –Lesley Wallace
Challenge:So how do we manually test within a two week Sprint? Won’t it just wind up mini-waterfall?
Mini-waterfall
Scrummerfall
Wagile
BAD!Not Agile!
Totally UNFAIR!
How are your User Stories broken down?
How many stories are you accepting into a sprint?
Do they take more than 2 days to code?
Evaluate Your Stories
How do you write your Acceptance Criteria (AC) or Conditions of Satisfaction for a story?
Is whoever’s testing involved in their creation?
AC as the “expected result” of tests
Acceptance Criteria: A Better Way to Define Testing Needs
Team decides on scope
Tester only focuses on the story (no exploring!)
Limits Documentation
AC as the “expected result”
Challenge:But what about Regression? It’s not possible within a Sprint!
Add a Hardening Sprint!
Are you comfortable that the application will work when all stories are pushed to production?
Do you have a bit more time before a release is expected?
Challenge:But we don’t have time for this “Hardening Sprint” business!
Modified Regression at the last Sprint
Where do you experience the most traffic?
What are the most critical features to keep your business in business?
Manual testing within a sprint is hard, but not impossible.
Final Thoughts…
• Decrease scope of each story
• Commit to testing only within scope
• Everyone should be involved in testing
Add automation whenever you can. It helps. And there are tools out there for all needs & budgets, so give one a try!