成果範例
標準版方案範例
Technical specification: booking website for a yoga studio
1. Project goals
- Let clients see the timetable and book a class in under one minute, from a phone.
- Sell class passes and memberships online.
- Cut the time staff spend on bookings from about 10 hours a week to under 2.
Success measures (3 months after launch): 70% of bookings made online; no-shows below 10%.
2. Users
| Role | What they need |
|---|---|
| Visitor | See classes, prices and teachers; buy a first-class trial |
| Client | Book and cancel classes, see remaining passes, join a waitlist |
| Teacher | See their own classes and the list of booked clients |
| Admin | Manage timetable, prices, passes, teachers and refunds |
3. Pages and screens
- Home: next classes today, trial offer, studio address.
- Timetable: week view, filters by class type, level, teacher and room.
- Class page: description, teacher, length, places left, Book button.
- Prices: single class, 5- and 10-class passes, monthly membership.
- Teachers: list and individual profiles.
- Account: upcoming bookings, history, passes, payment methods.
- Admin panel: timetable editor, client list, sales report.
4. Key features
4.1 Booking
- A client can book if they have a valid pass or pay for a single class.
- Class capacity is set per room (Room A: 18, Room B: 10).
- When a class is full, the client can join a waitlist; if a place opens, the first person in line gets it and receives an email and text message.
4.2 Cancellation
- Free cancellation up to 12 hours before class; the pass credit returns.
- Later cancellation or a no-show uses up the credit.
4.3 Payments
- Card payments through a payment provider chosen by the studio.
- Passes expire: 5-class after 2 months, 10-class after 3 months.
4.4 Notifications
- Booking confirmation, reminder 3 hours before class, waitlist updates.
5. Non-functional requirements
- Mobile-first; pages load in under 2 seconds on 4G.
- Works in the two latest versions of major browsers.
- Personal data stored in line with local data protection law.
6. Open questions
| # | Question | Who decides |
|---|---|---|
| 1 | Do teachers mark attendance in the app, or does the front desk? | Studio owner |
| 2 | Is a 2-week trial pass needed in addition to a single trial class? | Studio owner |
| 3 | Should the timetable be embedded on the current website or replace it? | Owner + developer |
| 4 | Which payment provider and text-message service are preferred? | Owner |
Client: Lotus Lane Yoga, a studio with 2 rooms, 9 teachers and about 60 classes a week. Today bookings go through direct messages and a paper sign-up sheet. Standard package: specification up to 10 pages. Excerpt below.
客戶與所有細節皆為虛構。
關於此服務
開發人員只會做工單上寫的，所以一個寫成「加入通知」的功能，可能讓人猜上一整週。我們會取得您為產品規劃的功能，寫成附 Given、When、Then 格式驗收條件的使用者故事，補上空狀態、錯誤與權限等邊界情況，並把大項目拆成團隊一個衝刺（sprint）內能完成的故事。您可以直接貼到 Jira、Linear、Trello 或 YouTrack。
包含內容
- 您會收到什麼一份依功能分組的使用者故事待辦清單，每則附驗收條件、邊界情況與待釐清問題，另有建議的優先順序，格式化文字可直接貼到您的追蹤工具。
- 使用者故事身為某角色，我想要，以便
- 驗收條件每則故事都有 Given、When、Then
- 邊界情況空狀態、錯誤、權限、限制
- 衝刺大小的項目大功能拆成小故事
- 優先順序先做什麼以及原因
服務流程
- 1需求說明您描述產品與功能
- 2撰寫我們撰寫故事、條件與邊界情況
- 3待辦清單您會收到可直接放進追蹤工具的故事
需要您提供的資料
產品與其使用者的簡短說明、您想新增的功能、現有版本的截圖或連結（若有），以及功能必須遵守的任何規則。
我們會詢問您：
- 產品是什麼，誰在使用？
- 故事要涵蓋哪些功能？
- 產品中有哪些使用者角色？
- 您使用哪個追蹤工具？
比較方案
付款保障
下單時付款，但只有在驗收成果後，款項才會撥付。
- 固定價格付款後，方案價格不會變動。
- 款項先行保留付款時，金額只會先保留，在您驗收後才會撥付給服務。
- 交付前檢查每份成果在交到您手上之前都會經過品質檢查，您也可以在驗收前於訂單頁面查看成果。
- 免費修改在需求說明範圍內，可依方案允許的次數提出修改。
- 3 天後自動驗收若您在交付後 3 天內未驗收也未提出修改，成果將自動驗收。若您在交付後於訂單聊天室留言，訂單會暫停自動驗收；我們回覆後，可能會重新起算 3 天，並會在聊天室中告知。
- 重新製作或全額退款若成果不符合您的需求說明且修改後仍未改善，或製作時間超過交付期限的兩倍，請在訂單聊天室留言：我們將重新製作，或全額退還款項。
常見問題
你們會估算故事點數嗎？
不會。估算屬於了解程式碼的您的團隊。我們會標出看起來偏大或有風險的故事，讓團隊優先討論。
可以為既有產品撰寫故事嗎？
可以。請以截圖或連結描述或展示目前的行為，我們會圍繞它撰寫新的故事。
你們可以幫我們匯入 Jira 嗎？
不行，我們不需要存取您的追蹤工具。每則故事的格式都可以直接貼成新工單。
沒有找到您要的答案？