ISEB-SWTINT1 · Question #53
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 B. a and c are products risks, b, d and e are project risks. Option B is correct because it correctly distinguishes between risks tied to the quality of the deliverable (product risks) and risks tied to the delivery process (project risks). Items a and c relate to whether the website itself fails to meet accessibility requirements…
Question
Options
- Aa, b and c are product risks, d and e are project risks.
- Ba and c are products risks, b, d and e are project risks.
- Cb, c and e are product risks, a and d are project risks.
- Da, d and e are product risks, b and c are project risks.
- EA key member of the team may leave before the Sprints have been
How the community answered
(41 responses)- A2% (1)
- B68% (28)
- C7% (3)
- D5% (2)
- E17% (7)
Explanation
Option B is correct because it correctly distinguishes between risks tied to the quality of the deliverable (product risks) and risks tied to the delivery process (project risks). Items a and c relate to whether the website itself fails to meet accessibility requirements - e.g., content presentation or navigation defects - making them product risks. Items b, d, and e concern project execution factors such as team stability (item e explicitly mentions a key member leaving), resources, or scheduling - these are project risks because they threaten the project's ability to deliver, not the quality of what is delivered.
The distractors fail by misclassifying at least one item: options A and D over-count product risks by including items that are fundamentally about project management concerns, while option C incorrectly pulls item e into the product risk category even though "a key member leaving" is a classic project risk with no bearing on the product's functional quality. Option E is actually item e's description, not a valid answer choice at all.
Memory tip: Ask yourself "Does this risk live in the product or in the project?" - if the risk is about whether the software works correctly for users, it's a product risk; if it's about whether the team can build it (people, time, budget), it's a project risk.
Topics
Community Discussion
No community discussion yet for this question.