Convert three user stories into symptoms, and find what the story left out
Task
Practise step one of the method on real reports: turn a story into testable symptoms, identify what was not said, and write the question that would have produced it.
Steps
- Write
lab/method/stories.txtwith three fault reports in the words a user would use, one per line. - For each, write
lab/method/symptoms.csvwith headerstory,symptom,testable,how_to_observebreaking the story into at least three symptoms and marking which are testable as stated. - Write
lab/method/questions.csvwith headerstory,question,what_it_would_settlewith at least five questions per story, including one about what changed and one about who else is affected. - Write
lab/method/steps.csvwith headerstep,produces,what_the_next_step_needslisting the six steps in order plus documentation. - Write
lab/method/backup.mdstating which step the backup belongs to and why it cannot wait until the plan of action.
Verify
grep -c . lab/method/stories.txt
awk -F, 'NR>1 && NF>=4 {n++} END {print n" symptom(s)"}' lab/method/symptoms.csv
awk -F, 'NR>1 && tolower($3)=="no" {n++} END {print n+0" symptom(s) not testable as stated"}' lab/method/symptoms.csv
awk -F, 'NR>1 && NF>=3 {n++} END {print n" question(s)"}' lab/method/questions.csv
awk -F, 'NR>1 && NF>=3 {n++} END {print n" method step(s)"}' lab/method/steps.csv
grep -Eic 'identify|first|before' lab/method/backup.md
Three stories, nine or more symptoms with at least one not testable as stated, fifteen or more questions, seven method steps, and the backup note. If every symptom was testable as stated, the stories were written by a technician rather than in a user's words.
Notes
'What changed' is the single most productive question in this job, and users volunteer the answer only when asked directly. Its absence from a question list is the most common omission in this lab.
This is an independent study companion for CompTIA A+ Core 1 220-1201 and is not produced by or endorsed by CompTIA.