ISTQB Agile Tester Extension Exam Theory Study Material Part 3
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. 21 to 30) with detailed explanation
Q. 21: What is “Sprint” in a Scrum project?
Scrum divides a project into iterations known as sprints.
Each sprint is of fixed length generally of two to four weeks.
<<<<<< =================== >>>>>>
Q. 22: What is “Product Increment” in a Scrum project?
The outcome of every sprint results in a potentially releasable/shippable product which is known as “Product Increment”.
<<<<<< =================== >>>>>>
Q. 23: What is “Product Backlog” in a Scrum project?
# Simplest definition of Scrum Product Backlog is simply a list of all things that need to be done within the project.
# The product owner manages a prioritized list of planned product items known as “Product Backlog”.
# It is a replacement of the traditional requirements specification artifacts. These items can have a technical nature or can be user-centric e.g. in the form of user stories.
# The product backlog evolves from sprint to sprint and is known as backlog refinement.
<<<<<< =================== >>>>>>
Q. 24: What is “Sprint Backlog” in a Scrum project?
At the beginning of every sprint, the Scrum team selects from the “Product Backlog” a set of highest priority items which are known as “Sprint Backlog”.
Instead of the product owner, the Scrum team decides on the items to be realized within a sprint, the selection is based upon the pull principle as against a push principle.
<<<<<< =================== >>>>>>
Q. 25: What is “Definition of Done (DoD)” in a Scrum project?
# To ensure the availability of a potentially releasable product at the end of every sprint, the Scrum team discusses and defines appropriate criteria for sprint completion. Such discussions enhance the team’s understanding of the backlog items and the product requirements.
# This is known as “Definition of Done”. To decide when an activity from the Sprint Backlog is completed, the Definition of Done (DoD) is used.
# Definition of Done (DoD) is a comprehensive checklist of necessary activities which ensure that only truly done features are delivered, not only in terms of functionality but in terms of quality as well.
# The Definition of Done (DoD) may vary from one Scrum Team to another, but must be consistent within one team.
# On agile projects, we need a definition of done (DoD) for every test levels.
# Generally one thinks of DoD in case of User stories, but we need to think about the definition of done (DoD) for Test Levels, Features, Iterations, and Release etc.
<<<<<< =================== >>>>>>
Q. 26: What factors are considered in “Definition of Done (DoD)”?
1) Each user story consistent with the others in the iteration
2) Aligned with product theme
3) Understood by the entire agile team
4) Have sufficiently-detailed, testable acceptance criteria
5) Card, conversation, and confirmation completed
6) User story acceptance tests completed
7) Development and test tasks for selected user stories identified, estimated, and within the achievable velocity
<<<<<< =================== >>>>>>
Q. 27: What is “Time boxing” in a Scrum project?
Time boxing refers to only those tasks, requirements, or features which the team expects to finish within the sprint as a part of the sprint backlog.
If the development team cannot finish a task within a sprint, the associated product features are removed from the sprint and the task is moved back into the product backlog.
Time boxing applies not only to tasks, but in other situations as well like in case of enforcing meeting start and end times.
<<<<<< =================== >>>>>>
Q. 28: What is “Transparency” in a Scrum project?
Transparency refers to the availability of daily reports and sprint status during the daily meeting known as daily scrum. The development team provides reports and updates sprint status on daily basis.
This makes the content and progress of the current sprint, including test results, visible to the team, management, and all interested parties.
For example, the development team can display the sprint status on a whiteboard.
<<<<<< =================== >>>>>>
Q. 29: What are the Key roles defined in a Scrum team?
Scrum defines three roles:
1) Scrum Master:
This position is not of a team lead but a coach. Scrum Master ensures that Scrum practices and rules are implemented and followed. Scrum Master resolves any violations, resource issues, or other difficulties which could prevent the team from following the practices and rules.
2) Product Owner:
Product owner represents the customer, and generates, maintains, and prioritizes the product backlog. This position is also not of a team leader.
3) Development Team:
In the Scrum Framework, the development team is a self-organized cross-functional team responsible for developing and testing the product.
The scrum team decides its own goals, as such, it remains highly motivated and delivers the best possible performance. The scrum team is allowed to select only those user stories that they can comfortably finish within the sprint length of 2-4 weeks.
The team does not have a team lead or a project manager. The Scrum Master and the Scrum Product Owner jointly share the responsibilities of the project manager.
However the decisions related to project iteration or Sprint are taken by the team as a whole.
<<<<<< =================== >>>>>>
Q. 30: What is Kanban?
Kanban is a management approach which is sometimes used in Agile projects.
The purpose of Kanban is to visualize and optimize the flow of work within a value-added chain.
Kanban has few similarities with Scrum. In both these frameworks, the progress of all active tasks is displayed on a public whiteboard for full transparency of content.
Tasks not scheduled so far are kept waiting in a backlog and moved onto the Kanban board as and when new space or production capacity is available.
Iterations or sprints are optional in Kanban. The Kanban process allows releasing its deliverables item by item, rather than as part of a release.
Synchronizing mechanism of Timeboxing is optional in Kanban, as against in Scrum, the Timeboxing synchronizes all tasks within a sprint.
ISTQB Agile Tester Extension Exam Theory Study Material Part 4
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.