ISTQB STQB-Agile-Public Practice Test - Questions Answers

In release planning for Agile project management, activities such as identifying testable user stories with acceptance criteria (i), prioritizing the user stories (iii), and performing high-level estimation for the release (vi) are essential. These activities ensure that the team has a clear understanding of what needs to be delivered, the order of importance of the deliverables, and an estimate of the effort required to achieve the release goals.

The defect titled 'Payment for parking ticket is restricted to cash only (no credit card supported)' is out of scope for the given test charter titled 'Buy a bus ticket' because it pertains to a different functionality not covered by the charter. The charter focuses on the process of purchasing a bus ticket, which involves functionality such as selecting a ticket type, choosing a journey, and completing the transaction. A defect related to payment methods for a parking ticket does not relate to these functions and is therefore considered out of scope for the testing session focused on buying a bus ticket.

In an agile project, testers often perform tasks beyond traditional testing roles, including implementing test strategy (i), measuring and reporting test coverage (iii), and coaching the development team on relevant aspects of testing (iv). Implementing test strategy involves planning how testing will be conducted within the agile framework, ensuring that testing aligns with agile principles and practices. Measuring and reporting test coverage help the team understand the extent to which the codebase is tested, which is crucial for maintaining quality in fast-paced agile environments. Coaching the development team involves sharing knowledge on testing best practices and fostering a quality-centric mindset across the team. These activities contribute to the collaborative and iterative nature of agile projects, where continuous feedback and improvement are emphasized.

A test charter is primarily used in exploratory testing (i) to guide the test session with a clear mission or objective, which might be related to specific functionalities, user stories, or areas of the application, making reference to user stories (iii) plausible. It also contains notes taken during the test session (iv), which are crucial for documenting observations, anomalies, and insights gained during exploratory testing. This approach aligns with Agile's emphasis on individuals and interactions and responding to change, as exploratory testing is inherently adaptive and relies on the tester's skill, creativity, and intuition. It contrasts with more traditional, documentation-heavy approaches, emphasizing the value of working software and collaboration.

Scrum is the agile development approach that incorporates the practice of dividing a project into iterations called sprints, with each sprint resulting in a potentially releasable/shippable product. Scrum's iterative and incremental approach allows teams to deliver working software frequently, with a focus on delivering tangible value to the customer at the end of each sprint.

In Agile teams, collaboration and direct communication are key. When faced with blocked tests due to ongoing development or failing unit tests, an agile tester should collaborate with the developer to identify and resolve the issues. This approach encourages teamwork, knowledge sharing, and problem-solving, leading to more efficient and effective resolution of blocking issues.