Your SlideShare is downloading. ×
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Quality in an_agile_world
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Quality in an_agile_world

339

Published on

Software quality and testing for an agile and mobile world.

Software quality and testing for an agile and mobile world.

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

No Downloads
Views
Total Views
339
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Quality in an Agile worldrethinking tools, processes, and teamsPresented by Jason ArbonJune 19, 2012
  • 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. Agile is the answerScary signals• speed• mobile• appification + fragmentation
  • 4. Agile SpeedScary: • No full test passes • Less upfront design and planningHappy:• Rollback• Fewer changes per build• Quick feedback
  • 5. Agile Speed
  • 6. Agile Speed
  • 7. Mobile• Undeniable• Dont miss this wave..
  • 8. Appification + FragmentationScary: • Distribution • User Voice• MatrixHappy: • User Voice • Data • Quality is quantified
  • 9. Fragmentation
  • 10. Fragmentation
  • 11. Appification + FragmentationFeedback from early adopters, dogfooders, crowd testers..Enable feedback everywhere. its easy!
  • 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. 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. 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. 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. 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. Agile, Continuous Testing at Scale
  • 18. Truly Agile Tools and PracticesBug Reporting:• No more bug forms with Repro, Results, Expected!• Capture all the environment + state data automagically
  • 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. 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. Next gen continuous testing workflow
  • 22. Final words• World is getting scarrier and changing underneath us• Agile used to be cool• ...now it is necessary
  • 23. evolve quickly
  • 24. contact jasona@utest.comQuality in an Agile World

×