Successfully reported this slideshow.
Your SlideShare is downloading. ×

No Time for Testing: Strategies to Keep Testing Inside Your Sprints

Ad

Presented by:
Lesley Wallace,
CSP, CSM, SA

Ad

Dilbert on Testing…

Ad

HELLO
My name is
Lesley Wallace
o Nit-picky tester since 2004
• Web and Software testing (Manual &
Automated)
• Automation...

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Upcoming SlideShare
Intro to DevOps
Intro to DevOps
Loading in …3
×

Check these out next

1 of 23 Ad
1 of 23 Ad

No Time for Testing: Strategies to Keep Testing Inside Your Sprints

Download to read offline

Learn how to navigate organizational culture to change views toward Quality and Scrum
Testing as part of a Scrum team (Everyone owns quality!)
Ways to "write tests" without breaking the time-bank
Set yourself up for success, even without automation
(Automation is awesome, and you should use it if you have it, but it's not 100% required to succeed at Scrum.)

Learn how to navigate organizational culture to change views toward Quality and Scrum
Testing as part of a Scrum team (Everyone owns quality!)
Ways to "write tests" without breaking the time-bank
Set yourself up for success, even without automation
(Automation is awesome, and you should use it if you have it, but it's not 100% required to succeed at Scrum.)

Advertisement
Advertisement

More Related Content

Similar to No Time for Testing: Strategies to Keep Testing Inside Your Sprints (20)

Advertisement

No Time for Testing: Strategies to Keep Testing Inside Your Sprints

  1. 1. Presented by: Lesley Wallace, CSP, CSM, SA
  2. 2. Dilbert on Testing…
  3. 3. HELLO My name is Lesley Wallace o Nit-picky tester since 2004 • Web and Software testing (Manual & Automated) • Automation tools: HP QTP/UFT, TestComplete, Selenium, AutoIt/Watir o Agile since 2013 o Scrum Master since 2014 o Certifications: CSP, CSM, SA, CSPO
  4. 4. How many are developing software using Scrum? How much test automation is being used? Do you find it difficult to test within a sprint?
  5. 5. From “101 Inspiring Quotes about Agile” - Front Row Agile
  6. 6. And More…
  7. 7. Who is responsible for Quality? A) QA Team Members B) Developers C) Business Analysts D) Product Owner E) All of the above Everyone in the team is responsible for building in quality. ANYONE can be a tester, and everyone should create tests.
  8. 8. Challenge: How can we change this? QA cannot be part of a Scrum team because automation doesn’t exist. A company’s culture dictates:
  9. 9. Elevate Organization’s Agile Maturity 01 Identify your person 02 Dedicate team members 100% 03 Discover the “why” behind documentation 04 Stop using “# of bugs” as a metric 05 Drive the culture that EVERYONE owns quality
  10. 10. – Larry Apke, Agilist and Technology Executive Identify Your “Person”
  11. 11. Focused on the Team’s success Higher productivity, no competing priorities, teamwork, shared vision Measurable Growth Consistent velocity, time to learn new technology Dedicate more than 50% If 100% isn’t possible, don’t split 50/50
  12. 12. Don’t accept “It’s always been this way.” Keep asking “Why?” until there’s a reason. If no reason, “Why not try something else?” Seek out the minimum necessary SOX? PCI? What do they really need to be happy? Look for easy ways to satisfy documentation needs Screenshots, automated notifications, tool access
  13. 13. Sprint 1 Sprint 2 Sprint 3 Sprint 4 #ofBugs Stop Using “# of Bugs” as a Metric Defect Management Changes Missed requirement, conversations Bugs should be hard to find Quality practices = less defects intrasprint Measure issues post-release Team accountability
  14. 14. How do we manually test within a two week Sprint? Won’t it just wind up mini- waterfall? Challenge:
  15. 15. Let Your Stories be Your Guide 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?
  16. 16. Are Testers involved in AC creation? Do Testers use AC as their “expected result”? How do you write your Acceptance Criteria (AC)? Let Your Stories be Your Guide
  17. 17. 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:
  18. 18. Splitting modules is risky Keep integration paths intact for Regression testing User Acceptance Testing Hands on in prod-like environment All additional tests go here Penetration, security, performance; any extra tests not covered in team’s DoD
  19. 19. HARDENING IS NOT A SAFETY NET FOR MISSED TESTS!
  20. 20. 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? Challenge:
  21. 21. Manual testing within a sprint is hard, but not impossible. Add automation whenever you can. It helps. And there are tools out there for all needs & budgets, so give one a try! 01 Make changing organizational culture a priority 02 Decrease the scope of each story 03 Commit to coding and testing based on Acceptance Criteria 04 “Everyone owns quality” should be ingrained in teams
  22. 22. Questions? Comments? @AgileLesley lesley.wallace@slalom.com https://www.linkedin.com/in/AgileLesley

×