1 Introduction
1.1 writing background
This paper is a summary of the description and development results of the development process of graduation design "Kind Weboa.Net". In this graduation design project, I will learn how to learn software processes, project management and software. The theory of design and development is used in practice, and has accumulated a lot of experience and experience, this paper will be the main content. The software engineering theoretical system is very large. This paper mainly describes a simple and effective part of small and medium-sized projects and the use of Kind Weboa.net. At the same time, this paper also briefly describes the topics related to this graduation design: office automation system.
1.2 project background
l Project Nature: This is a product, the goal is developing a commercial product, and is a software product registration.
l Project cycle: The project started in September 2003 and has experienced a few months of preparation (funds, manpower, technology), started in January 2004, until June 2004 project acceptance.
l Project size: probably 24 months before the project. The participant is 6 people before and after.
l Project Benefits: After the project is completed in June, two customers have been successfully implemented, and all investments have been recovered.
l Editor's responsibilities: I am in the project, participate in the entire process of the project, responsible for project management and system overall analysis and design, and participated in the development of some modules.
2 project management
2.1 Structured Project Management
As the size of the software project is increasing, the participant increases, the more strict requirements for normative requirements, the software development has bifpeared farewell to the mode of personal heroism, the engineering software development era has come. As a result, project management begins to gradually be in the core status in software research and development activities. Good project management is better for most projects, which is more significant. Software Project Management aims to form all kinds of resources of the project by using the basic principles of management, ensuring that the project meets the expected goals. Due to the complexity of software engineering, project management and software engineering have not had universal programs for many years. A book of "Moon Myth" gives a conclusion: no silver bomb. Project management needs more experience to solve problems. Even so, after years of development, everyone has summarized the basic principles and methods of project management. The "Silver Plan" of Project Management is given in "Successful Software Project Management" book: structured project management. This is the most influential theory in my influence in the past two years, and I have used many times in the project, the effect is good. Ten basic steps for structured project management are:
1. Visual target, pay attention
2. Give a list of things you want to do
3. There must be a leader and can only have a leader.
4. The division of labor is clear, responsible
5. Manage expectations and risks
6. Adopt appropriate leadership style
7. Understand what is happening
8. Tell people what is happening
9. Repeat 1-9
10. Result
1-5 Related to the project plan, others are related to how to implement programs. Here I sumly the experience of implementing this project management framework.
l The first step, the beginning of the project is to clarify the goals and scope, and define the goals and scope as a number of points that can be measured into the formal document. In the future, do not change this goal and range unless external factors. All activities in the future project must be related to this goal and do not exceed this range. It is important to emphasize that in the actual project, R & D personnel often do not meet this goal, but more than the established target requirements to complete his development tasks. Some technicians lack time cost and technical cost awareness, always do things best, and ignore the scale and time requirements of a project, which will make the project more, and ultimately affect the progress of the project. When the project goals are clear, it is necessary to hold a core personnel to launch a mobilization meeting. It can be used to describe the beautiful scenes after the project has been successfully completed by "They have a happy life" method. Morary and passion have always been the key to success. l The second step is to usually say WBS, most of the project management books have been said. Here you talk about the granularity problem of the task. Typically, the task list is also the main part of the project schedule. WBS is gradually refined, and things to do after a week basically do not need to be divided, as long as there is a general direction. As for the current task, it is best to make a unit in hours, and don't exceed 4 hours. The task subdivision can be divided into different people, everyone else to make his work, but must report the project manager and finally confirm the project manager. This work will also be detailed in the project plan.
l The third step is to determine the leader. There is only one leader in a project. In particular, there can be only one decision maker. This person is generally the project manager, he communicates the upper level, customers and teams. In some projects, it is possible that in addition to the project manager, there will be a secondary person, but only one person has decision-making right. Because the debate is a big jealous of the project for the differences. Policymakers should also fully listen to the opinions, but only the plan and task arrangements he issued are valid. This is also reflected in demand management. Any variation of the demand must be directly determined by the project manager's decision, without direct decision by the part, architect, or developer.
l The fourth step is actually a further work on the basis of the second step, and is also related to the project plan. The task must be person in charge, otherwise the subdivision task has no significant meaning.
l Risk management is quite important. Reducing the most effective way is to control the expected values of superiors and customers. This requires the project manager to have a relatively strong communication skills. At the same time, there are many risks that come from demand, so effective management needs are also an important part of risk management. At the time of demand analysis, it is necessary to assess the risk for each requirement, and try to reduce the demand for high-risk or the completion of the project body is completed or pushed to the second phase of the project. The key to change management is to control the occurrence of demand changes. You cannot easily modify the demand, all modifications must be approved and discussed and maintain consistent, the latest demand specifications in the hands of developers. This work can be used by version control software.
l Seventh, eight steps are to establish project supervision and feedback mechanisms. You can implement: daily work report, per week, double week project summary report, monthly project report. The first few items are the project members feedback to project manager and find problems, and adjust the plan. The last item is the project manager to report on the leadership. What form is not critical, the key is to keep the communication smoothly. The face-to-face conversation is far more than a thick document to achieve the effect of communication. For the purpose of communication, the document should be communicated, it should be reduced, and only the main communication mode is only when it cannot face-to-face.
2.2 Project Planning and Progress Control
The core activities of project management are developed and implemented. How does the project plan are developed, how to implement, is also a topic that everyone is discussed.
The production of the project plan is generally starting from the scope of the analysis project. First divide a few types of work, then do WBS for several types of work, and then assign the person in charge for each task. Since many tasks have a good value for the previous task, some will be clear as the project progresses, so the project plan is constantly changing, and it is generally reviewed once a week to introduce a new version. The above work can be done by MS Project. The content of the project plan is also directly related to the software processes used, and the software process of the project can be embodied. Different processes have different strategies for the task segmentation of the project plan. The general principle is that the project plan is constantly iterative, and the task of the week should be divided into one or two hours. After the demand is clear, the WBS is directly derived from the task of design and implementation.
2.3 Weboa.net project management
The project management of this project basically adopts the method of structured project management. The software process adopted is mainly in the unified process, and later, it has been influenced by agile processes, so the project plan combines two processes. Features. After the project, we first determined the goals and scope of the project:
Then start to prepare a variety of resources. After the project is started, the first edition project plan mainly includes the following:
l The goals and scope of this project
L using the technical system
l divide the task into three sets
n Management Process Grade: Arrange the work of project management needs. The daily task arrangement is determined, and the system will summarize each week. Specifies the process of demand change. A number of progress checks is arranged.
N R & D process level: including demand analysis, summary / architecture design, design, and implementation, and testing work. But because the project is just beginning, only the preliminary segmentation of demand analysis is performed, and the demand for the first week is divided into several tasks every day. The timetable of other work is developed.
n Support Process Campus: Specify some of the person in charge of some of the work of training, configuration management, and general timetable
This project plans to adjust after weekly review and launch new versions. The main content of the adjustment is the rejection of the research and development process. Then send a list of his one-week task per week. This work can be done well through Outlook. I don't advocate let everyone know the project's detailed plan, but as long as his mission is OK. After that, the next week plan is adjusted according to the feedback of each person's task completion.
Later,
XP
The impact, introduced the release plan, and determine the list of useful uses to be implemented every week. The development plan will be subdivided around the release plan.
