###BeginCaseStudy###
Scenario: 4
V2
Test Management Tool
The project situation after 11 months is:
– The first increment was released one week late but contained sufficient functionality to be
declared fit for purpose’. However, there were 20 outstanding incidents deferred to
increment two.
– The amount of voluntary overtime worked PV the test team has reduced the second
Increment slippage to just 3 weeks.
– There is talk of reducing the scope of requirements. The purpose of this is to first deliver
the application with support for manual testing and then to provide a delivery * weeks later to
resolve any remaining points and provide support for automated testing (i.e. the link to the
capture-replay tool).
– Concerns have been expressed by a section of the user community, that in some places
the usability is very poor.
###EndCaseStudy###

Which of the following are valid reasons for adopting a different life cycle (from the V model),
for increments after the first year?
i) We do not have a clear understanding of the requirements from a customer perspective.
ii) We see the risk of delivering requested functionality late as being higher than the risk of
delivering a lower quality product.
iii) We do not have a budget for additional regression testing which is needed to ensure that
existing functionality is not compromised by future iterations.
iv) The company test strategy does not fit well within the V life cycle model.

A.
(i) and (ii)

B.
(i) and (iv)

C.
(ii) and (iii)

D.
(ii) and (iv)