Many industries need pilot factories before product forming. That is to say, they need failed products. Similarly, in the software industry, writing Failed ProductsProgramIs normal. For most projects, the first developed system is not applicable. Therefore,You have to do this no matter what you plan to give up..
The only thing that remains unchanged is the change itself.
Software development is always full of changes. changes are inherent. the benchmarks established at the beginning of the project will certainly become higher and higher as development progresses, and even no products can be developed.
Change Plan System
Since changes are inherent, how can we prepare a change plan? This requires careful design, complete documentation, and all useful methods. To adapt to changes. For exampleXPThe method is a better way to adapt to changes.
Organizational structure for change plans
prior to design write a good document to show you, the courage to accept criticism has led to some meticulous things, such as whether the designers can accept their opinions with a good attitude. Therefore, building a team for a change is more difficult than designing a change. Therefore, it is necessary to establish a good atmosphere for people to communicate. For example, Bell Labs abolished all job titles, IBM is divided into two lines. One is the technical direction, one is the management direction, but both have the same treatment. Parallel transfers between them cannot be promoted or demoted, but can only be called for transfers, you can even raise salary from the management line to the technical line to balance the impact of this social factor.