Practical project development and management summary
Several members of the group recently carried out with project development, in order to avoid in 2009 led the project in Guangxi Unicom mistakes of time to do some summary records to constantly remind himself not to commit the same problem.
First, focus on
1: Requirements capture and analysis
2: Task decomposition
3: Effort Estimation
4: task prioritization
5: Resource access and authorization
6: Project Progress Tracking
7: handle unexpected problems
Second, the specific details
Requirements capture and analysis to be as accurate as possible, avoid rework phenomenon. Early prototypes can be combined Demo, communication as much as possible to allow customers to identify needs.
UML and the like can not be too complicated. Just to help them understand the needs, and and members of the communication and understanding of the task on the line.
Understand the strengths and ideas of members, a sound arrangement.
Task decomposition granularity as small as possible, to facilitate tracking and workload estimates.
In the project, we are not familiar with the technology used, the workload estimates * 2.
Task estimates, make arrangements for motor and motor time people should not be completely filled, in order to deal with unexpected incidents.
Ability to complement each other between members, not everyone do the same thing.
Reasonable arrangements to guide members of the work: in particular, work experience and who have just graduated soon encounter something new, you always want to learn that this is also science, not according to plan. Should allow them to clear, to progressively complete the task. Must first complete its work, and study. Learning to work, rather than learning the job done.
Use of new technologies, relatively rich people who have experienced a unified training, and not let members of the laissez-faire, self-learning is not easy to grasp the key, more important things to learn, not necessarily useful to the project.
Have good management tools and version management tools, unified training to avoid the use of tools errors waste of time.
Need of expert management equipment and configuration environment, preventing normal work.
Documents and specifications, are also important. To avoid the late accumulation of technical debt. Long-term projects, such as N of the kind, no corresponding documents, the people behind them will be very painful to maintain. Especially in face of members of the big shake-up, the more apparent. For a project, the company will be the company's consideration of cost, schedule, benefits, etc., so not all will be very seriously. But debt is always someone to also, and I hope the people themselves do not become a debt.
A problem should be thrown out and up, rather than dwelling on their own difficult things that other people may be very easy to solve, we must learn to rational use of team resources. So superior that the task complexity, and adjust well to seek resources to the task.
Motivate team members, improve the level of the work product.
Members of the executive power is very important.
Face to superior authority.
And members often communicate progress and problems encountered, can be as small as day.
The progress of the initiative and superior communication.
Human resources can not be easily changed. Superior to that call to schedule tasks that have been scheme members, can not guarantee the smooth progress.
Do not have hands-on, the task should be put out to grasp a whole. For experienced people, to trust and decentralization, as long as the guidance and tracking on-line. Themselves are not necessarily smarter than others.
Have incentives, such as Money and the like, or else we had no enthusiasm, but this should make decisions by the Boss, Incentives do not own, haha. Can only be in effect from the rest of time incentives.