qe-consultancy-practices
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseConsultancy Practices
咨询实践
<default_to_action>
When consulting on quality:
- LISTEN FIRST: Understand their context before prescribing solutions
- DISCOVER: What's the pain? What have they tried? What are constraints?
- PRIORITIZE: Impact/effort matrix - high impact, low effort first
- TRANSFER KNOWLEDGE: Leave them better, not dependent on you
- MEASURE: Define success metrics upfront, track weekly
Engagement Types:
- Assessment (1-4 weeks): Discover, analyze, recommend
- Transformation (3-12 months): Implement new practices
- Advisory (ongoing): Strategic guidance, course-correct
- Crisis (1-4 weeks): Fix critical issues blocking production
Key Questions:
- "Walk me through your last deployment"
- "Tell me about a recent bug that escaped to production"
- "If you could fix one thing, what would it be?" </default_to_action>
<default_to_action>
在开展质量相关咨询时：
- 先倾听：在给出解决方案前先充分了解对方的上下文
- 调研：核心痛点是什么？他们已经尝试过哪些方案？存在哪些约束条件？
- 优先级排序：使用影响/工作量矩阵，优先推进高影响、低工作量的事项
- 知识传递：帮助团队实现能力提升，而非让他们依赖你
- 效果衡量：提前定义成功指标，按周跟踪进度
服务类型：
- 评估（1-4周）：调研、分析、输出改进建议
- 转型（3-12个月）：落地新的研发质量实践
- 顾问咨询（长期）：提供战略指导、方向纠偏
- 危机处理（1-4周）：修复阻塞生产运行的严重问题
核心调研问题：
- "给我讲一下你们最近一次部署的全流程"
- "跟我说说最近漏到生产环境的bug的具体情况"
- "如果只能先解决一个问题，你会选择哪个？" </default_to_action>
Quick Reference Card
快速参考卡
The Consulting Process
咨询流程
| Phase | Duration | Goal | Deliverable |
|---|---|---|---|
| Discovery | Week 1-2 | Understand context | Interview notes, observations |
| Analysis | Week 2-3 | Identify root causes | Impact/effort matrix |
| Recommendations | Week 3-4 | Present findings | Report with roadmap |
| Implementation | Month 2-6+ | Execute changes | Working system, trained team |
| Transition | Final month | Ensure self-sufficiency | Handover docs |
| 阶段 | 时长 | 目标 | 交付物 |
|---|---|---|---|
| 调研 | 第1-2周 | 充分了解业务和研发上下文 | 访谈记录、观察结论 |
| 分析 | 第2-3周 | 定位问题根因 | 影响/工作量矩阵 |
| 建议输出 | 第3-4周 | 同步调研结论和改进方向 | 附带落地路线图的报告 |
| 落地执行 | 第2-6个月及以上 | 推进变更落地 | 可正常运行的系统、经过培训的团队 |
| 交接过渡 | 最后1个月 | 确保团队具备自主运营能力 | 完整的交接文档 |
Impact/Effort Matrix
影响/工作量矩阵
| Priority | What | Action |
|---|---|---|
| High Impact, Low Effort | Quick wins | Do first |
| High Impact, High Effort | Major initiatives | Plan carefully |
| Low Impact, Low Effort | Nice-to-haves | If time permits |
| Low Impact, High Effort | Distractions | Skip |
| 优先级 | 事项类型 | 执行策略 |
|---|---|---|
| 高影响、低工作量 | 快速赢项 | 优先执行 |
| 高影响、高工作量 | 核心项目 | 谨慎规划后落地 |
| 低影响、低工作量 | 锦上添花项 | 时间充裕时再做 |
| 低影响、高工作量 | 干扰项 | 直接跳过 |
Common Patterns
常见场景模式
"We Need Test Automation"
"我们需要测试自动化"
What they say: "We need test automation"
What they mean: "Manual testing is too slow/expensive"
Discovery: How long is regression? What's deployment frequency?
Typical Finding: They need faster feedback, not "automation"
Recommendation:
- Unit tests for new code (TDD)
- Smoke tests for critical paths
- Keep exploratory for discovery
- Build automation incrementally
对方表述： "我们需要测试自动化"
实际诉求： "手工测试效率太低、成本太高"
调研方向： 全量回归测试需要多久？部署频率是多少？
典型结论： 他们需要的是更快的反馈效率，而非单纯的"自动化"本身
改进建议：
- 新代码要求补充单元测试（TDD）
- 核心链路补充冒烟测试
- 保留探索性测试用于未知问题挖掘
- 逐步迭代构建自动化体系
"Fix Our Quality Problem"
"解决我们的质量问题"
What they say: "We have too many bugs"
What they mean: "Something is broken but we don't know what"
Discovery: Where found? What types? When introduced?
Typical Finding: No test strategy, testing too late, poor feedback loops
Recommendation:
- Shift testing left
- Improve coverage on critical paths
- Speed up CI/CD feedback
- Better requirements/acceptance criteria
对方表述： "我们的bug太多了"
实际诉求： "系统存在问题，但我们不知道根因是什么"
调研方向： bug一般在哪个环节被发现？属于什么类型？通常在哪个阶段被引入？
典型结论： 缺少清晰的测试策略、测试介入时机过晚、反馈链路效率低
改进建议：
- 测试左移
- 提升核心链路的测试覆盖率
- 加快CI/CD反馈速度
- 优化需求和验收标准的明确度
"We Want to Scale Quality"
"我们想要规模化落地质量体系"
What they say: "Growing fast, quality can't keep up"
What they mean: "Can't hire enough QA fast enough"
Discovery: Current QA:Dev ratio? Where's QA spending time?
Typical Finding: QA is bottleneck - manual regression, gatekeeping
Recommendation:
- Make QA strategic, not tactical
- Developers own test automation
- QA focuses on exploratory, risk analysis
- Use agentic approaches for scale
对方表述： "业务增长太快，质量管控跟不上"
实际诉求： "没法快速招聘到足够的QA人员支撑业务发展"
调研方向： 当前QA和开发的人员比例是多少？QA的时间主要消耗在哪些工作上？
典型结论： QA成为流程瓶颈，大部分时间消耗在手工回归、流程把关等事务性工作上
改进建议：
- 让QA聚焦战略层面工作，而非事务性执行工作
- 开发人员负责测试自动化落地
- QA聚焦探索性测试、风险分析等核心工作
- 采用agentic相关方案实现质量管控能力规模化
Anti-Patterns
反模式
| Anti-Pattern | Problem | Better |
|---|---|---|
| Cookie-Cutter | Same solution everywhere | Context-specific recommendations |
| Tool Pusher | Recommend expensive tools | Tools that solve actual problems |
| Process Nazi | Impose rigid process | Lightweight, fits their culture |
| Permanent Fixture | Never leave, create dependency | Work toward them not needing you |
| Blame Game | Point fingers at people | Fix systems, not blame people |
| 反模式 | 存在问题 | 更优做法 |
|---|---|---|
| 千篇一律 | 所有场景都套用同一套解决方案 | 基于客户实际上下文输出定制化建议 |
| 工具推销者 | 优先推荐昂贵的商业化工具 | 选择能解决实际问题的适配工具 |
| 流程至上主义 | 强行推行僵化的管控流程 | 输出轻量、适配客户团队文化的流程 |
| 永久驻场依赖 | 长期驻场，制造客户对你的依赖 | 以客户最终可以自主运营为目标推进工作 |
| 甩锅导向 | 出现问题先指责个人 | 优先优化体系流程，而非指责个人 |
Difficult Situations
难应对场景处理方案
"We already tried that"
→ "Tell me what you tried and what didn't work" (learn from their experience)
"Our context is special"
→ "Help me understand what makes yours special" (they might be right, or making excuses)
"We don't have budget/time"
→ "What's the cost of not fixing this? Let's start small" (show ROI)
"That won't work here"
→ "What specific constraints? Let's adapt" (find what WILL work)
"我们已经试过这个方法了"
→ "跟我说说你们当时的落地细节，以及哪些地方没有达到预期？"（从客户的过往经验中学习）
"我们的情况比较特殊"
→ "帮我了解下你们场景的特殊点是什么？"（客户可能确实有特殊情况，也可能是在找借口）
"我们没有预算/时间做这个"
→ "可以先算一下不解决这个问题的代价是多少？我们可以先从小范围试点开始"（向客户展示投入产出比）
"这个方案在我们这里行不通"
→ "有什么具体的约束条件吗？我们可以基于实际情况调整方案"（共同探索真正可行的落地方案）
Agent Integration
Agent集成
typescript
// Automated codebase assessment
const assessment = await Task("Assess Codebase", {
scope: 'client-project/',
depth: 'comprehensive',
reportFormat: 'executive-summary'
}, "qe-quality-analyzer");
// Returns: { qualityScore, testCoverage, technicalDebt, recommendations }
// ROI analysis for quality initiatives
const roi = await Task("Calculate ROI", {
currentState: { defectEscapeRate: 0.15, mttr: 48 },
proposedImprovements: ['test-automation', 'ci-cd-pipeline'],
timeframe: '6-months'
}, "qe-quality-analyzer");
// Returns: { estimatedCost, estimatedSavings, paybackPeriod }typescript
// Automated codebase assessment
const assessment = await Task("Assess Codebase", {
scope: 'client-project/',
depth: 'comprehensive',
reportFormat: 'executive-summary'
}, "qe-quality-analyzer");
// Returns: { qualityScore, testCoverage, technicalDebt, recommendations }
// ROI analysis for quality initiatives
const roi = await Task("Calculate ROI", {
currentState: { defectEscapeRate: 0.15, mttr: 48 },
proposedImprovements: ['test-automation', 'ci-cd-pipeline'],
timeframe: '6-months'
}, "qe-quality-analyzer");
// Returns: { estimatedCost, estimatedSavings, paybackPeriod }Agent Coordination Hints
Agent协调提示
Memory Namespace
内存命名空间
aqe/consultancy/
├── assessments/* - Client assessments
├── recommendations/* - Prioritized recommendations
├── roi-analysis/* - ROI calculations
└── progress/* - Implementation trackingaqe/consultancy/
├── assessments/* - Client assessments
├── recommendations/* - Prioritized recommendations
├── roi-analysis/* - ROI calculations
└── progress/* - Implementation trackingFleet Coordination
集群协调
typescript
const consultingFleet = await FleetManager.coordinate({
strategy: 'client-engagement',
agents: [
'qe-quality-analyzer', // Assess current state
'qe-regression-risk-analyzer', // Risk assessment
'qe-quality-gate', // Define quality gates
'qe-deployment-readiness' // Deployment maturity
],
topology: 'hierarchical'
});typescript
const consultingFleet = await FleetManager.coordinate({
strategy: 'client-engagement',
agents: [
'qe-quality-analyzer', // Assess current state
'qe-regression-risk-analyzer', // Risk assessment
'qe-quality-gate', // Define quality gates
'qe-deployment-readiness' // Deployment maturity
],
topology: 'hierarchical'
});Related Skills
相关技能
- quality-metrics - Metrics for client reporting
- risk-based-testing - Client risk assessment
- holistic-testing-pact - Comprehensive strategy
- quality-metrics - 用于客户报告的质量指标
- risk-based-testing - 客户风险评估方法
- holistic-testing-pact - 全面质量管控策略
Remember
核心原则
Good consulting is about empowering teams, not creating dependency. Your success is measured by them not needing you anymore - while still wanting to work with you again.
Best compliment: "We've got this now, but when we tackle X next year, we're calling you."
Be honest. Be helpful. Be context-driven. Leave them better.
好的咨询本质是赋能团队，而非制造依赖。 你成功的衡量标准是客户最终不再需要你，但仍然愿意未来和你继续合作。
最好的客户评价： "我们现在已经能自主搞定了，但明年做X项目的时候，我们肯定还会找你。"
保持坦诚，切实解决问题，以实际场景为导向，帮助客户实现能力提升。