The Agile Manifesto has 4 statements of values. Match the agile value on the left (1 – 4) with its traditional counterpart on the right (i – iv).
1) Customer collaboration over
2) Responding to change over
3) Individuals and interactions over
4) Working software over
i) Processes and tools
ii) Following a plan
iii) Contract negotiation
iv) Comprehensive documentation 1 – iii 2 – iv 3 – ii 4 – i 1 – iii 2 – ii 3 – i 4 – iv 1 – iv 2 – ii 3 – i 4 – iii 1 – ii 2 – iii 3 – iv 4 – i.
Which of the following statements best reflects one of the values of the Agile Manifesto? Working software allows the customer to provide rapid feedback to the developer Developers should use unit testing tools to support the testing process Business representatives should provide a backlog of user stories and their estimates to the team Adopting plans to change adds no real value to an agile project.
Which activities below best represent responsibilities that are consistent with agile development’s Whole Team approach?
Select TWO options. Testers are responsible for developing unit tests which they pass on to the developers for testing Business representatives are expected to select the tools the team will use during the project Testers are expected to work with customer representatives to create acceptance tests The whole team, not just testers, has responsibility for the quality of the product Developers are expected to test non-functional requirements (performance, usability, security, etc.).
Which of the following is an advantage of having the whole team responsible for quality? Companies no longer need to recruit and train software testing specialists Test automation tasks are now the responsibility of the development team instead of the test team Role barriers are eliminated, and team members contribute to project success based on their unique skills and perspectives Project costs are lower because the need for a specialized test team is eliminated.
Which of the following statements are true?
1. Early feedback gives the developers more time to develop new system features because they spend less time reworking features expected in earlier iterations
2. Early feedback enables agile teams to deliver features with the highest business value first, because the customer maintains focus on features with the highest system value
3. Early feedback reduces costs because it decreases the amount of time needed for system testing
4. Early feedback makes it more likely that the system built is what the customer wanted because they are given the opportunity to make changes throughout the product development process 1 and 4 2 and 3 2 and 4 1 and 3.
Which of the following is a benefit of the agile process promoting early and frequent feedback? The total number of defects found during the project is much higher than on traditional software development projects such as waterfall There is less rework because customers see the product regularly It is easy to determine the developer who introduces the most defects when integrating code There is enough time to complete all features scheduled for the given iteration.
Match the following agile software development approaches on the top with their corresponding descriptions on the bottom.
1. Extreme Programming
2. Scrum
3. Kanban
i. Embraces 5 values to guide development: Communication, Simplicity, Feedback, Courage, and Respect
ii. Divides the project into short iterations called sprints
iii. Optimizes the ‘flow’ of work in a value-added chain
1 – i 2 – iii 3 – ii 1 – i 2 – ii 3 – iii 1 – i 2 – iii 3 – ii 1 – iii 2 – ii 3 – i.
During an iteration planning meeting, the team is sharing their thoughts about a user story. The product owner advises that the customer should have one screen to enter information. The developer explains that there are technical limitations for the feature, due to the amount of information needed to be captured on the screen. Another developer says that there are risks about performance as the information will be stored in an external offsite database.
Which of the following would best represent a tester’s contribution to this discussion? The tester advises that the screen for the user story needs to be a single page to reduce test automation effort The tester advises that usability is more important than performance The tester advises that performance acceptance criteria should standard maximum of 1 second for data storage The tester advises that the user story needs acceptance criteria to be testable.
Which of the following BEST describes a tester participating in a retrospective meeting? As a tester participating in a retrospective meeting, I should bring in topics that are related
to testing only. All other topics will be covered by different participants As a tester, I participate in a retrospective meeting as an observer, ensuring that the
meeting follows the retrospective rules and agile values As a tester participating in a retrospective meeting, I should provide feedback and input on
all activities conducted by the team during the sprint As a tester, I should only attend and participate in a retrospective meeting if I have any
feedback and input related to activities conducted by the team during the sprint.
Which of the following items should NOT be raised during a retrospective meeting? There should be more emphasis on unit testing in the future, to improve overall quality The build process is manual and takes too long. Research and implementation of an
automated build framework should be done Tester XYZ is struggling to find defects. Test design training is required for this resource Automated regression test suites are taking too long to run. A review of the tests, to
eliminate redundant or unnecessary tests, is required.
Which of the following is NOT a principle of continuous integration? Continuous integration helps to build changed software regularly, including testing and deploying, in an automated way Continuous integration allows new builds to be available frequently to testers and stakeholders Continuous integration helps to identify new integration defects early and makes the analysis of these defects easier Continuous integration ensures that testing of builds is done manually, as this generates more reliable results than automated scripts.
Which of the following activities would a tester do during release planning? Produce a list of acceptance tests for user stories Help break down user stories into smaller and more detailed tasks Estimate testing tasks generated by new features planned for this iteration Support the clarification of the user stories and ensure that they are testable.
What is the most appropriate explanation of a ‘user story’? An artifact that the tester must review and sign off before testing can begin An artifact used to detail only the functional requirements of the system An artifact documented by business representatives to help developers and testers understand the system requirements An artifact written collaboratively by developers, testers, and business representatives to capture requirements.
Which of the following test activities is typically done during agile projects, but is not as common on traditional projects? Testers write detailed test plans so all team members can understand what will be tested during each iteration Testers are heavily involved in the creation of automated test cases which are then used to verify the implementation of the requirements Testers decide entry and exit criteria for each test level Testers are involved in the development to better understand what needs to be tested.
|
