[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"site-contact":3,"blog:en::sprint planning: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":37},"how-to-manage-bugs-and-sprints-in-software-outsourcing","practice","How to Manage Bugs and Sprints in Software Outsourcing Projects","Bugs in outsourced projects are rarely a technical problem — they're a process problem: too many entry points, missing fields, sprints with zero buffer, and defects mixed with change requests. Six rules we settled on after enough painful releases, all directly copyable.",null,[32,33,34,35,36],"bug management","sprint planning","software outsourcing","time tracking","client portal","2026-11-01T18:00:41"]