Path-to-production mapping

Path-to-production mapping is a standard practice at Thoughtworks that has become newly relevant with the advent of agentic coding. Increased code throughput can expose or amplify bottlenecks elsewhere in the path-to-production, making it essential for teams to optimize the end-to-end flow of software rather than coding speed alone. The activity is most often done in a workshop that includes everyone involved in designing, developing, releasing and operating the software. First, participants list the steps in the process on a whiteboard, from the developer workstation all the way to production. In a second pass, they capture pain points. The activity is often eye-opening, as participants identify delays, risks and inconsistencies they weren’t previously aware of. Tackling those bottlenecks is key to improving overall delivery productivity.

尽管 生产路径图 自从持续交付被编著时在Thoughtworks就是一种近乎普遍的实践，但是我们经常会遇到一些不熟悉生产路径图实践的组织。这一活动经常由一群跨功能团队的人——包括参与设计、开发、发布与运营软件的所有人——在工作坊中完成，他们围在同一张白板前面（或者是一个虚拟的等价物）。首先，按照顺序把流程的步骤罗列出来，从开发阶段一直到发布上产的所有路径。然后，主持一个会议来获取更多的信息和痛点。我们最常见的技术是基于价值流图，尽管有很多具有同等价值的流程图变种。这项活动经常会让参与者眼界大开，因为他们识别出了延迟，风险和不一致的地方，并且可以用可视化的陈述来持续改进构建和部署的流程。我们认为这是一项很基本的技术，所以当我们发现在之前的技术雷达中我们没有提到它的时候，我们感到非常惊讶。