A web project refers to a web-based development project. Due to some characteristics of web development, the project management of web development is very different from the previous software development project management, which is embodied in
1. The web project cycle is short.
The cycle of general web projects is from January to March, while the cycle of general software development is more than half a year. Like Vista, Microsoft spent five years to develop it.
2. The web project needs to be launched quickly.
The products launched by Internet companies pay attention to fast words. Whoever launches the product first to occupy the market will have the first chance. Therefore, web projects often require quick launch. For relatively large projects, we usually launch the product first, and then the first. Phase two and phase three will be completed again.
"Fast" should be the biggest difference between web development and ordinary software development. The maintenance of web products is on the server side, which makes this kind of fast possible. We can easily upgrade products at any time, while ordinary software is deployed because of On the user's machine, the frequency and magnitude of upgrades cannot be compared with web products.
It is also because of this "fast" that the requirement change of web projects has become the most important problem to be solved in web project management.
The web project manager handbook is divided into several topics, each topic introduces what the project manager has to do in this aspect from a certain aspect of project management, and the topics will be launched one after another.
This manual is a summary of my experience in project management, so the content of the manual will be continuously improved.
Principles of this manual:
1. Strong guidance.
2. Strong practicability.
I have always advocated this saying: complicating a problem is to help us understand it better, and simplifying a problem is to allow us to perform better. So this manual takes simplicity and feasibility as the standard. No matter how good a process is, if it is not simple and feasible, it will not be able to be promoted in practical work. Of course, the simple meaning is not to do less things, but to do things that make people who implement them feel that they should do it.
Requirements for readers:
1. The source of this manual is the same as my usual project management experience. Different companies have different characteristics, and the projects themselves are also different. Although this manual describes general problems, some specific problems are encountered. , we still have to take the actual situation as the standard, this manual can play a reference role.
content:
Web Project Manager Handbook - Version Control Process
Web Project Manager's Handbook - Development Time Estimation
Web Project Manager Handbook - Code Review
web project manager handbook - requirements change management
web project manager handbook - the content of the project manager's work
The web project manager handbook - words to keep in mind for project managers
web project manager handbook - risk management
web project manager handbook - cross-departmental collaborative projects
The web project manager handbook - can you communicate?
web project manager handbook - organizing meetings