declaration
Granville Miller (RMiller@together@together@together@togethersoft.com) consultant and developer, Together, Together, August 2001
Granville Miller temporarily waives the demand to collect the theme, and starts to discuss another topic: Sub-integrated software programming. Let's find this method how to supplement and extend the flexible development of the flexible development movement, and how it may change the education and software development practice of software developers in the mainstream development community. please at
Discussions Forum share your ideas about this article with author and other readers.
In my early column conclusion (see Resources), I have promised that this column will specifically discuss various methods for demand for demand during flexible development. However, when I started to start the column, I realized that it would be worth the development of this larger discussion from the flexible software. But when I started to start the topic, I found my own desire to discuss the topic of the sub-software development.
This is not surprising, because I believe that the overall software development is the next step in the development of flexible software. I am very loud, I chose to change my route and introduce my very unique Sub-Software Development Declaration. We will collect this topic in the next return.
Flexible software development flexible software development movement has caused huge impact on software engineering theory and practice. Its advocator's success challenges and refutes the excellent system development guidelines for practical proven, and replaces them with themselves. The foundation of the movement is the four core value, and the first time in the Flexible Software Development Declaration (see Reference):
Personal and interaction better than process and tool useful software superior to integrated document customer cooperation is superior to contract negotiations to make a react to comply with the plan
In fact, these value marks the departure of those who are supported by traditional software development methods. The highest purpose is to create a more beneficially successful software development environment. Indeed, flexible movement has left his own mark in the history of software development. However, although the flexible movement has revolutionary, it is just a more complex and more beneficial development practice. Sub-integrated software development is the next step.
Is the process first? During the Industrial Revolution, Mr. Frederick Winslow Taylor studied people's work. He has studied time and action to optimize the use of physical skills and effectively create products. Taylor is famous for his persistence of the principle of efficiency. His famous quotes summarize his mood for workers in the industrial age: "In the past, people were the first element, and in the future, the system is likely to be the first element."
Efficiency follow and system first or process first principle is now we call two basic components of quality management. Quality management is to study and implement those correct implementations will improve quality. The keyword is the correct implementation. These words form a security harbor expression in quality management. It is certain that if your business, manufacturing or engineering practice cannot improve quality, you have no correct implementation.
Although I don't believe that there is a quality management crisis in software development, I have seen failure is producing in our industry. These failures are often caused by process and technology, the reason is that the process is not properly implemented or unsuccessful. However, I think it is often an escape from failure to process and technology. Especially when you consider Alistair Cockburn's assertions - the process and technology in successful software development is the second element (see Resources).
People are the first element of any software development project. Any good first-line administrator knows that he or her team member is the primary and most useful assets of the project. A software development criterion that never replaces is an excellent person to prepare excellent software. However, if this, when the development project fails, should we blame? the answer is negative!
Submon I believe that the best place to find the behavior that reflects excellent software development skills is unlikely. Only the battlefield. Two guidelines leading to a single soldier to achieve huge success is training and initiative. The best army allows a single soldier to make a decision on how to achieve their goals during the battle. Many battle victories are made through many soldiers as individual thinking and actions, while also playing as a team. An entity that maintains its own independence, but also as a whole, is called a subsidey (Holon). This term is Arthur Koestler to combine the word overall (HOLOS or "the whol") and part (ON or "The Part"). The whole is used to describe the behavior of society, cells, and tissues, and recent manufacturing behavior. I believe that the monolonic behavior is the actual work of software developers and is likely to work.
The fact is that when developing software, we continue to follow the idea of Frederick Winslow Taylor. Time and action research proposes amazing laws in academic software engineering cycles. However, software development, like many other elements like the information age, have not been related to time and action. Related to it is creation, innovation and people.
For software development, we inherited the idea of born in the industrial age - the ideas and environments of being based on manufacturing-based assembly lines. In this environment, individuals can't get climate. He did not authorize manufacturing and change, and therefore, when the life cycle (software development cycle) requiring changes, he should not blamed him. Perhaps, it is time to stop the process and technology as the first element, so that the real first element - people - as the center.
Sub-integrated software development software project is a craft. It needs to use wisdom. Its criterion is complicated and needs knowledge. The best criterion is still in development. Because the software engineering field is so broad, no one can completely "master" it. Also because this area is constantly evolving, the protection of knowledge requires continuous efforts and learning.
If you are an excellent developer, an model or administrator, you should know what I mean. You have faced a variety of techniques and then routinely elected a best tape for work. You adjust and try to find a solution in the crisis. You make the submitted unit. Do you need a software development process that you should then do if you will then do any given time? Not required at all.
The true sub-integrated software development organization recognizes that different people have different ways of thinking. Some people's way of thinking is abstract, others are specific; some people are strategic planners, others are oriented with action. The techniques used by the sub-organization have made people work together while choosing the best working methods. These organizations allow people to work with the best way they find. Briefly, sub-integral software development requirements continue to learn and individual adaptation. It encourages differences.
Training model I made these warnings - our training is not mature as it should. In contrast, soldiers' training can be trained to thousands of years (most conservative estimate). It has developed many centuries. New technologies have changed some of our ways. But many of the basic models of war do not change due to changes in technology, and the training of soldiers is also the case. When we accept changes in technology, it is also necessary to adapt to these eternal lessons.
Half of effective combat training is to provide a soldier a choice of a choice of tactical library. The other half involves teaching them to create their own tactics as training. Similarly, I must solemnly announce half of the effective education of software developers in the acquisition of knowledge and skills. The other half is learning to process changes and quickly advance in the changing domain. In short, goen to revolution.
Software developing many software development processes is hardly provided by many software development processes. Some people propose to repeat the process itself, as if you continue to review the same status map, you will get more information. Repeating our actions can improve them, but only after introducing the feedback method. It is necessary to know where we have possible misunderstandings, simple repetition is not enough.
A supplementary activity is a growing trend in combination with an activity that can be incorporated to correct expected errors. This activity is called supplement. For example, we use the domain analysis weighing use of example to ensure that the subsequent object model does not work. These supplementary activities allow us to do not make a common mistake. Without supplementary activities, the second element such as process and technology becomes our only safety net; if we are in trouble, we can blame them. Because most software development processes have only two dimensions, perhaps this blaming is what they have. Indeed, in addition to the feeling of controlling us, there is no other purpose, it is a false security net.
process? What process? Does this mean that you can throw off the software development process and develop it under the support of the security net? Unless you have a responsibility to receive project failure.
On the other hand, if you are not adaptable, you will not try a new way to do things. If you don't try new things, you will not learn, develop and become the best. This is a process of continuous exploration, and there is no one in us to complete at any time.
Even if you choose the security network that has established procedures, you don't have to follow it completely. This will not be like this unless each of the group is the same. If you have found the ultimate process of everyone in the group in the group, please send me the ultimate process of all the projects you do. However, I don't expect many processes that meet the above conditions, because Jacobson's law indicates that this process does not exist. I believe that even in a highly united group, no process is suitable for everyone's thinking. There is too much difference between us.
Conclusion The overall software development is a logical extension of flexible movement. It needs to be highly understood to prepare technology, and it is also required to be responsible for the developer to the delivery system. Sub-integrated software development team uses the process as a guide, not a pillar. The group does not ink the rules, or the process is ignored when common sense is dominant.
This article is not a definition, but a declaration. Among them, a better delivery of the software system method is proposed, which uses the activities defined in many flexible processes. Similarly, I considered the best criteria for software development and a pressing supplementary activity that corrected the error method during development.
We will continue to discuss this topic in the next column, where we will return to the public discussions on the use of examples, functions, and user scenarios. I will show you how to make these elements into part of your overall software development toolbox, and how these elements will support a pre-contained, balanced or subsequent preparation software method. Please don't leave.
Reference
