We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byKaterina Elks
Modified about 1 year ago
© 2012 Scott W. Ambler Agile Testing Survey 2012 November 2012 Scott W. Ambler
© 2012 Scott W. Ambler How To Use These Slides I have provided these slides, and the raw data behind them, so that others can use them in their own work. You may reuse all, or a part of, this slide deck as long as you provide a clear reference to the source. The suggested reference is: Results from Scott Ambler’s 2012 Agile Testing Survey posted at Some slides have notes
© 2012 Scott W. Ambler About the Survey Mid October to mid November 2012 Survey link included in: –www.ambysoft.com/surveys/ pagewww.ambysoft.com/surveys/ –Tweet –Posting to the Disciplined Agile Delivery discussion forum on LinkedIn –Tweets to attendees of Agile Testing Days 2012 in Potsdam (Nov 2012) Data, summary, and slides downloadable from respondents –26% were developers or modelers, 29% were agile coaches/mentors, 22% were testers –67% had 2+ years of agile experience, 24% 5+ years –37% worked in orgs of 500+ people –20% North American, 69% European, 7% Asia Pacific Goal of the survey was to discover what approaches to testing agile teams were taking.
Agile Practice Adoption © 2012 Scott W. Ambler
Testing Strategies on Agile Teams 71% report that most or all of their developers test their own code 80% report that testers work very closely with programmers to test throughout the project 48% report that team members pair on a regular basis 41% have an independent test team working in parallel to our development team 30% have an independent test team that will be testing at the end of the lifecycle 29% hold formal reviews of code or other artifacts throughout development 68% hold informal reviews of code or other artifacts throughout development © 2012 Scott W. Ambler
Primary Approach to Acceptance Testing © 2012 Scott W. Ambler
Primary Approach to Developer Testing © 2012 Scott W. Ambler
Challenges Adopting Agile Testing Approaches Question: What has your team found to be the most difficult challenges when adopting agile testing approaches? Choose up to three. 50%Getting all testing done in the current iteration/sprint 37%Adopting test-driven approaches 33%Validating non-functional requirements 33%Getting stakeholders/customers involved with testing 27%Getting developers to test their own code 21%User interface testing 16%Learning to test throughout the lifecycle 13%Adopting new agile testing tools 12%Migrating existing testing and quality professionals to agile 8%Using our existing testing tools to support agile development 8%Remaining regulatory compliant © 2012 Scott W. Ambler
About SA+A Scott Ambler + Associates (SAA) is a boutique consulting firm that specializes in helping organizations adopt disciplined agile strategies, particularly at scale. We offer training, coaching, and transformation services. Our website is We can help.www.ScottAmbler.com © 2012 Scott W. Ambler
® IBM Software Group © 2006 IBM Corporation Agility in the Database: Data Doesnt Have to be a Four-Letter Word Any More Scott W. Ambler Practice Leader.
Of. and a to the in is you that it at be.
The. of and a to in is you that it he was.
ASWEC 2008Slide 1 Construction by Configuration: An opportunity for SE research Prof. Ian Sommerville St Andrews University Scotland.
Unified process(UP) UP is an OO system development methodology offered by Rational(Rational Rose) s/w, now a part of IBM Developed by Booach,Rambaugh,Jacobson--
High Frequency Words List A Group 1. the of and.
Agile and Open Development Neil Chue Hong, OMII-UK Ross Gardler, OSS-Watch JISC e-Infrastructure Programme Meeting Birmingham, 7 Feb 2008.
The. of and a to in is you that it he for.
1 st 5 minutes: Fill out Exercise #13 Write your team answers to #1 & 2 on your flip chart.
1 Note content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. Rapid Software Development IS301.
Jit Udset/Outcomes/Talking Points The Orkney Partnership: Outcomes Focused Reviews Our Experience.
Launching the common approach to regulatory competency.
Writing Effective Scenarios and Use Cases. Timetable Introductions Strategies for gathering requirements refreshments Creating.
CLIENT SERVICE, IT(IL) BEST PRACTICES & REQUEST TRACKER ON A FEDERATED IT CAMPUS CLICK CLICK
Marketing Strategies for the Use of HINARI (module 6.1)
USAGE AND PERCEPTIONS OF AGILE SOFTWARE DEVELOPMENT IN AN INDUSTRIAL CONTEXT Andrew Begel, Nachiappan Nagappan Microsoft Research ESEM 2007 September 21,
Brian Browning | Senior Director of Client Services Jason Arden | Director of Partner Engineering.
Objective Performance Appraisal has two objectives To help those appraised develop and improve their performance in future To help the organization evaluate.
Lecture 6 Conceptual Design Brainstorming Card sort Semantic networks Personas Scenarios, flowcharts and cognitive walkthroughs Both of these are excellent.
Learning outcomes: PwCs perspective Konica Stones Manager – Student Recruitment
Patient participation DES ‘How to’ workshop for practice managers By Kerry Naylor, Head of patient experience.
CENTRAL BAPTIST ASSOCIATION A Strategy for Mission…..Reviewed.
Best Practices for Implementing An Information Solution By Even Brande.
1 Science Subject Leader Training Preparing new and aspiring Subject Leaders for the role. East Riding/North Yorkshire LAs.
Why are you here? You are considered to be a core stakeholder in the changes taking place to our systems. To some extent you will be affected by this.
ADASS Spring Seminar Update Jeff Jerome National Director Social Care Transformation.
Lecture 2 1 Introduction to Software Engineering.
This presentation, including any supporting materials, is owned by Gartner, Inc. and/or its affiliates and is for the sole use of the intended Gartner.
© 2016 SlidePlayer.com Inc. All rights reserved.