nerdexam
BCS-ISEB

ISEB-SWTINT1 · Question #50

Scenario 2 Your organisation is a large media services corporation (MSC). MSC uses Agile development, within a Scrum framework. Here, the iterations are referred to as Sprints. For each Sprint, a…

The correct answer is C. A walkthrough of the set of user-stories, to ensure that the developers and testers understand. Option C is correct because a walkthrough is specifically designed for knowledge sharing and ensuring understanding - the team is new to accessibility rules, so the priority at each Sprint's start is confirming that developers and testers understand what the user stories…

Reviews

Question

Scenario 2 Your organisation is a large media services corporation (MSC). MSC uses Agile development, within a Scrum framework. Here, the iterations are referred to as Sprints. For each Sprint, a set of user-stories is defined, built, and tested. The user-stories are typically 1-2 lines long, indicating what the customer wants the system to do. MSC is in the process of updating its website to meet the recently introduced accessibility rules for websites. Accessibility means the availability of a system suitable to members of the public with, for example, visual or hearing difficulties. It has been decided to start with two requirements, as its first 2 Sprints: 1) Presentation of content with clear headings, short sentences, text versions always available. 2) Consistent navigation through the website. You are the test manager and there are four developers and two testers. You have all worked together previously, and are very experienced in MSCs products. Although the accessibility rules are new to you and the team, you have all attended a workshop where they were explained. Which of the following review types would be recommended at the start of each Sprint, for the reason given?

Options

  • AAn inspection, to find errors in the user-stories.
  • BA management review, to check that the user-stories will accurately reflect the rules for
  • CA walkthrough of the set of user-stories, to ensure that the developers and testers understand
  • DA technical review of the test plan, to ensure that the developers are aware that they must produce

How the community answered

(37 responses)
  • A
    5% (2)
  • B
    3% (1)
  • C
    84% (31)
  • D
    8% (3)

Explanation

Option C is correct because a walkthrough is specifically designed for knowledge sharing and ensuring understanding - the team is new to accessibility rules, so the priority at each Sprint's start is confirming that developers and testers understand what the user stories require before building and testing begins. Walkthroughs are lightweight and informal, fitting naturally into Agile's iterative, collaborative culture.

Why the distractors are wrong:

  • A (Inspection): Inspections are the most formal review type, requiring defined roles and structured defect logging - far too heavyweight for 1–2 line user stories at Sprint start, and the scenario's goal is understanding, not rigorous defect detection.
  • B (Management review): Management reviews assess project progress and resource decisions for management audiences - not the right tool for ensuring a development team understands technical requirements.
  • D (Technical review of the test plan): The test plan may not yet exist at Sprint start, and this option shifts focus away from the user stories themselves; the stated reason (making developers "aware they must produce") is also not what a technical review is for.

Memory tip: Match the review type to the goal - if the goal is understanding, choose walkthrough (think: a teacher walking students through material). If the goal is defect-finding with formality, choose inspection. If it's management oversight, choose management review.

Topics

#walkthrough#Agile reviews#user stories#review types

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full ISEB-SWTINT1 Practice