Personal project management plan and implementation suggestions

I. project initiation (project kickoff)
Understand stakeholders and their interests.
Check whether all project team members are in place. If the team members are in place, obtain the resume of the project developers to learn more about the situation of each developer (they may be organized for trial by the customer ).
Lists the project functions based on the project requirements and creates WBS Based on developers' technical skills.
Plan the preliminary project development plan based on the project time and resources (rough plan of each milestone time point and the amount of manpower invested in each time period ).
Determine various software and hardware requirements, such as version control servers, database servers, development servers, defect management software servers, and development tools.

Participants:
Project Manager, Project Director, all project team members, user leaders, user participants, and other key project stakeholders

Project kickoff meeting objectives:
Let members of the entire project team know each other
Establish project work relationships and communication relationships
Let everyone clarify the Team's work objectives
Let everyone know the current status of the project
Review the project plan together
Identify the difficult or potential problems of the project
Assign group and individual roles and responsibilities
Team and individual commitment

Implementation Suggestions:
Manage all valuable documents generated in the project management process, such as the project proposal, project investigation report, Project Feasibility Analysis Report, and project review report.
Keep necessary confidential.
Since each project occupies the Organization's capital and resources, project review must be strict. It is recommended to provide necessary project management training for the Organization's senior management personnel.

Output documents include:
Project Risk Management Plan, Job breakdown structure (WBS), project progress plan, configuration management plan, quality assurance plan, timesheet, development standard document, test plan

Ii. Demand Analysis
Requirement Research: it is based on the customer's needs for functions, processes, and operations, and must be a project manager or department head.
List A requirement management plan (including a detailed communication plan and requirement communication plan), and consider the personnel, resources, and time requirements in the requirement communication.
Although some factors are caused by customers, we should consider some objective and subjective factors for them.
Pay attention to the communication with project members and team building.
Check whether the requirement analysis progress and quality meet the requirements.
Analyze whether the requirements are met and whether there are any omissions in the functional points based on the interaction design prototype and customer communication requirements.
Which documents or data are provided by the customer and whether the data needs to be maintained in the new system.

Implementation Suggestions:
First, train the project members to master the necessary development skills. (For example, what to do for demand development, how much to do, and what problems to pay attention)
Manage configuration of all valuable documents generated by the domain in the requirement development process.
The Requirement Modeling analysis has a high technical difficulty, and project members should choose based on their own levels.

In the interactive design, the user's ease of use should be taken as the premise, and then whether the technical implementation is difficult or the workload exceeds 20% of the preliminary design.
(The task of a role of the customer can be completed in one page as much as possible in the form of tabs. Generally, context menus are used to avoid system menus. A function block generally only needs one portal)

Output documents include:
Product Requirement analysis manual, data flowchart, system application architecture diagram, interactive design prototype, Requirement Analysis Model (rqm)

Iii. Outline Design
Determine constraints affecting system design: standards or specifications, software and hardware environments (including operating and development environments) that the system should follow) constraints, interface/protocol constraints, software quality constraints, implicit constraints, etc.
Determine the design policy: Extension Policy, Reuse Policy, and compromise policy.
System Decomposition and design: The system is divided into several subsystems, the functions of each subsystem and the relationship between subsystems are determined, and the subsystems are divided into several modules, determine the functions of each module and the relationship between modules.
Database overview design.

Output document:
Product Overview design specification and Data Summary design model (CDM)

Iv. Detailed Design
Determine the participants, database tables, input parameter descriptions, preconditions, basic processes, abnormal processes, logs, and other information of the function module.
Interface Definition of each hierarchy
Database Design: Logical design-> physical design-> Security Design-> Optimization

Implementation Suggestions:
First, we will train system designers on "topics" so that they can master the necessary system design skills.
Because the vast majority of Chinese universities do not offer "user interface design courses", most software developers are not good at designing user interfaces. The project development team should try to invite user interface design experts to participate (or guide) in the software

Interface design.
Manages configuration of all valuable documents generated during system design.

Output document:
Product detailed design instruction, data Physical Design Model (PDM), custom data type and Bo data type files, data dictionary, system test cases, Object Model (OOM)

V. Coding
Software coding, implementation of each interface.
Unit test.

Implementation Suggestions:
High-qualityProgramDesign training, giving them the skills to write high-quality programs.
Perform "version control,CodeTraining in review, test, and error correction to improve their work efficiency.
The development team can appropriately reduce the test workload based on resource and time constraints of the project.
Manages configuration of all code and valuable documents generated during implementation and testing.

Output:
Unit Test Report and Code Review Report

Vi. Integration Testing
Test the system's functional requirements based on system test cases to ensure that the system's normal function processing and exception handling are correct.
The focus of user interface testing is to test the ease-of-use and visual effects of software systems.
The robustness test is used to test whether the software system can run normally in case of exceptions. (Fault tolerance and recovery)
Security Testing (This test can generally be evaluated by CCB's fortify software)
If the product needs to be installed, it must undergo installation and reverse installation tests.

Implementation Suggestions:
Train System testers to improve their testing efficiency.
The Project Manager and test team manage to reasonably reduce the test workload, such as reducing "redundancy or invalidity" tests, based on project resources and time constraints.
The system testing team may modify the document templates of this specification as appropriate based on product features.
Manages configuration of all code and valuable documents generated during system testing.
To motivate testers, we recommend that you set up incentives for enterprises or projects. For example, you can grade the rewards based on the severity of the defects. Each new defect corresponds to a bonus, send the bonus to the first person who finds the defect.

Output:
System Test Report, defect management report, Operation Manual

VII. Customer Acceptance
Results review. Acceptance personnel review the deliverables that the developer should deliver, such as codes and documents. Ensure that these results are complete and valid.
Acceptance Test. The acceptance personnel shall conduct a comprehensive test on the delivered products to ensure that the functions and quality of the products meet the requirements.
Promptly solves problems discovered by the customer.

Output:
Customer Acceptance plan, acceptance test cases, Customer Acceptance Report, and acceptance Operation Manual

Implementation Suggestions:
Before the customer's acceptance, the developer shall conduct necessary product training for the acceptance personnel.
Developers can give system test cases to acceptance engineers for reference to reduce the time required to design test cases.
Developers should enthusiastically assist acceptance personnel. The Software defects discovered by the acceptance personnel should be corrected immediately; for complex problems, the relevant leaders should be requested immediately, without delay. Do not quarrel with the customer during the Acceptance Period.

Good impression.
Manages configuration of all valuable documents generated during the acceptance process.

VIII. Completion
Comparison between the plan and the actual situation: product functions, work results, product quality, input personnel, workload, cost, etc.
Reason for application completion and project self-evaluation
Make a comprehensive evaluation of the project and summarize the lessons learned.

Valuable end-to-end management includes at least three items:
I. Liquidation of tangible and intangible assets of the project should not only prevent the loss of assets, but also promptly use these assets.
2. conduct a comprehensive assessment of the project. For example, evaluation of project completion, project quality, input-output analysis, project market value, project contribution to the enterprise, etc. This evaluation report can be used as an important basis for assessing project staff performance.
Iii. sum up experience and lessons to benefit the entire institution.

Implementation Suggestions:
Configure and manage all valuable documents generated by the domain during the completion management process.
Keep necessary confidential.
The completion review cannot be simplified.
Conduct necessary training for the completion Review Committee so that they can establish a correct concept and strictly control

Output:
Completion application and completion Review Report

The following is the use experience of these core tools:
1. Must be createdSource codeThe version control system is cvs. The basic code submission principles are as follows:
1) programmers try to submit only once a day before work;
2) The submitted code must run properly on your own machine;
3) Each submission must provide a brief description of the Code submission function.
2. Create an Error Tracking System. Use Bugzilla to configure the email system. This makes Bugzilla a bridge between testers and developers.
3. using BAT and Perl scripts, we can use the source code in CVS as the core to implement a simple daily compilation tool. We can put this self-written automated tool on a dedicated compilation machine, automatically downloads and compiles the code every midnight.

, Automatically package the installer, automatically record various compilation logs, and automatically place the installer in a fixed public area named by date. (Use cvs2cl. pl To get the Code Update log uploaded by the programmer for the tester's reference)
4. On the next day, the tester should go to the public area to get the latest version of the previous day, and test the new version according to changelog. The bugs found in the test are fed back to the programmer through Bugzilla. Programmers can

, Or company rules to decide the time to modify these bugs. And write the changes to these bugs into the code log when the code is submitted.
5. The next day, the developer should check the compilation log in the public area to check whether the module is properly compiled, correct it in time, check whether there is a bug report in his mailbox, and modify it in time.
6. on the second day, the management personnel can determine the development direction of the product based on the overall project requirements and the version progress of the previous day. If there is any yaw or misunderstanding or new requirements, it can be adjusted in time according to the current situation.
In this way, through CVS => Bugzilla => daily-build, programmers can interact with testers and perform their respective responsibilities. Reduce the communication and human troubles. The management layer can also be well aware: Because there are new versions every day,

Keep abreast of the Product Trend... And so on.

 

From: http://www.javaeye.com/topic/470476