software testing genius

ISTQB Agile Tester Extension Exam Theory Study Material Part 11

Welcome to “Software Testing Genius”. Subscribe to my RSS feed for latest content on Software Testing.

ISTQB Agile Tester Extension Exam Theory Study Material Part 11

Have a deep study of this entire question bank containing theory portion with detailed explanation. This study resource is as per the latest syllabus.

Just 1 hr. of time spent in brushing up your knowledge just before the ISTQB Agile Tester Extension Exam shall be of great help in clearing it.

Set of 10 Questions (Q. 101 to 110) with detailed explanation

Q. 101: What are the best practices related to Teamwork in Scrum teams?

When we talk about Agile it is all about teamwork.

The entire team follows agile methods with the whole-team approach.

An agile team is principally represented by three roles:

ISTQB Certification

Following organizational and behavioural best practices focussing on the role of “Tester” are;

1) Cross-functional team:
A team comprises of the group of people with different functional expertise working toward a common goal. The team works together on test strategy, test planning, test specification, test execution, test evaluation, and test

results reporting.

2) Self-organizing team:
In case of a conflict or disorder, some mechanism of coordination among the team members must be in place. The team may have developers, along with one or more testers.

3) Co-location:
Testers must sit together with the developers and the product owner.

4) Collaborative environment:
Testers must collaborate with own team members, other teams, the stakeholders, the product owner, and the Scrum Master to achieve shared goals.

5) Empowerment:
Technical decisions regarding design and testing are made by the team as a whole (developers, testers, and Scrum Master), in collaboration with the product owner and other teams if needed.

6) Commitment:
The tester must be committed to question and evaluate the product’s behaviour and characteristics with respect to the expectations and needs of the customers and users.

7) Transparency:
It refers to openness, communication, and accountability of each team member. Development and testing progress must be visible on the Agile task board.

8) Credibility:
The tester must ensure the credibility of the strategy for testing, its implementation, and execution, otherwise, the stakeholders will not trust the test results. This is generally done by providing information to the stakeholders about the testing process.

9) Openness to feedback:
Feedback is an important aspect of being successful in any project, especially in Agile projects. Retrospectives allow teams to learn from successes and from failures.

10) Resilience:
Testing must be able to quickly respond to changes, like all other activities in Agile projects.

<<<<<< =================== >>>>>>

Q. 102: What activities are performed by testers during Sprint zero or first Sprint iteration?

1) Identify the scope of the project (i.e. Product backlog).

2) Divide user stories into sprints

3) Create initial system architecture and high-level prototypes.

4) Plan, acquire and install needed tools - for test management, defect management, test automation, and continuous integration.

5) Create an initial test strategy - for all test levels, addressing the test scope, technical risks, test types, and coverage goals.

6) Perform an initial quality risk analysis.

7) Define test metrics - to measure the test process, the progress of testing in the project, and product quality.

8) Specify the definition of “done”.

9) Create the task board.

10) Define exit criteria – to decide when to continue or stop testing before delivering the system to the customer.

<<<<<< =================== >>>>>>

Q. 103: What are the Agile Testing Practices used by testers in a scrum team?

1) Pairing:
Pair testing is a technique in which two team members like a tester and a developer or two testers, or a tester and a product owner sit together at one workstation to test or carryout any other sprint task. The idea of involving two people is that when one person does the testing, the other one analyzes or reviews the test.

2) Incremental test design:
Test cases and charters are gradually built from user stories and other test bases, starting with simple tests and moving toward more complex ones.

3) Mind mapping:
Mind mapping is a useful tool to visually organise the information through a diagram. For example, testers can use mind mapping to identify which test sessions to perform, to show test strategies, and to describe test data.

We generally create mind map around a concept, drawn as an image in the centre of a blank landscape page, to which associated representations of ideas such as images, words and parts of words are added.

ISTQB Certification

Major ideas are connected directly to the central concept, and other ideas branch out from them.

<<<<<< =================== >>>>>>

Q. 104: What is the role of tester in Integration in Agile projects?

The primary objective of a tester is to:

1) Continuously deliver customer value:
# In the each sprint

# At the end of the project

2) Continuous testing requires identifying all dependencies between functions and features
# Integration strategy is helpful for this process

# Important to identify all dependencies between underlying functions and features Test

<<<<<< =================== >>>>>>

Q. 105: What tasks are parts of Sprint planning by an Agile team?

Planning includes following tasks displayed on Agile task board (covering at least 1-2 days)

1) What: Test scope, the extent of testing, test and sprint goals.

2) Why: Explain what is in and out of the scope.

3) Who: Assign testing of features and characteristics.

4) Where: Which test environment and what changes, data, tools, and configurations are needed.

5) When: Start date and frequency of testing tasks.

6) How: Which test methods, techniques, tools, and data.

7) Prerequisites: Predecessor tasks, expertise, training required.

8) Dependencies: Functions, code, system components, vendor, technology, tools, activities, tasks, teams, test types, test levels, and constraints.

9) Project and quality risks: What are the risks involved.

10) Priority: Consider customer / user importance.

11) Time: Duration and effort required for testing.

<<<<<< =================== >>>>>>

Q. 106: What types of risk are encountered by Agile teams?

A risk is the possibility of a negative or undesirable outcome or event.

The level of risk is found by assessing the likelihood of occurrence of the risk and the impact of the risk.

Risks are mainly of two types;

1) Quality risks or Product risks:
When the primary effect of the potential problem is on product quality, potential problems are referred to as quality risks or product risks.

2) Project risks or Planning risks:
When the primary effect of the potential problem is on project success, potential problems are referred to as project risks or planning risks.

<<<<<< =================== >>>>>>

Q. 107: When quality risk analysis is done in Agile projects?

Quality risk analysis is done during;

1) Release planning:
Business representatives who know the features in the release provide a high-level overview of the risks, and the whole team, including the tester(s), may assist in the risk identification and assessment.

2) Iteration planning:
The whole team identifies and assesses the quality risks.

<<<<<< =================== >>>>>>

Q. 108: What are the examples of quality risks?

Examples of quality risks for a system include:

1) Incorrect calculations in reports - is a functional risk related to accuracy.

2) Slow response to user input - is a non-functional risk related to efficiency and response time.

3) Difficulty in understanding screens and fields – is a non-functional risk related to usability and understandability.

<<<<<< =================== >>>>>>

Q. 109: How the tasks are prioritized based upon the level of quality risk associated with them?

# An iteration starts with iteration planning, which gets displayed on a task board after time estimation.

# Tasks can be prioritized in part based on the level of quality risk associated with them.

# Tasks associated with higher risks should start earlier and involve more testing effort.

# Tasks associated with lower risks should start later and involve less testing effort.

<<<<<< =================== >>>>>>

Q. 110: What is the process of quality risk analysis during iteration planning?

Quality risk analysis is done during iteration planning in the following steps:

1) Gather all the Agile team members together, including the testers.

2) List out all the backlog items for the current iteration on the task board.

3) Identify the quality risks associated with each item, considering all relevant quality characteristics

4) Assess each identified risk, by two activities like:
a) Categorizing the risk and

b) Determining its level of risk based on the impact and the likelihood of defects

5) Determine the extent of testing proportional to the level of risk.

6) Select the appropriate test techniques to mitigate each risk, based on the risk, the level of risk, and the relevant quality characteristic.

ISTQB Agile Tester Extension Exam Theory Study Material Part 12

Full Study Material on ISTQB Agile Tester Extension Exam 

Largest Database of Sample Papers - 1000+ Unique Questions for ISTQB Foundation Exam

ISTQB Foundation Exam - Full Crash Course for Download

ISTQB Advanced CTAL Test Analysts Exam - Full Crash Course for Download


ISTQB Advanced CTAL Test Manager Exam - Full Crash Course for Download


Consolidated Study Material - All ISTQB Certification Exams

What Successful Testers say about the Quality of this website

If you want to keep track of further articles on Software Testing,
I suggest you to subscribe my
RSS feed

.

You can also Subscribe by E-mail
and get All New articles delivered directly to your Inbox.


Quick Navigation of Software Testing Genius

Get your Absolutely Free Copy of Several MS PowerPoint Presentations & E-Books related to ISTQB, HP Load Runner, IBM RFT, HP QTP & QC Certification Exams, prepared by Popular Writers & Trainers, by writing to: Software.testing.genius@gmail.com

Full Study Material for Certification Exams on Automation Tools :

Study Material - IBM RFT Certification Exam

Study Material - HP QTP & QC Certification Exams

Study Material - HP LoadRunner Certification Exams for All Modules

Most Popular Topics in Demand:

Practical Roadmap to QTP Certification

Practical Roadmap to CSTE Certification

Consolidated Study Material - Testing & QA

Rehearsal of QTP in 1 Hr. -  Interview Questions

 

Comments :

0 comments ↓


Leave Your Comments: (*) Marked Fields are Mandatory

You can apply basic formatting to the text

Name *
 
Email Address *
 
Website
 
Speak your mind
characters
sex hikayeleri