The first week after the National Day holiday:
Overall retrospect, nothing worth reading about. Estimation of the only record that is process issues Friday to see new projects.
It is a small program project, the prototype is non-technical personnel on a painting business, it is ugly and a lot of loopholes and logic errors. Ironically, the leadership in time to give us new developers to finish projects or circumstances demand, design renderings almost finished? So we are listening to the needs, begin to understand the existing prototype and renderings of the time, is how unhappy and angry, to flow the wrong unhappy, unhappy with the results of the work of designers in vain, because no matter how good renderings, and certainly is based on a prototype to draw the prototype on loopholes, rendering even the best have to redo.
Also have to say it again, after the prototype came out, must be determined by the back-end personnel review, to determine the front-end staff, the leadership review, after review by the customer, and then to the interface designers to design renderings, the effect Figure out directly to the customer to determine the well, after the customer said OK, API, back office, front-end can begin where Admin can start earlier.
Second week:
Overall, this week I did a proper business, and that is according to their own understanding drew a prototype project, though not necessarily adopt but at least able to communicate more than the starting point, and reflects some of the problems, in order to improve subsequent optimization. A clear demand for people to work together just to exchange views, orally or in his head in agreement, but the abstract, these abstract to reflect on real prototypes, so we can be more clear understanding of the needs in the end is sawed, or imagination with their What is not the same place, or find yourself or someone else a vulnerable place. Thus contributing further to achieve unity between the teams.
Also this week, and also operates a co-worker exchange program optimization problem before a back-end system, very well. He wants to use their own experience to add a function technician, but this function is very general, he said, roughly one will feel not realize, because he did not let me imagine or perceive what he wants is something. This is like a painter who wants his friends to help draw a monster, because she likes, but the artist never laid eyes heard of monsters, so it is silent, but in order to hold each other, can only go as far as possible led him to want to try to describe himself details to something and repeatedly asked to confirm that this process may not be pleasant, but be patient, no matter can not draw, at least to understand what he wants is Gesha, it is respect for each other.
After this, I felt quite patiently, gradually have a state of mind: respect for the views and feelings of any user of the program, at least to finish them patiently listening, do not interrupt, do not criticize.
The third week:
This week is mainly engaged in their own work-related public a number of pages, from database design to the event page write interface, as well as static pages and the back of the binding test. Although only three pages, but still useful to a lot of things. This process, feeling the most valuable part of his own doing, some micro-channel package is commonly used method of ecological situation in the future reuse of this feeling will be a lot, so when writing these methods very rewarding.
the fourth week:
This week's work, on the whole, there is nothing valuable parts, has been put time on ineffective communication above, I look at myself, at most, three days real work of the day is on a project the ending (test optimization), a day is a database design, writing day was part of the interface. Then the problem is obvious, in the above communication invalid spend too much time indeed, the cause of this situation, I had the following thought:
1, the company's personnel constitute or projects involving personnel, as well as its current daily work:
Understand the point of technology, the project has its own ideas, the highest decision-owner;
And customer communication, communication boss, project manager for communication, non-technical products novice;
And the boss communicate, communication products, technical staff to communicate hands of novice project managers;
The main project manager and communication, and provide back-end support for grassroots developers of database data applications, API, backend systems, interactive front page;
And product communication, communication project manager, front-end staff communication interface designers;
Interface design and communication, project managers communicate, communicate and occasional back-end junior officers;
= "Is the status of each job personnel currently in the company's work more, causing a problem now is: backend grassroots developers even have time to spend two days a week to do useful work or ineffective communication situations , (as well as demand Indefinite lead interface designer to do a lot of useful work situation)
So what caused this problem in? I think had the insight or perspective:
1, the current product is the beginning of his career, to experience some of the interface design, interaction design needs to be improved, to withdraw from the system into the secondary flow logic then come to control is not in place can also be understood, after all, needs to be improved professionalism, not to mention user experience, basic needs or functional logic can go through the line.
2, if the level technician no power to decide on the prototype project, then please do not let the grass-roots contact with the technical aspects, namely, the underlying technology can not completely product-related worry about things such as prototyping. After the prototype is determined, so that the project manager can be notified.
3, a prototype is to project a restraint system or application or application framework it is defining what an application can do, what not to do, what display does not display anything, particularly on the order of interaction logic or a function; and he is a multiplayer discuss the foundation, he would have found it easier to communicate, rather than "intellectual exchange." The interface design is to create a prototype on the basis of this framework on the user's visual experience, such as background color, button size, shape, color and other text size, that is, "What show do not show any" exercise our fever within limits.
4, if the primary developers do not have the right to decide on the project prototype, not painted himself prototype, then the primary developer should not have too much involved in the project prototype determination process, even after the first prototype needs determined by the project manager informed about the result on the line. After learning the results and try to understand it again, or do not understand the logic put forward (data level) to be perfect, nowhere place uniform feedback to the project manager, and then began to work back-end (database, interface, background, technology finishing), if prototype does not lead to the back-end work carried out, before the communication of that product and project managers need to question.
The project manager is the spokesperson for junior officers, but also for prototyping applications determined aspects of the project development cycle, iteration planning, personnel division and so act as a "commander" role. The project manager is to reduce the presence of grass-roots project developers and decision-makers to communicate between the cost (product and bosses and customers), to control the project schedule.
Product Manager (may be the only entrance to our customers and to communicate), should organize as soon as possible the requirements document, and to the project manager, project manager or expected to have a general understanding, but he started the project that is the application framework layer design, that get a prototype project 1.0. This process should be minimal and project managers to communicate (this is the play to their talent, knowledge and learning phase, the product is fully human battlefield, regardless of how the back-end to achieve, can you realize), and directly after the completion of the first project manager communication, project managers or through comments, product prototype iterations made according to the project manager, comments until the project manager through. The product was then the boss at the prototype notification and clients, project manager for the boss and the task product of the project roughly cycle budget, while the project manager finishing bottom may need to know the technical points, and notify them to understand the related technologies, or directly based prototype the beginning of the development work.
The boss of the project to conduct their own assessments based on product requirements documents provided, prototype or project managers work expected technical point, if there are comments on the prototype technology have opinions, products which directly links the former contact the project manager.
"If the level technician no power to decide on the project prototype, so the focus is: isolation , when the next phase of work begins, must end on a stage work. This reduces ineffective or inefficient communication.