① Writing Order
② Term Glossary
③ Reading the Examples
④ Interview Questions (ask and write ...
⑤ Functional Requirements (write as "...
⑥ Non-Functional: Speed
⑦ Non-Functional: Hours of Use
⑧ Non-Functional: Data to Protect
⑩ Open Questions (ask what board ⑨ ca...
⑪ Today's Scope (write it in one sent...
⑫ What Was Agreed (show the requester...
⑬ What Was Dropped
⑭ For Next Time
⑮ Schedule Table (match it to the tas...
⑯ Rules for Change Requests
Requirements Inte...
How to use (4 pag...
Purpose & wha...
Requirements &...
Unclear points &a...
Open questions &a...
1/4
Learn the purpose
Ctrl+F / ⌘F : 2/4...
→ 2/4
2/4
List the requirem...
↙ 3/4
Page 1 to ask, page 2 to list, page 3 to choose, page 4 to agr ee Write answers on board ④ in the requester's own words Leave unclear points in "unclear points," then confirm them on board ⑩ Functional requirement = what the system can do. e.g. See all orders in one list Non-functional requirement = qualities like speed or hours of use. e.g. Opens within 3 seconds MoSCoW is a way to sort what to build into 4 groups, used on b oard ⑨ "e.g." shows how to fill it in - replace it with your own requ est The examples picture a small shop that takes orders online Leave out anything you can't share, like company names or deal figures To ask
Answer heard
Unclear points
Purpose
What's it for, and what changes once it's done? e.g. Stop mixing up order copies e.g. How fast "fast" needs to be is still unclear Who uses it
Who uses it, how many, and where? e.g. 1 manager and 3 staff, on the shop's computer e.g. Unclear if it needs to work on phones Current trouble
What's the biggest problem right now? e.g. Mixing up 2-3 orders a week e.g. Haven't asked why the mix-ups happen Current process
How is it handled today? e.g. Orders come by email, copied by hand into a spreadsh eet e.g. Are there orders that come in some other way than em ail? Deadline & li...
By when, and under what conditions? e.g. Needed from April. Keep taking email orders too e.g. Can it run on the current computer as-is? Who uses it
What it can do
Answer it came from
Feature 1
e.g. Manager e.g. Can see today's orders in one list e.g. The board ④ current process Feature 2
e.g. Staff e.g. Can change an order's status to "shipped" e.g. The board ④ current trouble Feature 3
e.g. Customer e.g. Can get an email when their order arrives e.g. The board ④ purpose Feature 4
e.g. Manager e.g. Can export orders to a spreadsheet file e.g. The board ④ deadline & limits Feature 5
Write who uses it Write it as "can..." Write which board ④ answer it came from e.g. Opens within 3 seconds, even during the 9 a.m. order rush e.g. Stays fast with 4 people using it at once Use a number of seconds or people, not just "fast" e.g. Available every day from 8 a.m. to 10 p.m. e.g. Taken down for maintenance once a month, at night only Also write who to contact if it goes down e.g. Only the manager and staff can see customer addresses and phone numbers e.g. Log in with a password before using it Write only what to protect - leave how to the dev team 3/4
Set today's scope
→ 4/4
4/4
Agree with the re...
⑨ Sort with MoSCo...
Must Required e.g. Can see today's orders in one list e.g. Opens within 3 seconds, even at 9 a.m . Only what makes this round pointless witho ut it Should Worth having e.g. Can change an order's status e.g. Can email customers when orders arriv e Important, but you can still launch withou t it Could Nice to have e.g. Can export to a spreadsheet file e.g. Easy to read on a phone Do it if there's time left over Won't Not this time e.g. Importing 3 years of past orders e.g. Managing stock Decided not to do this round (copy to ⑬) Ask who
Deadline
Answer
Works on phones
e.g. Manager e.g. By the next meeting e.g. Staff want it on phones too - stays a Could Phone orders
e.g. Staff e.g. This week e.g. About 5 phone orders a month Start date
e.g. Purchasing lead e.g. By the next meeting e.g. Settled on April 1 Keeping order rec...
e.g. Manager e.g. This week e.g. Keep orders for 1 year Today's scope e.g. Build enough for the manager and staff to see email orders in one list and change their status, without copying by hand Sign of done e.g. The manager went a week checking orders without copying the m to a spreadsheet Unclear edge cases e.g. Unclear if "change status" covers returns too - carried to ⑭ e.g. Agreed to build the board ⑪ scope (date __/__) e.g. Opens within 3 seconds, even at 9 a.m. e.g. Starts April 1 Read it aloud to the requester to check no wording is off e.g. Importing 3 years of past orders e.g. Managing stock Copy the Won't items from ⑨ as-is Add a short reason for dropping each one e.g. How to enter phone orders (board ⑩ found about 5 a month) e.g. Whether returns fall inside scope (the ⑪ edge case) Write what to decide at the next meeting Also write who brings the answer Step 1
Step 2
Step 3
Confirm purpose
e.g. Set the meeting date e.g. Send the board ④ questions ahead of time e.g. Write the answers on board ④ List requirements
e.g. Write 5 requirements on board ⑤ e.g. Fill in numbers on boards ⑥-⑧ e.g. Show it to the dev team Agree scope
e.g. Sort into 4 columns on board ⑨ e.g. Ask board ⑩ questions e.g. Write board ⑪ in one sentence Final check
e.g. Read boards ⑫-⑭ with the requester e.g. Record the agreement date e.g. Move the task to "Agreed" When a new request comes in e.g. Go back to board ⑨ and re-sort. If Must grows, move one ite m down to Should Not decided on this board Contractual liability and estimates aren't decided here - confir m those separately with your own team Sharing with the dev team e.g. The dev team works from the same board and adds an owner an d deadline to each task → 2/4
List the requirem...
↙ 3/4
Set today's scope
→ 4/4
Agree with the re...
Drag to move, scroll to zoom
