Area 01 · For people turning a business question into a shared, testable need.
Business analysis and requirements
Objective: Frame the outcome, stakeholders, constraints, and evidence that make a requirement useful.
Video lesson and accessible transcript
Approved video media has not been supplied yet. Coming soon; the equivalent text below is the complete lesson for this course session.
Open transcript / equivalent text
Start with the decision or outcome, not a preferred solution. Ask who is affected, what must be true, what is constrained, and how the team will know the need has been met. Capture assumptions separately from confirmed requirements. A useful requirement can be discussed, traced to a need, and revisited when the context changes.
Practical takeaways
- Name the outcome before writing a solution-shaped requirement.
- Separate confirmed facts, assumptions, constraints, and open questions.
- Make acceptance evidence visible to the people who will use it.
Practice scenario
Scenario: inconsistent public-service intake
A regional service team receives the same request through email, paper, and three web forms. Residents report repeating information, while staff cannot tell which requests are urgent. The team asks for “one new portal” before agreeing on the outcome.
Write the first outcome statement you would bring to the next conversation. Include one stakeholder perspective and one question that must be answered before solution selection.
Knowledge check
Check your understanding before continuing.
Answer each scenario question. Feedback appears immediately and remains available when you revisit this lesson.
Question 1 of 1