David Anderson 的《Agile Management for Software Engineering》里对这些话题有很深入透彻的讨论 http://www.amazon.com/Agile-Management-Software-Engineering-... ，《Software by Numbers》里也有类似的概念 http://www.amazon.com/Software-Numbers-Low-Risk-High-Return-... 我觉得很奇怪的是，为什么有人会认为固定时间和预算（而不是固定范围/需求）就必须采用不同的管理方式…
There are good thorough discussions of these topics in David Anderson's "Agile Management for Software Engineering" http://www.amazon.com/Agile-Management-Software-Engineering-... and similar concepts in Software by Numbers http://www.amazon.com/Software-Numbers-Low-Risk-High-Return-... I think it's odd to suppose that fixing time and budget as opposed to fixing scope/requirements needs to result in different management…
…但这或许完全是值得的。关于这个话题能说的还有很多，但在 HN 这种简短的帖子里很难一下子讲透。顺便提一句（FWIW），还有几本书或许也值得一读：1. 《Software by Numbers》[5] 2. 《The Economics of Iterative Software Development》[6] 3. 《Software as Capital》[7] [1]: https://en.wikipedia.org/wiki/Agile_contracts [2]: https://agilecontracts.org/ [3]: https://www.contractworks.com/blog/three-types-of-agile-cont...…
…But it might just be worth it. There's a lot more that could be said about this, but it's not easy to condense into a quick HN post. FWIW, a few books that might be worth reading as well include: 1. Software by Numbers[5] 2. The Economics of Iterative Software Development[6] 3. Software as Capital[7] [1]: https://en.wikipedia.org/wiki/Agile_contracts [2]: https://agilecontracts.org/ [3]: https://www.contractworks.com/blog/three-types-of-agile-cont...…
David Anderson 的《Agile Management for Software Engineering》里对这些话题有很深入透彻的讨论 http://www.amazon.com/Agile-Management-Software-Engineering-... ，《Software by Numbers》里也有类似的概念 http://www.amazon.com/Software-Numbers-Low-Risk-High-Return-... 我觉得很奇怪的是，为什么有人会认为固定时间和预算（而不是固定范围/需求）就必须采用不同的管理方式…
There are good thorough discussions of these topics in David Anderson's "Agile Management for Software Engineering" http://www.amazon.com/Agile-Management-Software-Engineering-... and similar concepts in Software by Numbers http://www.amazon.com/Software-Numbers-Low-Risk-High-Return-... I think it's odd to suppose that fixing time and budget as opposed to fixing scope/requirements needs to result in different management…
…但这或许完全是值得的。关于这个话题能说的还有很多，但在 HN 这种简短的帖子里很难一下子讲透。顺便提一句（FWIW），还有几本书或许也值得一读：1. 《Software by Numbers》[5] 2. 《The Economics of Iterative Software Development》[6] 3. 《Software as Capital》[7] [1]: https://en.wikipedia.org/wiki/Agile_contracts [2]: https://agilecontracts.org/ [3]: https://www.contractworks.com/blog/three-types-of-agile-cont...…
…But it might just be worth it. There's a lot more that could be said about this, but it's not easy to condense into a quick HN post. FWIW, a few books that might be worth reading as well include: 1. Software by Numbers[5] 2. The Economics of Iterative Software Development[6] 3. Software as Capital[7] [1]: https://en.wikipedia.org/wiki/Agile_contracts [2]: https://agilecontracts.org/ [3]: https://www.contractworks.com/blog/three-types-of-agile-cont...…