Quality in an_agile_world


Published on

Software quality and testing for an agile and mobile world.

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Quality in an_agile_world

  1. 1. Quality in an Agile worldrethinking tools, processes, and teamsPresented by Jason ArbonJune 19, 2012
  2. 2. context on me• co-author of "How Google Tests Software"• uTest.com: o Engineering Director• Google: o Chrome Browser, Chrome OS o Google+ (Search)• Social Search Startup• Microsoft: o Bing, BizTalk, WindowsCE o ...and WinFS :)
  3. 3. Agile is the answerScary signals• speed• mobile• appification + fragmentation
  4. 4. Agile SpeedScary: • No full test passes • Less upfront design and planningHappy:• Rollback• Fewer changes per build• Quick feedback
  5. 5. Agile Speed
  6. 6. Agile Speed
  7. 7. Mobile• Undeniable• Dont miss this wave..
  8. 8. Appification + FragmentationScary: • Distribution • User Voice• MatrixHappy: • User Voice • Data • Quality is quantified
  9. 9. Fragmentation
  10. 10. Fragmentation
  11. 11. Appification + FragmentationFeedback from early adopters, dogfooders, crowd testers..Enable feedback everywhere. its easy!
  12. 12. Appification + Fragmentationleverage the crowd • They have the device matrix • They are the end users• Spin up and down like AMZN• No mangment 1:1s :)
  13. 13. Truly Agile Tools and Practices• Only the quick will survive• Beware if you think your software is too critical or complicated to adopt agile. Your software and practices might actually be too complicated to compete.
  14. 14. Truly Agile Tools and PracticesPlanning:• Stop planning.• If you have milestones that go out 30+ days, you arent agile and not responding to feedback and the market"There is no need for a spreadsheet, database, or filing system. Therequests that really matter are the ones you will hear over and overagain ... your customers will be your memory ... If there is a request thatyou keep forgetting, thats a sign that it isn’t very important. The reallyimportant stuff doesnt go away."--Jason Fried, David Heinemeier Hansson, Rework,37Signals
  15. 15. Truly Agile Tools and PracticesTest Plans: • Stop. No more documents • Risk-based • Continuous testing on whatever is the most risky • Dont worry so much! • Cut or hide red areasAppification + Fragmentation
  16. 16. Truly Agile Tools and PracticesRegression Testing:• Have lots of Unit+ test automation• Delete as many as you can bear• Low ROI...they usually pass :)• Crowd and dogfooders find your bugs (calendar ex) o Instrument your builds o Feedback channelsAppification + Fragmentation
  17. 17. Agile, Continuous Testing at Scale
  18. 18. Truly Agile Tools and PracticesBug Reporting:• No more bug forms with Repro, Results, Expected!• Capture all the environment + state data automagically
  19. 19. Truly Agile Tools and PracticesTestcase and Textual Bug databases: • If you have them, you are still transitioning to Agile • Exploratory testing • Bugs should be fixed immediately
  20. 20. Truly Agile Tools and PracticesTeam Structure and Process: • Engineers own quality • Daily standups and recurring meetings should be banned. Just a sign that the team is too large or doesnt collaborate well. • re-Architect for smaller and agile teams. Services structure (GOOG + AMZN).
  21. 21. Next gen continuous testing workflow
  22. 22. Final words• World is getting scarrier and changing underneath us• Agile used to be cool• ...now it is necessary
  23. 23. evolve quickly
  24. 24. contact jasona@utest.comQuality in an Agile World