My opinion of project management

1. The project requirements document, as a project requirements change is unavoidable. But what is the version management of the requirements document? Should there be a reasonable change and filing of the version by SVN, and the appropriate written reasons. This way, regardless of who took over the project has the source can be found, and not with the former project colleague asked West, not to tell the customer I do not know.

2. As party B should remember clearly the reason for the change, whether it is the electronic version of Notepad or notebook should be written clear reasons, red mouth white teeth, in black and whites, then the customer asked to explain.

3. Internal communication of the project.

1. It is the interface personnel and ETL personnel communication. To tell the backstage my front desk need to filter those conditions, the background run the number of times must add these parameters, otherwise the fact table out data, the front desk also can not see the data.

2. Is the background of the communication between different modules, it is necessary to maintain the consistency of the dimension table, not a module of a dimension table, especially some very important dimension table between the different modules must be agreed good number, otherwise different modules of different dimension table data, to the customer presentation when a module to import a version of the data? Who will do this when the data is integrated and how? How many unexpected ETL problems will be caused by the so-called bug?

3. Is the front desk problem, modeling and interface is each person divided into lines do? Or modeling is a human interface that is done by other colleagues. When modeling and interfaces are not the same developer to do, modeling colleagues can communicate the modeling design ideas to other people. It's not that I think technology is very good, and I don't say anything. You have to know that you are facing a team, not a lone fighter. If you can do anything, then what are the other teammates doing?

4. In the project except whether the project manager has the technical Danale can support this project data flow direction, from the foreground to the backstage link, the key link realization. Perhaps the background implementation process is unclear, but the entire process he can control, can find problems in the foreground or backstage.

4. Remote projects, for these communications should be more thoughtful, not QQ discussion, phone is OK. It's best to have mail control. Because everyone is very busy, said someone will forget, and even some people do not see a pile of information in the group. Of course, the customer site This situation will be much better.

5. What is the project manager, responsible for coordinating the control, risk, schedule, time, communication, clear each task of the responsible person, not every day down the head to see the most work is Good project manager. Finally, with a team, he failed in any of his own projects. Poor delivery, Project extension and so on. The responsibilities of management and developers are not the same.

6. The project is done, what we have learned and what has been left behind. A year to do a bunch of projects, and finally the company needs a demo to do it now?

7. The data dictionary is perfect, whether the project should have a data dictionary from start to finish, is there a continuous update?

8. The growth of technical personnel, the company can give their own platform, growth is on their own, we all say so. But the environment is also very important, how many people are because of the role in the project to do dispensable roles to resign. The best job is not to be idle every day, as a technician at least personally think this kind of work is torture.

9. Technical problem solving, when a development can not solve the problem whether someone in time to solve. No one can do anything, unity is power, maybe one person

My opinion of project management