《能力成熟度模型：软件过程改进指南》（The Capability Maturity Model: Guidelines for Improving the Software Process）里讲了很多这方面的内容。这本书现在绝版了，但二手卖得挺便宜，非常值得一读。https://www.amazon.com/gp/product/0201546647?ref%5F=sr%5F1%5... 还有……
Much of that is covered in "The Capability Maturity Model: Guidelines for Improving the Software Process". The book is out of print now but available fairly cheap and it's well worth reading. https://www.amazon.com/gp/product/0201546647?ref%5F=sr%5F1%5... And…
The thing to bear in mind is that not every organisation needs 'NASA-level' quality. IMHO The Capability Maturity Model is a must-read for everyone interested in professional software development. https://en.wikipedia.org/wiki/Capability_Maturity_Model_Inte...
…area of expertise, and I've experienced it working on a very large scale (tens of thousands of servers) rather than a bunch of hacking efforts at some company on the InterNet. https://www.amazon.com/Capability-Maturity-Model-Guidelines-... https://www.amazon.com/Managing-Software-Process-Watts-Humph...
…of the IT processes that borrow the word "kaizen". Even "continuous improvement" can be a loaded term with respect to responsibilities. The first time I ran across the term was dealing with CMM (the Capability Maturity Model). Once you are up to level 4 or 5 you are using metrics to improve your process in order to obtain continuous improvement. In every organization I've seen that attempted to achieve CMM level 4 or above,…
…but you can still ship. For example, level 2 is called "Managed Process". "Managed Process is distinguished by the degree to which the process is Managed". I'm not making this up. There's a book called Capability Maturity Model Integration, and this book, heavy enough to kill a human, is full of this sort of stuff. Reading it is impossible. http://www.yosefk.com/blog/extreme-programming-explained.htm...
I work on DoD projects with varying project reporting requirements. There are many methodologies and processes one can follow. I've experiences success with Capability Maturity Model Integration and Agile (others here have mentioned agile too). There's an ongoing "meeting of the minds" of merging CMMI with Agile in the defense space. For estimation, learning a bit of earned value…
《能力成熟度模型：软件过程改进指南》（The Capability Maturity Model: Guidelines for Improving the Software Process）里讲了很多这方面的内容。这本书现在绝版了，但二手卖得挺便宜，非常值得一读。https://www.amazon.com/gp/product/0201546647?ref%5F=sr%5F1%5... 还有……
Much of that is covered in "The Capability Maturity Model: Guidelines for Improving the Software Process". The book is out of print now but available fairly cheap and it's well worth reading. https://www.amazon.com/gp/product/0201546647?ref%5F=sr%5F1%5... And…
关键得记住，并不是每个组织都需要达到“NASA 级别”的质量。依我看，对于每个对专业软件开发感兴趣的人来说，《能力成熟度模型》都是必读书。https://en.wikipedia.org/wiki/Capability_Maturity_Model_Inte...
The thing to bear in mind is that not every organisation needs 'NASA-level' quality. IMHO The Capability Maturity Model is a must-read for everyone interested in professional software development. https://en.wikipedia.org/wiki/Capability_Maturity_Model_Inte...
……我的专业领域，而且我经历的是超大规模环境（数万台服务器）下的运作，而不是互联网上某些公司搞的那套东拼西凑的 hacking。https://www.amazon.com/Capability-Maturity-Model-Guidelines-... https://www.amazon.com/Managing-Software-Process-Watts-Humph...
…area of expertise, and I've experienced it working on a very large scale (tens of thousands of servers) rather than a bunch of hacking efforts at some company on the InterNet. https://www.amazon.com/Capability-Maturity-Model-Guidelines-... https://www.amazon.com/Managing-Software-Process-Watts-Humph...
……那些借用了“改善”（kaizen）这个词的 IT 流程之一。就连“持续改进”在职责划分上也可能是一个含义复杂的词。我第一次碰到这个词是在处理 CMM（能力成熟度模型）的时候。一旦达到 4 级或 5 级，你就会用指标来改进流程，以实现持续改进。在我见过的所有试图达到 CMM 4 级或以上的组织里，……
…of the IT processes that borrow the word "kaizen". Even "continuous improvement" can be a loaded term with respect to responsibilities. The first time I ran across the term was dealing with CMM (the Capability Maturity Model). Once you are up to level 4 or 5 you are using metrics to improve your process in order to obtain continuous improvement. In every organization I've seen that attempted to achieve CMM level 4 or above,…
……但你依然能交付。举个例子，2 级被称为“已管理流程”（Managed Process）。“已管理流程的特征在于流程被管理的程度”。真不是我编的。有本叫《能力成熟度模型集成》的书，厚重得能砸死人，里面全是这种鬼话。根本没法读。http://www.yosefk.com/blog/extreme-programming-explained.htm...
…but you can still ship. For example, level 2 is called "Managed Process". "Managed Process is distinguished by the degree to which the process is Managed". I'm not making this up. There's a book called Capability Maturity Model Integration, and this book, heavy enough to kill a human, is full of this sort of stuff. Reading it is impossible. http://www.yosefk.com/blog/extreme-programming-explained.htm...
我在做国防部（DoD）的项目，各个项目的汇报要求都不一样。你可以遵循的方法论和流程有很多。我在结合使用能力成熟度模型集成（CMMI）和敏捷（这里其他人也提到了敏捷）方面有过成功的经验。在国防领域，现在有一场将 CMMI 与敏捷相融合的“思想碰撞”正在进行。至于估算，学一点挣值……
I work on DoD projects with varying project reporting requirements. There are many methodologies and processes one can follow. I've experiences success with Capability Maturity Model Integration and Agile (others here have mentioned agile too). There's an ongoing "meeting of the minds" of merging CMMI with Agile in the defense space. For estimation, learning a bit of earned value…