nerdexam
BCS-ISEB

ISEB-SWTINT1 · Question #60

Scenario 4 A bank is upgrading its systems to include an on-line investment service, allowing investors to trade with each other, in a mini-stock market environment. The upgrade will be carried out…

The correct answer is A. A management review of the test plan and results. Option A is correct because the test manager has identified a delivery risk - the Sprint is halfway through and likely to miss its deadline. A management review is the appropriate response at this point, as it escalates the issue to the right authority level, examines test plan…

Reviews

Question

Scenario 4 A bank is upgrading its systems to include an on-line investment service, allowing investors to trade with each other, in a mini-stock market environment. The upgrade will be carried out using Agile development (within the Scrum framework). Here, the iterations are referred to as Sprints. For each Sprint the required functionality will be defined as a set of user-stories. The user stories are typically 1-2 lines long, indicating what the business wants the system to do. These user stories will be built then tested. There will be 3 Sprints: 1) Creation of the mini-stock market trading environment. 2) Creation of additional front-end enhancements. 3) Linking to stock exchange for pricing. You are the test manager. You lead a team of 4 testers, and there are 6 developers. Your team has worked on Agile projects previously, and on average, Sprints usually last 4 weeks. At the end of all Sprints, a full end to end test is carried out. This is called the E2E test phase. The timescales for Sprint 1 were not changed, and development is now halfway through. You are convinced that delivery will be late. Which of the following reviews would be recommended at this time?

Options

  • AA management review of the test plan and results.
  • BA walkthrough of the test plan and results.
  • CA technical review of the user-stories.
  • DAn inspection of all code for the trading environment.

How the community answered

(42 responses)
  • A
    81% (34)
  • B
    12% (5)
  • C
    5% (2)
  • D
    2% (1)

Explanation

Option A is correct because the test manager has identified a delivery risk - the Sprint is halfway through and likely to miss its deadline. A management review is the appropriate response at this point, as it escalates the issue to the right authority level, examines test plan progress and results, and enables management to make informed decisions (adjusting scope, adding resources, or revising timelines).

Option B (walkthrough) is wrong because a walkthrough is an author-led peer review technique used to examine a document, not a mechanism for addressing schedule risk at a management level - it lacks the authority to drive corrective action.

Option C (technical review of user stories) is wrong because user stories are already defined and mid-Sprint development is underway; revisiting requirements at this stage doesn't address the lateness problem and would likely make things worse.

Option D (inspection of all code) is wrong because a full formal code inspection is the most time-consuming type of review - conducting one mid-Sprint when you're already late would compound the delay rather than resolve it.

Memory tip: Match the level of the problem to the *level of the review. Schedule/delivery risk = Management review (decisions get made). Technical quality issues = technical review or inspection. Think: "Who has the authority to fix this problem?" - that's who needs to be in the room.

Topics

#management review#test results#review types#regulatory compliance

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full ISEB-SWTINT1 Practice