How should a formal software project plan be written... Master, please point! It is better to have s

Quanbao to help you, pay attention to check the mailbox.

The project plan generally consists of two parts:

Project proposal.

It is generally formed in the early stages of the project and is relatively stable for the duration of the project.

Timetable. Once the project structure is clear, a timeline should be prepared and updated as the project progresses.

The contents that should be included in the project proposal are as follows:

Logotype. The name, **, and other relevant identifiers of the program.

Resources. Background material.

Role assignment and segregation of responsibilities.

Decisions on the design approach of the project.

Technical issues. What is the language, platform, or protocol that is applicable to the project?

Tools needed.

What tools are needed for design, coding, testing, document management, and plan generation during the project?

Staffing. Including the skill requirements of personnel, the time of arrival, and the way of hiring.

Training needs. Requirements, methods and cost plans for external and internal training, etc.

External relations and dependence.

What are the external constraints on the project, and what are the external dependencies of the project team?

Risk. Identify risk factors, analyze costs, and plan mitigation measures.

Handling of unforeseen events.

Project process and quality.

What process does the project follow, and how does it guarantee the quality of the activities and work products? What inspection methods are used?

Configuration management. Version control tools and usage rules.

Document management. What documents are required for the project? How do I check and approve all kinds of documents?

Monitoring and reporting of the process.

Test plans and scenarios.

Management of bugs.

The process of software release.

Acceptance (delivery) of software

After-sales service. Permit.

Product safety. Handling of changes in product demand.

Organization. Generally speaking, the project proposal is relatively stable. It is generally completed in the earliest stages of the project and requires few modifications in the subsequent process.

To emphasize, the value of a project proposal lies not in the paper itself, but in the thinking and problem-solving ideas that arise during the writing process. In the same way, it can be the basis for your decision-making.

Also, you don't have to write everything in your project plan. This is because many of the contents of the planning document are similar to similar documents in the past, and some of the content can be in different documents. If you have a test manager, a configuration manager, and a product manager, they will do a lot of things for you, but you have to review them.

400 sets of ppt templates|[70 sets of proposal templates] y3027|[63 sets of fresh templates] Y3030|[23 sets of two learning and one doing]|90 college style ppt|50 ppt templates|47 personalized PPT-Y3014|30 sets of resumes are universal24 business atmosphere templates-Y3020|Y3020 catalog. rar|Y3020-24 Business Catalog (**Preview)|Template|Template templates are free**.

Extraction Code: FRKY Slide Template is a defined slide format. Powerpoint, like word, excel and other application software, is one of the office series products launched by Microsoft, mainly used for the design and production of advertising, product demonstration of the electronic version of the slide, the production of presentations can be through the computer screen or projector**; With PowerPoint, you can not only create presentations, but also hold face-to-face meetings on the Internet, remote meetings, or present presentations to an audience on the web.

With the popularization of office automation, the application of PowerPoint is becoming more and more widespread. <>

The biggest purpose of using project software is to prepare and track the plan, and in order to be able to track the change process of the plan in a refined manner, the scientific and reasonable preparation of the plan is a prerequisite.

In the general project management requirements, it may not be required to prepare all the above plans, but the minimum schedule, resource plan, and cost plan are mentioned in most project management requirements.

Project software can easily help you prepare the above three plans.

Schedule Sequence:

2. Doing task breakdown (WBS) is to decompose your project into a series of tasks that need to be completed, and these tasks are divided according to a certain hierarchy, so it is called WBS (Work Breakdown Structure). Lift operation can be carried out during the disassembly process.

3. Set the duration of the task, how big is the time span that each task needs to be executed, and note that it is not the workload, but the time period.

4. Set the logical relationship between tasks, try not to manually set the start time or completion time of the task, but let the project automatically arrange the time according to the logical relationship of the task, so as to check whether our plan is reasonable.

5. Find out the critical path, the critical path is particularly important for the monitoring of the plan, if the critical path can not be displayed correctly and completely, it means that there is a problem with the preparation of the plan, and it will bring great difficulties to the future monitoring.

6. Optimization and adjustment of the schedule.

Expense plan arrangement:

1. Establish resource information, including human resources, equipment resources, material resources, cost resources and other information.

2. Allocate resources to tasks, you can assign resources to a task, and you can allocate them in batches.

3. Check whether there is a conflict in the assignment, and adjust it if there is a conflict.

4. Optimization and adjustment of resource planning.

Cost plan orchestration order:

1. Set the type of cost resource, that is, the account of the expense, such as travel expenses, transportation expenses, and so on.

2. Allocate cost resources to tasks, and the overall cost of each summary task, stage, and project is automatically calculated by project.

3. Optimize the cost plan.

After the preparation of the above three plans, the overall optimization and adjustment need to be carried out.

It's complicated and depends on the nature of the software you're developing. I'll give you a few points:

Choice of Software Protocol. This determines the form of software distribution, involving whether it is open source, whether it can be commercialized, copyright, copyright, redevelopment rights, and so on.

Selection of development model. This determines the development process, waterfall, V-mode, spiral mode, iterative mode, and so on.

Selection of development tools. Depending on the type of software, development language, framework, and functional structure, some tools come with their own software protocols, and you must check whether they are consistent with your software protocol. For example, some tool libraries use inherited open source licenses, and the software that uses this tool library must also be open source, if your software is not open source, you can't use this library.

Resource planning. Including manpower allocation (the formation of the development team), equipment utilization (the allocation of hardware facilities), funds (development funds and use plans), time arrangement (development cycle planning).

Software goal planning. Describe the minimum standards to be met in terms of the functionality of the software.

1. Project plan format.

According to the requirements of the project development plan in the GB8567 88 Computer Software Product Development Document Preparation Guide, the content index of the project plan adjusted according to the actual situation is as follows:

1 Introduction. Purpose of writing.

Background. Definition.

Resources. Standards, Treaties and Conventions.

2. Project Overview.

Project Objectives. Product Objectives and Scope.

Assumptions and constraints.

Project scope of work.

Deliverables should be made.

Software to be completed.

The user's document needs to be submitted.

Internal documentation must be submitted.

Services that should be provided.

The project development environment.

Project acceptance method and basis.

3. Project team organization.

Organizational structure. Division of labor.

Collaboration and communication.

Internal collaboration. External Communications.

4. Implementation plan.

Risk assessment and countermeasures.

Workflow. Overall schedule.

Project monitoring. Quality control plan.

Progress monitoring plan.

Budget monitoring plan.

Configure a management plan.

5 Supporting conditions.

Internal support (optional).

Customer support (for projects).

Outsourcing (optional).

6 budget (optional).

Personnel costs. Equipment costs.

Other budgets.

The total budget of the project.

7 key questions.

8 Thematic Program Points.

The software project plan consists of the following: A comprehensive description of the software project, defining the work to be done and the performance limits, including:

1) Project objectives.

2) Main functions.

3) Performance limitations.

4) System interface.

5) Special requirements.

6) Development Overview. (1) Personnel resources.

2) Hardware resources.

3) Software Resources.

4) Miscellaneous. The quality of the schedule often affects the completion of the entire project on time, so this link is very important. There is no big difference between developing a software schedule and other projects, and the main methods are:

1) Engineering network diagram.

2) Gantt diagram.

3) Task resource table.

4) Cost Estimate.

5) Training program.

A key activity in the software project management process is to develop a project plan, which is the first step in software development work. The goal of a project plan is to provide a framework for project leaders to reasonably estimate the resources, funding, and progress required for software project development, and to control the software project development process according to this plan. When planning, it is important to make an estimate of the manpower required, the duration of the project, and the cost.

That is, through research, the main functions, performance and system interface of the software project are determined.