when we start to cut corners and rush through, we start making small mistakes, then piling up into big mistakes, and then spending more time (and spending) to find and fix them. The Iron Triangle Does not Apply to software development
by David Bernstein May. 06, 16 · Agile Zone translation Kumat 2016.5.18 (if you have a mistake) (
The translated sequence was fine-tuned in the original. )There is three main constraints in manufacturing that is sometimes referred to as the "iron Triangle." These is scope, time, and resources. Three major factors in production (also known as the "Iron Triangle"): scale, time and resources. Scope refers to the size of the project or the amount of work to is done. Time refers to when the project would be a finished or how long it would take. The "resources" for developing software is people. Scale refers to the size of the project or the amount of work to be done. Time refers to the duration of the project's completion or the amount of time it will take to work. "Resources" in software development is the person. In manufacturing they say, "Pick of the These three things to flex, but one must remain fixed." The two factors are often flexible in production, but the other factor must be fixed. But the this model does does not apply to software development. However, this model does not work with software development.
And because developing software requires a great deal of communication and coordination among people, when we add more PEO Ple to a project it almost always have the short-term effect of slowing the project down. because development software requires a lot of communication and coordination when we add more people to the project Almost always makes development efficiency fall in the short term. Assembling software is not like assembling a car. In software development, resources is generally fixed because adding more people to a project doesn ' t make it go faster. Group Installation software is not like assembling a car. In software development, resources are generally fixed, because adding more people does not make development progress faster. On a Waterfall project, scope and time is also fixed, which often creates a nearly impossible situation. On the waterfall Flow project, the scale and timing are also limited Often leads to an unrealistic situation. if scope, time, and resources is all fixed then what's left-to-flex? if the size, timing, and resource limits, what is the elasticity? Developers know the answer to this question because they often find themselves in this situation. developers know the answer to the question because they own Are often caught in this situation. When all three sides of the Iron triangle be fixed the only thing that can flex is the quality of their own work -a nd this is the oneThing that developers must not compromise on. When the three corners of the iron triangle are fixed, the only thing that can be sacrificed is the quality of their work- and this is something that developers should never compromise on. As we start cutting corners and rushing we start making little mistakes that cluster into big mistakes so cost Considera Ble time (and therefore money) to find and fix. When we start to cut corners and rush through, we start making small mistakes, then piling up into big mistakes, and then spending more time (and spending) to find and fix them. Teams very quickly get on a downward spiral this puts them in a reactive rather than proactive development environment. The team is Get into a vicious circle that puts them in a passive, non-active development environment. A Real and sincere effort toward quality software has been the hallmark of every highly productive team I ' ve ever seen. For high quality Volume software real and pure effort is a common feature of every efficient team I see. Original address by David Bernstein May. 06, 16 · Agile Zone Translator Kumat 2016.5.18 (if you have a mistake)
"Translation" The Iron triangle (size, time and resource constraints) does not apply to software development
