The two things that do not need to be compared have been compared for a long time because they are always assigned to a department of the enterprise (EPG) to manage, so they have been compared N times and have been disputed for a long time.
At the 2011 Process Improvement Annual Meeting (actually the original PK meeting), several guests were asked a question that could have resolved this dispute: What is the management goal of CMMI? What are the management goals of Agile? Guest answer: The management goal of CMMI is schedule, quality, cost. Agile is...... (This question was not answered later) If you answer like this, you will find that the dispute cannot be resolved at all, because both almost manage the quality cost of progress, if there is more, people/technology/organization...... Manage everything, although the focus is different. The Martian proverb says: Only simple answers are the right answers. So is there a simple answer to resolve this dispute?
In fact, I think the answer is: the management goal of CMMI is to allow the US Department of Defense to objectively evaluate and select suppliers; The management goal of Agile is to enable developers to manage projects with their own values.
What is NASA worried about? Worried about programmers not being motivated? Worried that programmers aren't innovating? Worry, but never more than this: worry about the project failing. Because they have huge property and life safety issues involved, they need a way to ensure that everything goes smoothly, no matter how high the cost. CMMI's heavy but guaranteed first-time success philosophy is clearly more suitable. No matter how successful Apple and Google are, NASA cannot find them to manage the process or outsource the project to them (even if there is, the project has passed CMMI level 3 or above, which is US law).
What is Google worried about? Worried about project failure? No! If you are worried, don't open an Internet company, the success of any government banking project is greater than that of an Internet project. So what are you worried about? Worry about not innovating, worry about being half a step slow. Who to choose in this environment? Of course, choose agile development that makes people more open to their minds. Shanda Network's 18 plan has more than 100 cooperative teams, and it does not require all teams to succeed, to be precise, as long as one is successful, it will return to its original cost.
There is something called male economics, which is to think that more, bigger, stronger, and wider is the goal of pursuing. Therefore, some agile development promoters desperately want to prove that agile is also suitable for aerospace, and agile is also suitable for a development team of 10,000 people, which is actually completely unnecessary. When the pioneers who founded the Agile Development Manifesto were skiing, who was thinking about aerospace? Who is thinking about a development team of 10,000 people? |
Posted on 11/2/2017 2:40:22 PM
|
|
|
|
Landlord|
Posted on 4/8/2018 10:16:51 AM
|
