Course Description

ISTQB Advanced Test Manager

The ISTQB Advanced Test Manager course builds the knowledge gained in the ISEB/ISTQB Foundation Certificate up to an advanced level.

Having successfully passed the ISTQB Foundation certificate is a prerequisite for delegates attending this course. In addition, it is recommended that delegates have a minimum of 3 years testing experience before attempting this qualification. The Advanced Test Manager Certificate is one of the three advanced testing certificates, the others are Advanced Test Analyst and Advanced Technical Test Analyst. Candidates may find the BCS Intermediate Certificate a useful bridge between Foundation and Advanced, although it is not mandatory.

The ISTQB Advanced Test Manager syllabus is intended for testing professionals who are, or intend to become, test leaders or test managers. This includes; testers, test engineers, test analysts, test leads and test managers. The ISTQB Advanced Test Manager course spans 5 days, with a 3 hour examination on the final day.

Our trainers are experienced testing practitioners with many years of software testing experience to relate to candidates in order to enhance the learning process. This tutor led course is carried out at locations UK wide, the price includes the ISTQB examination fee, lunches and all course materials.

Cost

The course is priced at £1200 per delegate excluding VAT. This includes the ISTQB examination fee, all course materials, lunch and refreshments.

Courses can be arranged at your offices for group bookings of 4 or more delegates, these can be run on the normal five day basis or for less experienced groups, over longer periods – allowing extra time for practical exercises and discussion. Contact us for full details or a quote. Please note prices exclude VAT.

Select the location of your choice, then click a date to book a place:

The course is presented in 14 modules that are split in two parts of ‘A’ and ‘B’. Each part lasts two and three days respectively:

Course Design

PART A

Module 1: Introduction to the Test Manager Syllabus
Presents an overview of the course, its arrangement and the examination.

Module 2: Foundation Certificate Review
A review of the material covered in the Certified Tester: Foundation Level training course.

Module 3: Basic Aspects of Software Testing
This Module introduces central testing themes that are generally relevant for all testing professionals. These themes will be explained in the context of the Test Management discipline, and illustrated with relevant examples.

Testing in the Software Lifecycle
Describes the relationships between testing activities and software development activities, and between the testing discipline and other software project disciplines, in the sequential, iterative, and evolutionary software development models.

Specific Systems
Considers the roles of testing, and test management, in relation to systems of systems, and safety-critical systems.

Metrics and Measurement
Discusses how to monitor test activities by measurements related to test objects, test assets, and the test process, and how to mount a measurement (metrics) programme.

Tester Ethics
Provided to encourage ethical behaviour by testing professionals; subscription to the ISTQB Code of Ethics for Software testers is a prerequisite for the Advanced examinations.

Module 4: Testing Processes

      • The Fundamental Test Process
      • Test Planning and Control
      • Test Analysis and Design
      • Test Implementation and Execution
      • Evaluating Exit Criteria and Reporting
      • Test Closure Activities

Module 5: Test Tools and Automation
This module expands on the Foundation Level Syllabus, covering a number of general concepts and discussing some specific tools in further detail.

Test Tool Concepts
Explains the benefits and risks of acquiring and deploying test tools, considering various strategies (including internal development of tools), scripting languages, test oracles, and open source tools.

Test Tool Categories
Summarises several categories of test tool, including some additional to those covered in the Foundations Syllabus, giving consideration to objectives, intended uses, and strengths and weaknesses.

Module 6: Reviews
This module re-examines the four kinds of review covered at the Foundation Level, plus two others included in IEEE Std 1028, the Standard on Software Reviews. It considers strengths and weaknesses of each type, and how they might be used singly and in combination.

The Principles of Reviews
Expands on Foundation-level concepts of reviews, revisiting the process, roles, and tools and discussing them in greater detail.

Types of Review
Briefly revisits Walkthroughs, technical reviews, and Inspections, then introduces Management Reviews and Audits, concluding with some principles of reviewing particular kinds of document.

Introducing Reviews
Provides a step-by=step process for introducing reviews into an organisation that has no culture of reviews, including techniques for selecting an appropriate mix of review types, monitoring the ongoing cost-effectiveness of review activities, and avoiding common problems in the conduct of reviews.

Success Factors For Reviews
Discusses causes of successful or failing reviews in three categories: Technical factors (important aspects of reviews themselves), Organisation factors (important aspects of the reviews environment within an organisation), and People factors (important issues in the personal psychology of reviews).

Module 7: People Skills and Team Composition

Individual Skills
Describes a balanced set of five skill types needed in a test team, and preferably found within each tester. Expands to include additional skills required of test managers. Concludes by reviewing ways of acquiring professional skills.

Test Team Dynamics
Particularly concerned with selection, assimilation, and induction of new hires to a test team.

Fitting Testing Within an Organisation
Reviews six options for relationships between testing and development, with particular attention to out-sourcing.

Motivation
Considers both motivating factors for testers, and de-motivators. Advises how to gain evidence of motivation within the team.

Communication
Outlines factors that tend to promote professional, objective, and effective communication within and between teams and other groups.

Module 8: Incident Management
Incidents are threats to the achievement of individual and group goals, and should be managed accordingly.

When Can an Incident Occur?
Reviews the nature of incidents and their relationships to failures, defects, errors, and software lifecycle activities.

Incident Lifecycles
Provides an overview of the skeleton “incident life cycle” in IEEE Std 1044. Particularly considers classification of incidents for downstream analysis, and collection of supporting data.

Incident Reporting Data
Discusses formal compliance with the requirements of IEEE Std 1044.

Incident Management Metrics
Examines data requirements for incident management and use of metrics in monitoring test status and progress, including stability trend, defect trend, defect density, fault feedback ratio, trend convergence and divergence, and Defect Detection Percentage, Considers the use of defect taxonomies and root cause analysis in relation to software incidents.

 

Part B

Module 9: Test Management Documentation
This Module is concerned with the documentation necessary to control test activities in order to meet organisational and project goals.

Test Management Processes and Documents
Describes the interactions between organisational, managerial, and technical test processes, and revisits the hierarchy of test management documentation introduced at Foundations level.

Test Policies
Explores the need for and creation of organisational test policies. Outlines contents of a possible test policy for achieving defined organisational objectives.

Test Strategies
Considers test strategies as tools for implementing policy. Addresses contents and creation of test strategies, with particular attention to the definition of test levels.

Master Test Plan
Describes purpose of master test plans and relationships to other test management documentation. Examines possible Master Test Plan contents based on IEEE Std 829-2008.

Level Test Plans
Describes purpose of Level Test Plans and relationship to other test management documentation. Considers contents of an IEEE Std 829 level test plan in terms of project objectives in dimensions of scope, quality, time, cost, and risk.

Scheduling Test Planning
Explores advantages and problems of early planning, and how to plan for and maintain test plans.

Module 10: Test Estimation, Monitoring and Control
This Module covers principles and methods of test estimation, monitoring and reporting the status of testing, and management activities to ensure that testing remains under control.

Estimation Principles
Summarises the nature and purpose of test estimation, including its importance, a defined process for doing it, and important factors in getting it right.

Test Estimation Methods
Reviews five categories of estimation method, plus a method of gauging confidence levels.

Overheads, Contingencies, and Test Cycles
Describes layers of adjustment that might be necessary to raw estimates of effort required for a task. Illustrates how multiple cycles of test execution might be estimated within a test level, and why they might need to be.

Introduction to Test Progress Monitoring and Control
Formulates a process for management monitoring and control of test processes, based on plans. Identifies aspects of testing that may be subject to monitor and control activities.

Monitoring by Measurement
Introduces, examines, and illustrates five dimensions of measuring test progress: software product risks, testware products, test coverage, known defects, and confidence.

Reporting Test Status
Identifies management’s role in reporting status to other stakeholders. Considers various formats of test summary report, using IEEE Std 829-1998 and IEEE Std 829-2008, and considering a variety of report recipients.

Module 11: The Value of Testing
This Module surveys the types of information that would be useful in presenting a Business Case for software testing, and also looks at test staffing strategies.

Business Value of Testing
Discusses what constitutes “value” for the business, versus what constitutes “costs”. Describes the parameters that make up the “Cost of Quality”. Relates “testing” to the cost, and value, of “quality” for a software-using organisation.

Test Staffing Strategies
Explores risks in, and commonalities and differences between, three test staffing strategies: distributed, outsourced, and “in-sourced”.

Module 12: Risk-Based Testing
Explains the various ways in which risk-based testing responds to risk, how risk can be managed in software and testing projects, and how Failure Mode and Effects Analysis deals with risk.

Introduction to Risk-Based Testing
Reviews product and project against the proposition that “all testing is risk-based”. Presents software testing as a planned approach to monitoring and controlling software product risk.

Risk Management
Examines the three-stage iterative process for risk identification, analysis, and mitigation. Shows how to assess likelihood and impact of software product failure, and how to build a risks register. Presents the three (or four) primary options for responding to risk. Discusses respective options for product risk management and project risk management.

Risk Management in the Software Life Cycle
Introduces, examines, and illustrates five dimensions of measuring test progress: software product risks, testware products, test coverage, known defects, and confidence.

Reporting Test Status
Identifies management’s role in reporting status to other stakeholders. Considers various formats of test summary report, using IEEE Std 829-1998 and IEEE Std 829-2008, and considering a variety of report recipients.

Module 13: Standards and Test Process Improvement
This Module considers the role of standards in normalising test activities, then outlines the principles of test process improvement, taking into account four specific approaches.

Standards
Summarises the nature of different types of standard, reviews the potential applicability of international, national, and domain-specific standards, and outlines the concept of standards compliance.

Test Process Improvement
Explores the need for test process improvement, including discussion of typical symptoms of need.
Considers industry statistics indicating the widespread need for process improvement. Introduces the Shewhart-Deming cycle as the basis of test process improvement methods, and lists several process improvement approaches, some generic for software projects, some specifically aligned towards test process improvement.

Improving the Test Process
Reviews two competing approaches to software development process improvement, the “Capability Maturity Model” (CMM) and the “Software Process Improvement and Capability determination” model (SPICE). Introduces CMMI (“Capability Maturity Model Integration”) as an amalgam of the two approaches, and examines the role of Verification and Validation in CMMI efforts. Briefly introduces process improvement models specifically aimed at test process improvement, including the ISTQB generic process for process improvement models that lack a specific improvement process

Improving the Test Process With TMMi
Examines the Test Maturity Model Integrated as a CMM-style test process improvement model.

Improving the Test Process With TPI
Examines the Test Process Improvement model as a SPICE-style test process improvement model.

Improving the Test Process With CTP
Introduces the Critical Testing Processes model for assessing current testing methods, using the ISTQB generic process improvement model to achieve improvement objectives

Improving the Test Process With STEP
Introduces the Systematic Test and Evaluation Process as a model for software development, using the ISTQB generic process improvement model to achieve improvement objectives.

Module 14: Test Management Issues
This Module considers special management issues in three categories.

Exploratory Testing
Considers the nature and roles of exploratory testing, and its possible contributions to a software development and testing project.

Special Systems
Reviews test management issues related to test strategies, benefits and disadvantages, and adequacy for systems of systems and safety-critical systems, with their impact on planning, coverage, and monitoring and control.

Non-Functional Testing
Reviews test management issues related to test strategies, benefits and disadvantages, and adequacy for systems of systems and safety-critical systems, with their impact on planning, coverage, and monitoring and control.

The Exam

The examination is a 3 hour multiple choice paper that is carried out by an external examiner, provided by the     British Computer Society. Examinations takes place on the final day of the course, on the 5th day. In cases where English is not the first language, a time extension of 45 minutes is available. Candidates must achieve a grade of 65% to successfully pass the ISTQB Advanced Level Exam.

Training

logo