I haven't had a feeling of frustration and loss of control for a long time.
The head of the technical department said: "We must focus on the product direction represented by the current project. We have to increase manpower. We must complete some other functions while the project is completed, we must completed products and projects. While completing our basic platform, we have to complete the time limit of customer requirements - before May, it will be completed in March. "
I am surprised to find that I am in a scene depicted in the "deadline", after a meeting, suddenly discovered that my team expanded more than double. Being repeatedly emphasized the importance of demand documents, he refused to spend 20 minutes to discuss what is the needs of the project; listening to them to tell me how J2EE architecture is naturally promoted, and the fact Most people are still the so-called "business logic layer", but to make a page; look at the main program, discussing them without specializing 2 people to perform database design, and this explanation is "We must be very flexible The fields on most interfaces are configurable ", the strange thing is that I have not heard any customer mentioned this, and I haven't written it yet, and he may not see the demand document. One.
Although the head of the technical department is not so poor and evil, even though we agree to lay a layered and object-oriented packaging on the structure of the program; even though we all believe that the project should be iterative Although he also said that the product completed in March is not required, and my original plan will also release the first version in March. However, there are more subtle differences, so that I can only sorrowful look at the project's process, I can only hope that all the time has enough time to catch the customer's progress, or leave before the past I sent the project with a hop.
There are so many identical points, why can't I accept it?
No one truly understands the progress of the project and soliciting my opinion about the progress. It is directly to "give help" and think that it should have a faster progress.
Although we are all use of "iteration", but they say it is just a small waterfall that takes one.
In their brain, the software is designed. Developers can do such a design. He can master it, but it is the extent of design.
Three different goals are completed by a team, and this team is too big for a single project. Worse, the leaders have the power and possibilities of the "helping" person who pumped back to him. More worse, after a morning discussion, I am surprised to find a unified team, not the three relatively independent teams I have been insisted on the three relatively independent teams I have been in the regular review. And technical exchanges to share technical results. Such basic differences have been discovered at the end of the finals, I don't know what is the issue of communication.
Maybe work is this, the real agility is to show the competitive advantage of relative other methods. (Although only my efforts are unable to make the entire project, it is better to think about it.
In the previous practice, I have found that I can't make a project as the most streamlined approach as XP, mainly because there is no on-site customer. However, it has also been adjusted to adjust the norms of more suitable intermediate products. At present, this project is constantly subjected to quenching and constraints from traditional perspectives, and the deviation in the original practice can be adjusted appropriately, and the agile effectiveness is truly tested.
Since there is no effective implementation of TDD, there is no sufficient energy to ensure the quality of the project. Now the project is confirmed by others, I can concentrate on considering the functional design and demand verification of the project.
The problem of repeated thinking struggles, at least the decision to leave now will be easier.
