Software project management processes and methodologies

Will soon usher in his own life in the first software project management work, the first to collect relevant knowledge to collate a software project management method I decided to use, in practice and gradually improve. See this article and have their own experience and views of prawns welcome correction and communication, we have to do this is the Enterprise information management software

Reprint Please specify source: Jiq's technical Blog

Project Management Process1 Demand Research phase

n project and feasibility analysis

N Demand Collection, collation

Deep-line and user communication, to obtain the most original requirements, and then based on experience for the user to comb the management process, optimize the management process, establish management norms, collate the final requirements report, to the user to confirm, as the basis for development and communication with users, the requirements of the collation of the functional and non-functional requirements.

n Requirements Review

Organizational review needs, but also the role of organizational learning needs

Output: Demand research Report

2 Overview Design phase

N function Point Division

First, we need to split the requirements into corresponding function points, note that the demand and function points here may be many-to-many management;

Secondly, we should design and organize the module, and usually draw the navigation menu in the way of mind map;

Finally, it is necessary to determine the overall architecture of the system, including the logical and physical architectures, and the technology chosen.

Output: Navigation map, overall architecture, List of function points

n Develop a development plan

The project manager formulates the development plan, divides the function point according to the priority to divide into three stages, indicates the time that each stage completes, the function point which is assigned to specify the specific responsible person and the participant, selects the development pattern (waterfall, iteration, agile, etc.).

The development plan is then entered into the Task management tool.

The final development plan is to identify each function point.

Output: Project overall plan, including function Point development plan

3 Detailed design phase

n function Point design

Function point design can use an Excel description, create a few sheet, respectively, the version information, interface layout design, input form, output report, flowchart, operational requirements (ease of use, security, performance, data volume, concurrency, etc.), the required database operation interface, and even can include test cases.

In addition, you design database tables, roles, and permissions (navigation and data).

Note: First of all, this stage does not require the design of all people, you can arrange for other people to carry out technical pre-research, development environment preparation, such as pre-work. Secondly, after the design of this phase is completed, it is important to organize the project team members to review to determine that there are no problems to meet the needs of users before starting coding.

Output: Detailed design documentation

n task Assignment or pickup

After the design is completed, the task needs to be assigned or picked up, and the corresponding task is entered into the Task management tool.

Output: Detailed development task plan

4 Coding Phase 5 test Phase 6 release phase
Project Management Tools

Requirements gathering and Finishing phase: Word, requirements management tools

Overview design phase: excel+ Brain Map +word

Detailed design phase: Excel+ppt+word+powerdesigner

Development phase: WSS or MS Project management task progress, SVN management code

Test phase: Bug Management tool

Requirements management tools, tasks, progress management tools, bug management tools, these three tools can be selected individually, you can also share one, such as WSS

Document management tools: SVN

MindManager: Project group structure Management

Qq,msn,skype: internal and external communication within the project group

Project Management Tools

Periodic code reviews between project members: Software quality can be submitted

The project manager approves each completed function point or organizes the project team review

The project manager summarizes all proposed bugs and distributes them uniformly

Weekly meeting Summary and next week schedule

The daily state will tell you what was done yesterday, what you are going to do today, and there is no difficulty

Software project management processes and methodologies