[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"site-contact":3,"blog:zh::外包研发:1":21},{"phone":4,"wechatId":5,"wechatQr":6,"wecomQr":7,"emails":8},"17744963663","","\u002Fqr\u002Fwechat.png","\u002Fqr\u002Fwecom.png",[9,13,17],{"labelZh":10,"labelEn":11,"email":12},"商务咨询","Sales","hi@dhthub.com",{"labelZh":14,"labelEn":15,"email":16},"客户服务","Support","service@dhthub.com",{"labelZh":18,"labelEn":19,"email":20},"联系 Peter","Peter","peter@dhthub.com",{"total":22,"page":22,"size":23,"list":24},1,12,[25],{"slug":26,"category":27,"title":28,"summary":29,"cover":30,"tags":31,"publishAt":38},"managing-bugs-and-sprints-in-outsourcing-teams-a-practical","practice","研发团队如何高效管理 BUG 和迭代：外包团队能落地的做法","外包团队的 BUG 和迭代一旦各管各的，就会互相挤占。这篇讲清楚三个具体做法：BUG 只设一个入口、五个状态，由提单人负责关闭；迭代按 80% 容量排期，并固定留出 20%~30% 给 BUG 和技术债；该盯的四个数字分别是哪些。",null,[32,33,34,35,36,37],"BUG管理","迭代管理","外包研发","研发流程","项目管理","客户交付","2026-11-03T12:00:41"]