问 HN：对齐税
1 分•作者: brihati•6 个月前
我最近和一些工程领导者交流，他们表达了担忧，认为导致项目延期的不仅仅是代码本身，还包括许多与代码相关的问题：
1. 工程团队与其他相关方之间的沟通协调问题，导致需求迟迟无法最终确定。
2. 冲刺中期需求变更，而这些变更在规划阶段并未考虑到，从而导致截止日期延后。
3. 对系统 X 最为了解的工程师休假或离职，导致决策延误。
4. 资深工程师在冲刺中期修改已批准的设计，因为发现已批准的设计存在缺陷。
5. 发现对其他团队的依赖，而这些团队正忙于其他紧急任务。
...等等
我很想知道贵公司的情况。你们团队经历过的最昂贵的协调失败是什么？给公司造成了多大的损失？
查看原文
I am having conversations with engineering leaders where they have expressed concerns that it's not only the code but a lot of other things around code:<p>1. Alignment between engineering teams and other stakeholders which causes the delay in finalising the requirements
2. Scope changing mid sprint, which was not accounted during planning, hence pushing deadlines
3. Engineers who have the most context of system X, is on leave or have left the company, hence decisions are delayed
4. Senior engineer changing the approved design mid sprint because of some flaws in approved design
5. Identified dependencies on other teams who have their hands tied up with other urgent tasks
.... & so on<p>Curious what this looks like at your company. What's the most expensive coordination failure your team has experienced? How much did it cost the company?