Assume that you are working for an ambitious start-up that is developing a system which provides customized loyalty and rewards programs for small and medium-sized companies selling to webbased customers. The companies using the system are able to self-enroll on the system’s web store and can then create customized buttons for their websites. These buttons can then be used to allow their customers to enroll in the companies’ loyalty and rewards program. Each subsequent purchase earns points, and both companies and their customers can manage the program; for example, to determine the number of points required to receive a free product or service.

Your employer’s marketing staff is heavily promoting the system by offering aggressive discounts on the first year’s fees to sign up inaugural companies. The marketing materials state that the service will be highly reliable and extremely fast for companies and their customers.

Four months ago, the requirements had been completed and the development of the software was started. When analyzing the quality risks, the adaptation of the buttons was classified as the lowest risk, while registration was classified as the highest risk. As planned in the schedule, the first release was launched a month ago and companies and their customers could start registering.

The system has now been in use by companies and their customers for a month. Your team has used a mix of risk-based testing, requirements-based testing, and reactive testing. You are now conducting a retrospective for the testing work.

Which TWO of the following areas should most likely be considered in this retrospective?

Select TWO options.

You are a tester in an Agile software development team that has just completed an iteration. You are preparing for the retrospective meeting with the rest of the team.

Which of the following activities is NOT part of a typical retrospective?

Select ONE option.