Software project development processes that regulate how

In the software development project management process, how often such a scenario: developers do not know when to turn test; project managers take a Excel document out of the group, a task should be done the day before, how have not begun to do; this is part of the UI front-end ask who is doing what can this be done; test line, said this bug and who changed out, this did not turn this test module ...... and so on. Collaboration whole feeling mess, full of atmosphere within the team and complained about the rejection of the pot. Software project development processes that regulate how, team members can be targeted, in unison, so that the product iterations full sense of rhythm. Based on the research and development project management experience I finish, I hope, serve, and to explore effective team collaboration process mode.

1. Collaboration flowchart

The basic principle:

1. All problems can be tracked (demand, Bug, optimization)
2. All work transparency (work progress, Block factor)

2. Detailed contents of each stage

2.1. Confirm requirements gathering

This stage is mainly related to the product manager Activities:

1. Product manager collected before the beginning of each version of the periodic needs of all parties, including customer feedback, source, output requirements led the list of comments (for many SMEs, the boss is the greatest "user"), market research and technical teams demand
2. Held in the beginning of the previous version release planning meetings , participants including project managers, product managers, and core members of the project, according to a priority list carding demand, the output of the next version of the preliminary list of tasks (initial reason why, is because the back of the list may is adjusted according to the assessment)
3. Product manager to complete the task based on the preliminary list of detailed requirements documents, organize team members - including the relevant UI, development, testing, held a needs assessment meeting , the output of the corrected time and review comments
4. Product manager for advice needs assessment team meeting proposed recommendations, timely correction requirements document within the corrected time, and promptly notify the relevant team members, document output needs identified

Note: After review meeting the demand, a preliminary estimate of time the task assigned claim preliminarily determined measurement turn, on-line time node

2.2. Design and Development

1. The project manager needs to complete the task dismantling according to the document, and create a corresponding task list in a task management system, specify Managers
2. Attn unclaimed after each mission, according to the duration of their mission, timely communication with the relying party, determine dependencies task completion time, so as not to affect the progress of their mission, problems and timely feedback to the project manager.
3. After the UI design is complete, developers associated with product managers need to confirm UI design, if it involves more content can be organized UI review meeting (by the product manager or project manager to weigh Organization)
4. Involved in the process of development tasks need to have the necessary design, technical responsible person responsible for the design review , no review of the design can not be developed; tasks need to be completed to develop the code review
5. Project managers regularly organize regular items (emergency version is recommended once a day, a longer-term version is recommended once or twice a week), continue to follow up the progress of tasks and problems, and timely coordination process, in order to protect the progress expected
6. One day, written before the scheduled transfer time measurement node developers turn detected document describing the contents of this release adjustment (attach task lists) and notes, and inform project stakeholders (nails or group e-mail)

2.3. Test

1. After the needs assessment meeting, testers need to write test cases document the various functional modules, and the organization before the transfer test test review meeting , to be reviewed various aspects of each function and leak filled
2. A task batch release testing according to the situation, and to determine the content of each node and the rotation sensed time; after completion of the batch testing, integration testing for an on-line before, attention reserved for a certain time fixes
3. The test is completed, test results need to be informed of project-related personnel (group nails or mail), including whether the remaining issues and reach conclusions on line requirements

Note: Product Manager for development can be achieved acceptance in the transfer test to determine whether the development of the actual needs for timely adjustments

2.4 On-line

1. On-line personnel have to prepare prior to on-line on-line program file, recording the on-line content, and the on-line operation deduction, all the operations involved are recorded according to the step, such as a database operation, the code merge, jenkins constructed like; possible Note the problems and the corresponding treatment options, and to submit the relevant person in charge of technical review
2. Project Manager in conjunction with test results and other aspects of the case, whether the decision on the line, and opinions to inform project stakeholders (nails or group e-mail)
3. On-line person steps on-line documentation of the program, in order to complete the operation on-line (on-line operation is preferably completed by at least two people, one person, one person view, to avoid making mistakes)
4. After the completion of on-line, testers and product manager for the on-line for online verification process to ensure problem-free online functionality
5. After verification, the project manager or other designated person responsible for the on-line notification issued to stakeholders, including the project team all members and associated partners, the on-line time, on-line content, factors, considerations, etc. (instant messaging groups, or mail )

2.5. Replay

1. After the release, the project manager according to the situation of the previous cycle recovery disk tissue wrap-up, summarize problems and causes, and ways to circumvent the existing follow-up, summarize experience, etc.

The above stage is not entirely serial advance, there are some interludes between each other, such as collecting the next version needs finishing with the current version of the development is advancing in parallel, development and testing can also advance in parallel in the form of a phased transfer of measurement ,and many more.

3. Some common tools

1. jira task manager for the project, which Agile plug-ins can easily view the overall task panel, task status at a glance, request team members develop the habit of timely update status
2. confluence document management, centralized maintenance for all types of documents, such as the above-described requirements documents, design documents, test file transfer, on-line documentation, etc. can be used in the form of project space confluence of centralized management.
3. gitlab code management
4. jenkins project deployment build tools
5. nexus maven to build a private library

4. Summary

Emphasis on team work pace and rhythm, a good flow and a level of specification that allows the average person can fully play its role, allowing the whole team to forge ahead, efficient output. Not a good process, or simply do not pay attention to the process of the team, but often a mess, thrown pot filled with complaining, low combat effectiveness. In this paper, a relatively coarse granularity of the basic processes of project management software, made the introduction, more details of the content may need to be treated with the team and dealt with accordingly based on the internal situation.