Practical summary of the project development and management
Recently with several members of the group project development, in order to avoid in 2009 led the project in Guangxi Unicom mistakes, time to do some summary records, in order to constantly remind himself not to commit the same problem.
1: Requirements Capture and Analysis
2: Task decomposition
3: Effort Estimation
4: task prioritization
5: Resource access and authorization
6: Project progress tracking
7: deal with unexpected problems
Second, the specific details
Requirements capture and analysis to be as accurate as possible, to avoid rework. Can be combined with pre-prototype Demo, as many communication, allowing customers to determine needs.
UML and the like can not be too complicated. Just to aid understanding of the requirements, as well as communication and members understand the tasks on the line.
Members understand the strengths and ideas, reasonable arrangements for the task.
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 estimate * 2.
Task estimates, to arrange for people with mobility and motor time, should not be completely filled in order to deal with unexpected things.
Ability of members to be complementary, not everyone do the same thing.
Guide members of the rational organization of work: work experience, especially people who have just graduated and soon encounter something new, always trying to learn that this is science, not according to plan. Should let them know, to progressively complete the task. Complete the work first, then learn. To learning at work, rather than in learning the job done.
Use of new technology, the relative wealth of people have experienced a unified training, and not let members of the laissez-faire, self-learning is not easy to seize the key, more important is to learn something, not necessarily useful to the project.
Have a good management tool and version management tools, unified training to avoid the use of tools errors waste of time.
Equipment and have someone manage to configure the environment to prevent the effects work.
Documents and specifications, are also important. To avoid the accumulation of technical debt later. Long-term projects, such as the kind of period N, there is no corresponding documentation, maintenance of the people behind it will be very painful. Especially in face of members of the big shake-up, the more apparent. For a project, the company will consider the company's cost, schedule, benefits, etc., so not all will be very seriously. However, debt is always someone to have, and I hope people themselves do not become insolvent.
Problems should be thrown outward and upward, not into a dead end, that difficult things their own, others may be easy to solve, to learn the rational use of team resources. Higher complexity of the task to know, good for resources and adjust task.
Motivate team members to improve the level of the plot work.
Members of the execution is very important.
The person authorized to be higher.
And members often communicate progress and problems encountered, can be as small working days.
The progress of the initiative and superior communication.
Human resources can not be easily changed. To the parent that has called the arrangement a member of the Task Scheduler can not guarantee the smooth progress.
Do not have to do things the pro-bow, we should put out the task, grasp the overall. For experienced people, to trust and delegation of authority, as long as the guidance and tracking on the line. Themselves are not necessarily smarter than others.
Have incentives, such as Money and the like, or else we no enthusiasm, but by the Boss to decide this, not people themselves motivate it, ha ha. Can only be disguised from the rest on the incentives.