Free ISTQB-CTFL-AT Mock Exam – Practice Online Confidently

In agile projects, when should we transform user stories and acceptance criteria into more formal requirements specifications ?

Given the following results from a product risk analysis that occurred at the beginning of an iteration:• User story 1 (Performance): likelihood: high, impact: high• User story 2 (Security): likelihood: high, impact: high• User story 3 (Functional): likelihood: medium, impact: high• User story 4 (Functional): likelihood: high, impact: medium• User story 5 (Compatibility): likelihood: low, impact: low• User story 6 (Recoverability): likelihood: low, impact: lowWhich TWO of the following describes best what the team should do with this information? Select TWO options. A. Move onto planning poker session to estimate effort for user stories, and determine what can be done in the current iteration, and what needs to be added to backlog.B. Remove user stories 5 and 6 from the current iteration and move to a later iteration.C. Because of the number of high likelihood, high impact risks slotted for this iteration, the team has no choice but to extend the timeframe of the iteration by 2 weeks.D. The team should collaborate on effective ways to mitigate the high likelihood, high impact risks.E. The team should plan to complete all items in the current sprint, but save the lower risk items for the end of the sprint, and only test these items if there is time. 

An Agile team has done all the necessary tasks to identify quality risks, categorize risks and assess risk level, estimate efforts according to risk level and selected strategy to mitigate risks. In the middle of the iteration, customer came up with a set of new requirements and changes to user stories selected for the current iteration. What should the team do in terms of keeping risk low?

Which of the following is the correct pairing according to the Agile Manifesto statement of values?

User Documentation is a type of...