First Agile Development

20 days, four iterations, four times presentation.

Iterate one

As the front desk, the remaining 5 people repeatedly confirm the page design needs, need to provide several parameters, variable name is what, respectively, in what form to pass, using form form, action path fill what. The first will be suspicious of their ability to communicate, will always have a little in and out, and then re-adjust, but at least this is still within the scope of adjustment, some people alone, for their own things there will always be some sudden new ideas, and regardless of the front desk to achieve the situation, "anyway, the change will not be very big", really want But angry still want to smile Ah, continue to communicate.

Personally, due to the long time of communication and lack of experience, a system of basic pages-login and page main frame template is implemented without regard to aesthetics, but also completed the function of the background function to display the corresponding page, the same is not considered aesthetic situation.

Iteration Two

Repeat the previous iteration-communication, but at least a phase of the cushion and run-in, late changes will not be too big, just this stage, more function pages, involving the data interaction is cumbersome, resulting in heavy testing tasks, repeated output and even go to the breakpoint test to troubleshoot problems.

Communication time is not long, but a person at the same time write seven to eight pages, under the circumstances of lack of experience, there is no extra energy to consider the interface style, detail optimization and other aspects

Iteration Three

Because the communication is really good time, and the interface design speed is too slow, my group chose to change the strategy, each function implementation of the respective page demo, later unified modification. Using the free time, I began to find a lot of material plug-ins and other resources for modifying the interface style, including a particle background effect with verification code generation and verification of the login interface, adminlte--use bootstrap including a variety of skin style control Panel theme, due to the existing resource mismatch requirements, It also wrote the Unified style of table and reason pop-up layer on its own, and basically reconstructed the whole system interface in this iteration. During the revision of other people's page code is also encountered difficulties, everyone has their own writing habits, may go to use the plugin, will use the native JS, and even re-import different versions of jquery, so the whole webcontent become extremely messy. And the biggest problem is that a member of the group X without communication, design their own interface, and then realize the function, but later I found that the front desk can not be like his design, also need to modify the background code, the other side expressed resistance, eventually the entire group coordinated, agreed to the foreground program, but the final realization, In the process of coding, he found that a missing parameter could not complete the function, he added the code on his own, but did not communicate with the foreground, the final page could not be realized.

Presentation, unexpected situation, the demonstration computer suddenly broken network and can not reconnect, and the group inside and outside the network database data is not updated, no data, resulting in exposure to many null pointers in the background error could not be processed. After replacing the computer, the computer user did not update the code in time, resulting in subsequent members failing to demonstrate their capabilities on schedule. and member X replaced the computer for the third time to demonstrate the different versions of the demo that you prepared. So, the entire third iteration of the presentation, was evaluated by the teacher as "if the person in charge of your company is present, you 6 will be fired off on the spot". Very depressed, but at least prematurely exposed the shortcomings of my group's lack of preparation. Database updates are not timely, personal code Update submission is not available, the import file is not backed up to everyone, you need to ensure that each computer is demonstrating the same version.

And I have not been clear to the end is the first oneself through the communication and writing function page, the later unified conversion style or let them first each implementation of the page demo again unified modification will be better, perhaps after the subsequent experience rich, processing will be more handy bar.

Iteration Four

The first agile development encountered a change in people, or at such a critical moment, it is not known to be fortunate or unfortunate. The beginning of the last iteration, the above member X because the communication with the front page to achieve agreement, reluctant to modify their own code, by another member J Choke, the front desk to do their own page, write him to achieve the function on the line. Member X announces strike, all of you do it by yourselves, I quit! Communication is not, determined to retreat group. The head of the company intervened, failed to change the situation, announced that my group to reduce one person. This member x in my group is mainly responsible for database creation and maintenance, late and functional realization, so that the functional part of the need to be rewritten, the database also have to send people to maintain, aggravating the burden and pressure of all members. But somehow the final project was finished near misses.

Learn to optimize the interface, humanized processing operation, enhance the user experience sense. Will correct the JS writing specification, merging similar CSS to reduce the impact on page loading speed.

First Agile Development