BA-201 · Question #180
The business analyst (BA) at Universal Containers (UC) wants to understand why UC failed to meet a deployment date for its product go live while following the Agile process. According to the BA's…
The correct answer is C. Review the user stories to ensure they are small, testable, and valuable. The symptoms described - developers lacking clarity on scope and intent, QA unable to test by persona - are classic indicators of poorly written user stories. Good user stories must be small (clear, bounded scope), testable (acceptance criteria tied to a persona and behavior)…
Question
The business analyst (BA) at Universal Containers (UC) wants to understand why UC failed to meet a deployment date for its product go live while following the Agile process. According to the BA's research, the developers lacked a sense of the work in progress and the intended goal of that work, and the QA team was unable to clearly test the functionality based on a given persona. Which step should the BA take next?
Options
- ACreate a SWOT (Strength, Weakness, Opportunity, Threat) analysis to understand why
- BMove the deployment date out so the teams have more time to work.
- CReview the user stories to ensure they are small, testable, and valuable.
How the community answered
(28 responses)- A7% (2)
- B11% (3)
- C82% (23)
Explanation
The symptoms described - developers lacking clarity on scope and intent, QA unable to test by persona - are classic indicators of poorly written user stories. Good user stories must be small (clear, bounded scope), testable (acceptance criteria tied to a persona and behavior), and valuable (the goal is explicit). The BA should review and improve the user stories to address these gaps. A SWOT analysis (A) is a strategic planning tool, not appropriate here. Simply extending the deadline (B) does not fix the underlying quality of the artifacts the team is working from.
Topics
Community Discussion
No community discussion yet for this question.