Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.

Slides:



Advertisements
Similar presentations
© 2007 BigVisible Solutions, Inc. All Rights Reserved Coaching Solutions Agile Project Start v
Advertisements

Professional Services Developer Program Services
Testing and Quality Assurance
Local Touch – Global Reach The New Tester Matthew Eakin, Manager Managed Testing Practice Sogeti, USA.
Alternate Software Development Methodologies
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall B.1.
Agile development By Sam Chamberlain. First a bit of history..
Fundamentals of Information Systems, Second Edition
COMP 350: Object Oriented Analysis and Design Lecture 2
1.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
High Level: Generic Test Process (from chapter 6 of your text and earlier lesson) Test Planning & Preparation Test Execution Goals met? Analysis & Follow-up.
Managing a Project Using an Agile Approach and the PMBOK® Guide
Copyright © 2014 ASTQB Presented by Rex Black, CTAL Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further.
Software Engineering Lecture No:12. Lecture # 7
Gaining Support for a Sustainable Agile Transformation Dennis Stevens, VP Enterprise Engagements LeadingAgile November 12, 2013.
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 3: Phase Management - Inception.
1 Software Testing (Part-II) Lecture Software Testing Software Testing is the process of finding the bugs in a software. It helps in Verifying and.
Current Trends in Systems Develpment
Rational Unified Process Fundamentals Module 4: Disciplines II.
Business Systems Development SDLC and introduction to the Microsoft Solutions Framework Team and Process Models.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Testing Challenges in an Agile Environment Biraj Nakarja Sogeti UK 28 th October 2009.
ASTQB Mobile Tester Certification Now available!.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
APMG-International Webinar Integrating Agile into PRINCE2® Thursday 19 December 2013 / 13:00 GMT Presented by Melanie Franklin,
Delivery Method: Online Duration: 180 Days Scrum Developer Certified (SDC™)  Participants will become familiar with the concepts, advantages, and challenges.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Applied Software Project Management SOFTWARE TESTING Applied Software Project Management 1.
AGILE METHODS Curtis Cook CS 569 Spring 2003.
CS223: Software Engineering
Agile Methods SENG 301.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
CLE Introduction to Agile Software Acquisition
Software Quality Control and Quality Assurance: Introduction
Scrum.
Appendix B Agile Methodologies
Fundamentals of Information Systems, Sixth Edition
School of Business Administration
Agile Training – Agile Overview
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
The Systems Engineering Context
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
TechStambha PMP Certification Training
Unified Process Source & Courtesy: Jing Zou.
Information Technology Project Management – Fifth Edition
ISTQB Foundation Let’s Get Started!.
Microsoft Exam Dumps Questions & Verified Answer - Dumps4downlod.in
E2E Testing in Agile – A Necessary Evil
Quality Strategies In AGILE
COMP 350: Object Oriented Analysis and Design Lecture 2
Advantages OF BDD Testing
Project Management and the Agile Manifesto
Johanna Rothman Create Technical Excellence Chapter 9
What do you need to know about XP?
Johanna Rothman Agile Team Measurements Chapter 12
Summarizing Our Models to Date
Introduction If you have got a call for an Agile testing interview, then congratulations are in order. You may be feeling nervous, but it sure to be felt.
Course: Module: Lesson # & Name Instructional Material 1 of 32 Lesson Delivery Mode: Lesson Duration: Document Name: 1. Professional Diploma in ERP Systems.
Practical Software Engineering
Project Management Chapter 11.
Software Testing Lifecycle Practice
Software Development In Agile
How to deal with requirements in an Agile context?
IREB Foundation Level Agenda: About Me About CodeSpace About IREB
Scrum in Action.
Adapting Agile in Pharmaceutical Industries
Chapter 5: New and Emerging Process Methodologies
Presentation transcript:

Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1

Introduction The ISTQB has always recognized different software development lifecycles in syllabi Sequential, incremental, and agile Foundation, Advanced, and Expert The new syllabus extends the Foundation Two-day focus on testing in agile projects Syllabus written in 2013 Draws on established testing and agile best practices Let’s look at learning objectives, content, sample exam questions, and exam structure… Copyright © 2014 ASTQB 2

Fitting the Extensions in the Program Copyright © 2014 ASTQB 3

The Contribution of Agile Testers Agile testers should: Collaborate in an agile team, being familiar with agile principles and practices Adapt existing testing experience, knowledge, and best practices Support the agile team in planning test related activities Apply relevant test methods and techniques Assist in test automation Help business stakeholders define understandable and testable user stories and acceptance criteria Work and share information with other team members An ISTQB Agile Tester should work effectively within an agile team and environment Copyright © 2014 ASTQB 4

The Content of the Syllabus Agile software development The fundamentals of agile software development Aspects of agile approaches Fundamental agile testing principles, practices, and processes The differences between testing in traditional and agile approaches Status of testing in agile projects Role and skills of a tester in an agile team Agile testing methods, techniques, and tools Agile testing methods Assessing product quality risks and estimating test effort Techniques in agile projects Tools in agile projects Copyright © 2014 ASTQB 5

Understanding LOs and K Levels In the syllabus, you’ll see learning objectives and knowledge levels These indicate what you need to know and the depth of knowledge required for the exam The knowledge levels in the syllabus are: K1: remember, recognize, recall K2: understand, explain, give reasons, compare, classify, summarize K3: apply Copyright © 2014 ASTQB 6

The Exam Structure Forty multiple-choice questions, 65% or more to pass Thirteen questions for Chapter 1 K1 = 5 questions K2 = 7 questions K3 = 1 question Twelve questions for Chapter 2 K1 = 1 question K2 = 11 questions K3 = 0 questions Fifteen questions for Chapter 3 K1 = 4 questions K2 = 4 questions K3 = 7 questions ASTQB has an exam ready now, awaiting release of the syllabus The K-level distribution is more challenging than the CTFL exam Copyright © 2014 ASTQB 7

Learning Objectives of Chapter 1 The fundamentals of agile software development Recall the basic concept of agile based on the Agile Manifesto (K1) Understand the advantages of the whole-team approach (K2) Understand the benefits of early and frequent feedback (K2) Aspects of agile approaches Recall agile software development approaches (K1) Write user stories in collaboration with development, business representative and product owner (K3) Understand how retrospectives can be used as a mechanism for process improvement in agile projects (K2) Understand the use and purpose of continuous integration (K2) Know the differences between iteration and release planning, and how a tester adds value to each of activity (K1) Copyright © 2014 ASTQB 8

Chapter 1 Example Exam Question During an iteration planning meeting, the team members are sharing thoughts about a user story. The product owner says that the customer should have one screen to enter information. The developer explains that there are technical limitations on the feature due to the amount of information captured on the screen. Another developer says that there are performance risks as the information will be stored in an external database. Which of the following would best represent a tester’s contribution to this discussion? The tester suggests a set of testable acceptance criteria for the user story The tester states that usability is more important than performance The tester requests that performance acceptance criteria follow an industry standard The tester advises the group that the screen for the user story should be a single page to reduce test automation effort Copyright © 2014 ASTQB 9

Learning Objectives of Chapter 2 Differences between testing in traditional and agile approaches Describe the differences between testing activities in agile projects and non-agile projects (K2) Describe how coding and testing activities are integrated in agile (K2) Describe the role of independent testing in agile projects (K2) Status of testing in agile projects Describe the basic set of work products used to communicate the status of testing in an agile project, including test progress and product quality (K2) Describe the process of evolving tests across multiple iterations and explain why test automation is important to manage regression risk in agile projects (K2) Role and skills of a tester in an agile team Understand the skills of a tester in an agile team (K2) Understand the role of a tester within an agile team (K2) Copyright © 2014 ASTQB 10

Chapter 2 Example Exam Question Consider the following activities to decide on user acceptance to design, create, and execute appropriate tests to schedule defect reports for analysis to automate and maintain tests to improve program logic by pair programming The role of a tester in an agile team includes: i and iii are correct; ii, iv, and v are incorrect ii and iii are correct; i, iv, and v are incorrect ii and iv are correct; i, iii, and v are incorrect ii and v are correct; i, iii, and iv are incorrect Copyright © 2014 ASTQB 11

Learning Objectives of Chapter 3 (1) Agile testing methods Recall the concepts of test driven development, acceptance test driven development and behavior driven development (K1) Recall the concepts of the test pyramid (K1) Summarize the testing quadrants and their relationships with testing levels and testing types (K2) For a given agile project, practice the role of a tester in Scrum team (K3) Assessing quality risks and estimating test effort Assess product quality risks within an agile project (K3) Estimate testing effort based on iteration content and product quality risks (K3) Copyright © 2014 ASTQB 12

Learning Objectives of Chapter 3 (2) Techniques in agile projects Interpret relevant information to support testing activities (K3) Explain to business stakeholders how to define testable acceptance criteria (K2) Given a user story, write acceptance test driven development test cases (K3) Write test cases, for both functional and non-functional aspects, using black box test design techniques based on given user stories (K3) Execute exploratory testing to support the testing of an agile project (K3) Tools in agile projects Recall different tools available to testers according to their purpose and to the activities in agile projects (K1) Copyright © 2014 ASTQB 13

Chapter 3 Example Exam Question Why is it important to gain insight into the product’s quality risks at the beginning of each iteration in an agile project? Programmers can eliminate the potential impact associated with related failures for each risk The scrum master can mitigate the quality risks prior to the start of programming The level of risk will affect the thoroughness of testing and the testing effort The product owner should reject any user stories that have a high level of quality risk Copyright © 2014 ASTQB 14

Is the Agile Extension for You? The target professionals are: Testers experienced with traditional SDLCs Entry-level testers with an interest in agile testing Experienced developers with a lot to a little knowledge of testing who work in agile projects Roles include testers, test analysts, test engineers, test consultants, test managers, user acceptance testers, software developers The ISTQB Foundation certificate is a pre-requisite Copyright © 2014 ASTQB 15

Exam Preparation Options Training is optional, as always in the ISTQB program Training guidelines: Two-day minimum All K3 learning objectives require lecture, examples, and exercises All K2 learning objectives require lecture and examples All K1 learning objectives require lecture Books, other training courses, e-learning, and exam prep guides will follow Copyright © 2014 ASTQB 16

Conclusion The ISTQB program has extended its agile coverage The agile syllabus has three chapters with 27 learning objectives It covers the application of testing best practices in an agile project The exam is similar to the Foundation, but focused on understanding and application Training courses are available now, with other options coming soon The ASTQB has an exam ready now, which you can take as soon as the syllabus is formally released Copyright © 2014 ASTQB 17