An Agile task board is a visual framework to display and sync up on the tasks moving between production steps. It is usually applied to the two most popular Agile development frameworks - Kanban and Scrum. Used by software developers and project managers, an Agile board helps manage workloads in a flexible, transparent, and iterative way1. An Agile task board provides a detailed visual representation of the whole team's status, showing which tasks remain to be started, which are in progress, and which are done. It also helps to track the progress of the current sprint, identify bottlenecks, and facilitate collaboration and communication among team members2. References:
* : ISTQB Foundation Level Agile Tester Syllabus, Version 2014, Section 2.1.1
* : ASTQB Agile Tester Certification Resources, Agile Testing Foundations, Chapter 2, Section 2.1.1
* : 6

Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 3.1Exploratory Testing, it defines atest charteras:
"A mission statement defining what to test, how it can be tested, and what issues to look for. Effective charters support focused yet flexible exploration." Option Bis the best because it specifies:
* Thearea of the system under test
* Theparameters involved
* Theapproach(combinations)
* Thegoal(discover unexpected effects)
* Option Afocuses only onone parameter.
* Option Cistoo vague.
* Option Dis tooprescriptiveand limits exploration.
References:
CTFL-AT Syllabus v4.0, Section 3.1
Learning Objective (K3) - Design effective exploratory test charters

Comprehensive and Detailed Explanation From Exact Extract:
From theCTFL-AT Syllabus v4.0, Section 5.1, it states:
"The team uses the retrospective to review how they worked during the iteration, including planning accuracy and team collaboration, and to identify actionable improvements." Thus,Option Dis correct - retrospectives help reflect on iterationplanning accuracy, team dynamics, and efficiencyto improve future iterations.
* Option Ais incorrect - retrospectives aim to focus on what the teamcan improve, not just on external hindrances.
* Option Bis false - Agile retrospectivesrequire follow-up, often in the form ofaction itemstracked in the next iteration.
* Option Cis incorrect -Product Ownerand possibly others may contribute, depending on team context.
References:
CTFL-AT Syllabus v4.0, Section 5.1
Learning Objective (K2) - Understand retrospective purpose and follow-up actions

Cross-functional teamwork is an important organizational and behavioral best practice for a tester in the SCRUM team that should have also been practiced when using the sequential model. Cross-functional teamwork means that all team members, regardless of their functional roles, collaborate and share their skills and knowledge to achieve a common goal. In the context of testing, this means that testing is not seen as a separate activity or phase, but as an integral part of the development process. All team members contribute to testing in various ways, such as:
* Involving people with the test strategy, test planning and execution as well as test reporting. This can help ensure that the testing activities are aligned with the business objectives, the user needs, and the technical requirements. It can also help improve the test coverage, the test quality, and the test efficiency.
* Sharing the responsibility for testing among the team members. This can help reduce the workload and the dependency on a single tester or a testing team. It can also help increase the feedback and the communication among the team members, and foster a culture of quality and learning.
* Leveraging the diverse skills and perspectives of the team members. This can help enhance the test design and the test execution by applying different techniques, tools, and approaches. It can also help identify and address the risks, the issues, and the opportunities for improvement from various angles. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 1.2.1, page 9; ISTQB Glossary of Testing Terms2, version 4.0, page 16.

Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 5.4Progress Tracking, it explains:
"Burndown charts track completed story points, which are only counted when the entire user story is 'done'." SinceT3 and T4 are not complete, and the user story is only complete whenall its tasks are done, thestory points are not yet burned. So,Option Cis correct.
* Option Ais incorrect -partial completiondoes not burn partial story points.
* Option Bmisrepresents the chart's purpose -story pointsremain the unit.
References:
CTFL-AT Syllabus v4.0, Section 5.4
Learning Objective (K2) - Understand how progress is tracked in Agile