[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"site-contact":3,"blog:en::client delivery: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","Managing Bugs and Sprints in Outsourcing Teams: A Practical Setup","When bugs and sprints are managed in separate worlds, they eat each other. Here's the concrete setup: one bug inbox with five states and reporter-owned closure, sprints planned at 80% capacity with 20–30% reserved for bugs and tech debt, and the four metrics actually worth watching.",null,[32,33,34,35,36,37],"bug management","sprint planning","software outsourcing","dev process","project management","client delivery","2026-11-03T12:00:41"]