Back to Details

job-stories

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Job Stories

Job Stories

Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format. Generates stories with detailed acceptance criteria focused on user situations and outcomes.
Use when: Writing job stories, expressing user situations and motivations, creating JTBD-style backlog items, or focusing on user context rather than roles.
Arguments:
  • $PRODUCT
    : The product or system name
  • $FEATURE
    : The new feature to break into job stories
  • $DESIGN
    : Link to design files (Figma, Miro, etc.)
  • $CONTEXT
    : User situations or job scenarios
使用“当[场景]时，我想要[动机]，以便我能够[成果]”的格式创建工作故事。生成的故事将包含聚焦于用户场景与成果的详细验收标准。
适用场景： 撰写工作故事、表达用户场景与动机、创建JTBD风格的待办事项，或是关注用户上下文而非角色的场景。
参数：
  • $PRODUCT
    ：产品或系统名称
  • $FEATURE
    ：需拆解为工作故事的新功能
  • $DESIGN
    ：设计文件链接（Figma、Miro等）
  • $CONTEXT
    ：用户场景或工作情境

Step-by-Step Process

分步流程

  1. Identify user situations that trigger the need
  2. Define motivations underlying the user's behavior
  3. Clarify outcomes the user wants to achieve
  4. Apply JTBD framework: Focus on the job, not the role
  5. Create acceptance criteria that validate the outcome is achieved
  6. Use observable, measurable language
  7. Link to design mockups or prototypes
  8. Output job stories with detailed acceptance criteria
  1. 识别触发需求的用户场景
  2. 定义用户行为背后的动机
  3. 明确用户期望达成的成果
  4. 应用JTBD框架：聚焦工作需求，而非用户角色
  5. 创建可验证成果是否达成的验收标准
  6. 使用可观察、可衡量的表述
  7. 关联设计原型或线框图
  8. 输出附带详细验收标准的工作故事

Story Template

故事模板

Title: [Job outcome or result]
Description: When [situation], I want to [motivation], so I can [outcome].
Design: [Link to design files]
Acceptance Criteria:
  1. [Situation is properly recognized]
  2. [System enables the desired motivation]
  3. [Progress or feedback is visible]
  4. [Outcome is achieved efficiently]
  5. [Edge cases are handled gracefully]
  6. [Integration and notifications work]
标题： [工作成果或结果]
描述： 当[场景]时，我想要[动机]，以便我能够[成果]。
设计： [设计文件链接]
验收标准：
  1. [场景被正确识别]
  2. [系统支持所需的动机实现]
  3. [进度或反馈可见]
  4. [成果高效达成]
  5. [边缘情况被妥善处理]
  6. [集成与通知功能正常运作]

Example Job Story

示例工作故事

Title: Track Weekly Snack Spending
Description: When I'm preparing my weekly allowance for snacks (situation), I want to quickly see how much I've spent so far (motivation), so I can make sure I don't run out of money before the weekend (outcome).
Design: [Figma link]
Acceptance Criteria:
  1. Display Spending Summary with 'Weekly Spending Overview' section
  2. Real-Time Update when expense logged
  3. Progress Indicator (progress bar showing 0-100% of weekly budget)
  4. Remaining Budget Highlight in prominent color
  5. Detailed Spending Log with breakdown by category
  6. Notifications at 80% budget threshold
  7. Weekend-Specific Reminder at 90% by Thursday evening
  8. Easy Access and Navigation to detailed breakdown
标题： 追踪每周零食支出
描述： 当我在为每周的零食预算做准备时（场景），我想要快速查看迄今为止的支出金额（动机），以便确保周末前不会没钱（成果）。
设计： [Figma链接]
验收标准：
  1. 显示支出摘要，包含“每周支出概览”板块
  2. 记录支出时实时更新
  3. 进度指示器（显示每周预算0-100%的进度条）
  4. 剩余预算以醒目颜色突出显示
  5. 按类别细分的详细支出记录
  6. 预算达到80%时触发通知
  7. 周四晚预算达到90%时发送周末专属提醒
  8. 可轻松访问和导航至详细支出明细

Output Deliverables

输出交付物

  • Complete set of job stories for the feature
  • Each story follows the 'When...I want...so I can' format
  • 6-8 acceptance criteria focused on outcomes
  • Stories emphasize user situations and motivations
  • Clear links to design and prototypes
  • 针对该功能的完整工作故事集
  • 每个故事遵循“当...我想要...以便我能够...”的格式
  • 6-8条聚焦成果的验收标准
  • 故事重点突出用户场景与动机
  • 清晰关联设计与原型

Further Reading

延伸阅读