npx skills add https://github.com/danhvb/my-ba-skills --skill 'Agile BA Practices'指导 AI 助手在敏捷和混合方法论中应用业务分析实践,在轻量级文档与全面分析之间取得平衡。
| 方面 | 传统业务分析师 | 敏捷业务分析师 |
|---|---|---|
| 文档 | 前期全面详尽 | 刚刚好,及时完成 |
| 需求 | 开发前完成 | 涌现式,不断演进 |
| 交付物 | 业务需求文档、功能需求规格说明书、用例 | 用户故事、验收标准 |
| 方法 | 瀑布式/分阶段 | 迭代式/增量式 |
| 反馈 | 项目结束时 | 持续进行,每个冲刺 |
| 变更 | 正式的变更控制 | 拥抱变更 |
冲刺计划 :
冲刺期间 :
冲刺评审 :
冲刺回顾 :
待办事项列表细化 :
结构 :
Epic > Feature > User Story > Task
示例 :
Epic: Customer Self-Service Portal
├── Feature: Account Management
│ ├── User Story: View profile
│ ├── User Story: Update profile
│ └── User Story: Change password
├── Feature: Order History
│ ├── User Story: View orders
│ └── User Story: Track shipments
└── Feature: Support
├── User Story: Submit ticket
└── User Story: View FAQs
**Title**: [简短、描述性的标题]
As a [用户角色]
I want [目标]
So that [收益]
**Acceptance Criteria**:
- Given... When... Then...
- Given... When... Then...
**Notes**: [技术备注、线框图链接]
**Story Points**: [估算值]
故事就绪时:
故事完成时:
何时编写文档 :
何时保持精简 :
| 传统方式 | 敏捷替代方案 |
|---|---|
| 100 页的业务需求文档 | 1 页的项目简介 + 待办事项列表 |
| 详细的功能需求规格说明书 | 用户故事 + 验收标准 |
| 用例文档 | 验收场景 |
| 数据字典 | 故事中的实体定义 |
| 测试计划 | 自动化测试 + 完成定义 |
故事拆分 :
估算 :
与产品负责人确定优先级 :
一种可视化技术,用于沿着用户旅程组织用户故事。
Activities (顶层行)
↓
Tasks (第二行)
↓
Details/Stories (底层行,按优先级)
Browse Products → Add to Cart → Checkout → Order Tracking
↓ ↓ ↓ ↓
View catalog Add item Shipping View status
Search products Update qty Payment Track shipment
Filter/sort Save for later Review order Get notifications
MVP ─────────────────────────────────────────────────
View catalog Add item Shipping View status
Search Update qty Payment
Release 2 ───────────────────────────────────────────
Filter/sort Save for later Review order Track shipment
瀑布式元素 :
敏捷元素 :
Discovery (2-4 周): 需求、业务需求文档、架构
↓
Sprint 0: 设置、详细设计、初始故事
↓
Sprints 1-N: 敏捷开发
↓
UAT Sprint: 用户验收测试
↓
Go-live: 部署、上线后支持
✅ 面对面沟通优于文档 ✅ 可工作的软件优于详尽的文档 ✅ 每日站会保持对齐 ✅ 尽早且频繁地演示
✅ 拥抱变更 ✅ 及时细化 ✅ 协作式细化 ✅ 可测试的验收标准
✅ 编写刚刚好的文档 ✅ 保持文档最新 ✅ 使文档易于访问 ✅ 尽可能自动化
✅ 与产品负责人紧密合作 ✅ 对团队保持可用 ✅ 促进而非命令 ✅ 学习技术基础知识
❌ 前期大设计 : 开发前进行过多分析 ❌ 需求倾倒 : 在没有协作的情况下编写故事 ❌ 缺席的业务分析师 : 冲刺期间不可用 ❌ 镀金 : 过度记录所有内容 ❌ 范围否认 : 不根据需求变化进行调整
每周安装次数
0
代码仓库
首次出现
1970年1月1日
安全审计
Guide AI assistants in applying BA practices within Agile and Hybrid methodologies, balancing lightweight documentation with comprehensive analysis.
| Aspect | Traditional BA | Agile BA |
|---|---|---|
| Documentation | Comprehensive upfront | Just enough, just in time |
| Requirements | Complete before dev | Emergent, evolving |
| Deliverables | BRD, FRS, Use Cases | User stories, acceptance criteria |
| Approach | Waterfall/phases | Iterative/incremental |
| Feedback | End of project | Continuous, each sprint |
| Change | Formal change control | Embrace change |
:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
During Sprint :
Sprint Review :
Sprint Retrospective :
Backlog Refinement :
Structure :
Epic > Feature > User Story > Task
Example :
Epic: Customer Self-Service Portal
├── Feature: Account Management
│ ├── User Story: View profile
│ ├── User Story: Update profile
│ └── User Story: Change password
├── Feature: Order History
│ ├── User Story: View orders
│ └── User Story: Track shipments
└── Feature: Support
├── User Story: Submit ticket
└── User Story: View FAQs
**Title**: [Short, descriptive title]
As a [user role]
I want [goal]
So that [benefit]
**Acceptance Criteria**:
- Given... When... Then...
- Given... When... Then...
**Notes**: [Technical notes, wireframe links]
**Story Points**: [Estimate]
Story is Ready when:
Story is Done when:
Write documentation when :
Keep lean when :
| Traditional | Agile Alternative |
|---|---|
| 100-page BRD | 1-page project brief + backlog |
| Detailed FRS | User stories + acceptance criteria |
| Use Case documents | Acceptance scenarios |
| Data dictionary | Entity definitions in stories |
| Test plan | Automated tests + DoD |
Story Splitting :
Estimation :
Prioritization with PO :
Visual technique to organize user stories along the user journey.
Activities (top row)
↓
Tasks (second row)
↓
Details/Stories (lower rows, by priority)
Browse Products → Add to Cart → Checkout → Order Tracking
↓ ↓ ↓ ↓
View catalog Add item Shipping View status
Search products Update qty Payment Track shipment
Filter/sort Save for later Review order Get notifications
MVP ─────────────────────────────────────────────────
View catalog Add item Shipping View status
Search Update qty Payment
Release 2 ───────────────────────────────────────────
Filter/sort Save for later Review order Track shipment
Waterfall Elements :
Agile Elements :
Discovery (2-4 weeks): Requirements, BRD, Architecture
↓
Sprint 0: Setup, detailed design, initial stories
↓
Sprints 1-N: Agile development
↓
UAT Sprint: User acceptance testing
↓
Go-live: Deployment, hypercare
✅ Face-to-face over documentation ✅ Working software over comprehensive docs ✅ Daily standups for alignment ✅ Demo early and often
✅ Embrace change ✅ Just-in-time elaboration ✅ Collaborative refinement ✅ Testable acceptance criteria
✅ Write just enough ✅ Keep it current ✅ Make it accessible ✅ Automate when possible
✅ Work closely with PO ✅ Be available to team ✅ Facilitate, don't dictate ✅ Learn technical basics
❌ Big Design Up Front : Too much analysis before development ❌ Requirements Dumping : Writing stories without collaboration ❌ Absent BA : Not available during sprints ❌ Gold Plating : Over-documenting everything ❌ Scope Denial : Not adapting to changing requirements
Weekly Installs
0
Repository
First Seen
Jan 1, 1970
Security Audits
飞书日程待办摘要工作流:AI自动生成每日/每周开工报告,提升个人生产力
24,200 周安装
前端动画设计指南:提升用户体验的微交互与动效策略
38,600 周安装
跨平台设计适配指南:移动端、桌面端、平板、打印及邮件适配策略与实施方法
38,800 周安装
前端打磨(Polish)终极指南:提升产品细节与用户体验的系统化检查清单
39,900 周安装
Web应用测试指南:使用Python Playwright自动化测试本地Web应用
39,500 周安装
Azure Cloud Migrate:AWS Lambda到Azure Functions迁移工具 - 微软官方评估与代码迁移
38,700 周安装
Excel财务建模规范与xlsx文件处理指南:专业格式、零错误公式与数据分析
42,900 周安装