FREE REQUIREMENTS DISCOVERY LEARNING PATH

WikiFree original practice workbook

The discovery lens

CASE STATUS: fictional/synthetic teaching material. Do not present the example as real research, employment experience or measured business performance.

OUTCOME
Turn fictional interview evidence into prioritized requirements, acceptance examples and a traceable validation plan.

BEFORE YOU START
Basic workplace communication and a text editor; no prior business-analysis role is required.

CASE
Elm Equipment Library lends tools. Staff propose a mobile app, but the case evidence concerns unclear availability and return reminders. The training goal is to establish what must change before selecting software.

INPUTS
Evidence ID,Fictional observation
E1,A borrower phoned twice because the online list did not show whether a drill was available.
E2,A volunteer copied return dates from paper into a spreadsheet at the end of each day.
E3,A borrower missed a return date because no reminder was received.
E4,Some borrowers use a shared phone and prefer a printed receipt.


ENTRY CHECK

Question: Is a requested app already a validated requirement?

Self-check: It is a proposed solution; first identify the need and constraint.

Question: Can an interview quote establish how common a problem is?

Self-check: Not by itself. It is evidence from that case or participant.

Question: What makes acceptance useful?

Self-check: An observable result under a stated condition.

STAGE 1: Separate evidence from assumptions

Prerequisite: Basic workplace communication and a text editor; no prior business-analysis role is required.

Instruction: An observation describes what happened; an interpretation explains why you think it happened. Keep them in separate columns. A proposed solution may address one symptom while creating another. Start by asking which task fails, who experiences the failure and what successful completion looks like. These supplied observations are synthetic; do not present them as research you conducted.

Practice task: Code E1–E4 into task, obstacle, consequence and uncertainty. Write three follow-up questions that avoid suggesting the desired answer.

Deliverable: An evidence and question log

Acceptance check: Each claim points to evidence or is explicitly marked as an assumption.

If stuck: If a question asks whether the participant wants your app, rewrite it around a recent borrowing experience.

Record your work, decisions and evidence:




Record your result against the acceptance check:



STAGE 2: Describe the present workflow

Prerequisite: Bring your previous output: An evidence and question log

Instruction: Map the current journey across people and records. A problem can occur at a handoff rather than inside a screen. Note when availability becomes known, who records a loan and when the next person receives that information. Preserve alternative routes, including the printed receipt. A workflow model should reveal decisions and missing information rather than decorate a preferred solution.

Practice task: Map request, availability check, checkout, reminder and return. Mark the handoff connected to each evidence item.

Deliverable: A current-state workflow

Acceptance check: The double-entry and availability gaps are located in specific transitions.

If stuck: If every step is a screen, add the people, records and decisions between screens.

Record your work, decisions and evidence:




Record your result against the acceptance check:



STAGE 3: Write solution-neutral needs

Prerequisite: Bring your previous output: A current-state workflow

Instruction: A requirement states needed behavior or a constraint. It should be narrow enough to test without specifying unnecessary implementation. The system must show current availability is more useful than build a modern app. Add the affected actor and relevant timing. Separate functional behavior from constraints such as shared-device privacy and the ability to obtain a printed record.

Practice task: Write six requirements with IDs, evidence links and priorities. Explain two exclusions from the first release.

Deliverable: A prioritized requirement set

Acceptance check: Requirements are traceable, testable and do not assume every borrower owns a personal smartphone.

If stuck: Split any requirement containing several independent behaviors into separately reviewable statements.

Record your work, decisions and evidence:




Record your result against the acceptance check:



STAGE 4: Make acceptance observable

Prerequisite: Bring your previous output: A prioritized requirement set

Instruction: Acceptance examples connect conditions, actions and results. Include exceptions, not just the successful path. If two people request the last drill, the second should not receive a false confirmation. A reminder requirement also needs a rule for missing contact details. Avoid undefined words such as quickly or intuitive unless you state how they will be evaluated.

Practice task: Write successful and unsuccessful examples for availability, checkout and reminders. Add a printed-receipt case and a missing-contact case.

Deliverable: An acceptance-example table

Acceptance check: Each requirement has at least one observable check and the conflicting-booking case is covered.

If stuck: If an example merely repeats the requirement, add concrete input, action and expected output.

Record your work, decisions and evidence:




Record your result against the acceptance check:



STAGE 5: Plan validation and manage changes

Prerequisite: Bring your previous output: An acceptance-example table

Instruction: Validation checks whether the proposed result addresses the need; verification checks whether the specified behavior was implemented. A prototype can expose misunderstandings before development. Decide whose feedback matters and how changes will be assessed. Keep the evidence-to-requirement-to-check chain intact when scope changes. A neat matrix does not compensate for an untested assumption.

Practice task: Design a five-task prototype review using the fictional scenarios. Introduce a request for loyalty points and assess its evidence, value and impact on the first release.

Deliverable: A traceability matrix and change decision

Acceptance check: Every included requirement has evidence and a check; the new request receives a reasoned disposition.

If stuck: If the change is accepted only because a senior person asked, document the missing evidence and trade-off.

Record your work, decisions and evidence:




Record your result against the acceptance check:



WORKED CASE
E1 supports current availability; E2 supports a single recorded loan and a timely handoff; E3 supports a reminder rule; E4 supports an accessible receipt route and shared-device caution. None of these observations alone proves that a native mobile app is necessary. A simple prototype can validate the workflow before a platform decision.

FINAL PROJECT
Deliver the Elm discovery dossier: evidence log, workflow, six prioritized requirements, acceptance examples and a traceable validation/change plan.

REQUIRED CRITICAL CHECK
Fabricated research, unsupported consensus or a requirement without a check must be corrected.

SCORING
Score each of the five stage acceptance checks from 0–16 (0 missing/incorrect; 8 partially supported; 16 complete and evidenced). Score the final integrated project from 0–20 (0 missing; 10 incomplete handover; 20 complete, reproducible and consistent with the case). Target: at least 80/100 AND the critical check must pass. A total score never overrides a failed critical check.

SCOPE LIMIT
This is requirements discovery for a small service change, not CBAP preparation or comprehensive enterprise business analysis.

SOURCES AND ACCESS
Assigned public videos can be watched free. Complete the original case in a text editor, on paper or in a spreadsheet you already have. No paid course, exam or provider certificate is included.

Free UX Design Course: Research to Prototypes by Google
WikiFree: https://wikifree.com/courses/google-ux-design-free-video-course/
Official source: https://www.youtube.com/playlist?list=PLTZYG7bZ1u6oHnGp4Ib3n0y-CmFQdTW6r
Why selected: Selected research and prototype-testing lessons support discovery and validation.

Free Project Management Course by Google
WikiFree: https://wikifree.com/courses/google-project-management-free-video-course/
Official source: https://www.youtube.com/playlist?list=PLTZYG7bZ1u6puLWxUtqAjZkIB4dB_JFzk
Why selected: The stakeholder lesson helps connect requirements to the people affected and the decision owners.

Stage 1 selected lessons:

7. What is UX Research? (23:00)
https://www.youtube.com/watch?v=kQ_6faxhyIw&list=PLTZYG7bZ1u6oHnGp4Ib3n0y-CmFQdTW6r&index=7

8. The Importance of Empathy in UX Design (36:48)
https://www.youtube.com/watch?v=fqNAWyOOVfw&list=PLTZYG7bZ1u6oHnGp4Ib3n0y-CmFQdTW6r&index=8

Stage 2 selected lessons:

9. Communicating and Working with Stakeholders (23:52)
https://www.youtube.com/watch?v=jz7tPVDwb50&list=PLTZYG7bZ1u6puLWxUtqAjZkIB4dB_JFzk&index=9

Stage 5 selected lessons:

15. UX Research & Prototype Testing (41:02)
https://www.youtube.com/watch?v=PZ2hchA4Jvg&list=PLTZYG7bZ1u6oHnGp4Ib3n0y-CmFQdTW6r&index=15

REUSE
Original WikiFree teaching text and synthetic fixtures are supplied for personal learning and adaptation with attribution. Provider lessons remain on their original sites and retain their own terms. No provider certificate is included.