Collaborative development practice summary
Collaborative building including pair programming, formal inspection, informal technical review, document reader, and let other developers create shared technology code and other work product liability.
- Collaborative build other quality assurance complementary technology;
- Build collaborative corporate culture conducive to teaching and programming expertise;
- Collective ownership applies to all forms of co-constructed;
- Collaboration should be maintained before and after the build.
Pair Programming
Knot key to successful application programming
- Encoding specification for programming support node;
- Do not let the pair programming becomes a spectator;
- Do not force the use of pair programming on a simple question;
- Regularly to carry out the rotation of the junction and the staff assigned tasks;
- We encourage both parties to keep up with the pace of the other party;
- Confirmed that two people can see the display;
- Do not force the programmer of tension between people with their counterpart;
- Avoid novice combination;
- Specify a leader.
- Knot benefit to programming
Knot benefit to programming
- Pair enable people to maintain a better state under pressure;
- Code quality can be improved;
- Can shorten the time schedule;
- Dissemination of corporate culture to guide junior programmer, culture collective sense of belonging.
Checklist: Effective pair programming
- [] Whether there is a coding standard to allow programmers to always concentrate to the programming, rather than discussing coding style?
- [] Pair of twin whether all actively involved?
- [] Whether to avoid abuse of pair programming, choosing instead to derive the benefits of those jobs can be pair programming?
- [] Is there a regular work tasks and personnel rotation?
- [] Knot match each other in the development of a combination of speed and personality aspects?
- [] Is there a leader focused on project management and communication with others outside of the project?
Official inspection
Although any review are designed to have the design or code, but formal check (detailed investigation) are still several key issues with the general review differ.
- Detailed investigation is concerned at the problems encountered by previous reviewers;
- Detailed investigation focused on the detection of defects, rather than amended;
- Review personnel sift meeting waist well prepared in advance, and bring a list of known problems they found;
- Participants have been given a clear role;
- The host is not detailed investigation of the product to be inspected;
- Detailed investigation host should have received a detailed investigation of the chair aspects of training;
- Only participants held a detailed investigation will be doing after meeting fully prepared;
- Each detailed investigation of the data collected will be applied to the subsequent detailed investigation, in order to improve detailed investigation;
- Detailed investigation of senior officers not to participate in the meeting unless you are a project of detailed investigation plan, or other data management, but technical director may participate.
Detailed investigation of the general steps
- plan;
- Overview;
- ready;
- Detailed investigation of meeting;
- Difference report;
- Rework;
- follow up;
- The third hour of the meeting.
Checklist: Effective detailed investigation
- [] Do you have a checklist that allows commentators to focus on areas where problems have occurred?
- [] Do you focus on finding errors rather than correcting them?
- [] Do you consider making a certain perspective or scenarios to help focus the attention of commentators at the time of preparation work?
- [] Do you give commentator enough time to prepare detailed investigation before the meeting, if everyone made preparations?
- [] Whether each participant plays a definite role - host, commentator and recorder and so on?
- [] Whether the meeting at a speed of some colleges and universities?
- [] Whether the meeting is limited to less than two hours?
- [] Whether all participants in the conference have accepted a difference of targeted training in how to conduct a detailed investigation, whether to accept a host of targeted training in skills presided over?
- [] Error each time whether the data detailed investigation found are collected, so that you can later use to adjust the checklist of the organization?
- [] Whether the data collected detailed investigation of speed and speed of preparation, in order to optimize your preparation and after detailed investigation work?
- [] Whether each detailed investigation was assigned to go on activities are properly followed up, either by word or re-host their own detailed investigation?
- [] Does management understand that they should not be involved detailed investigation of the conference?
- [] Is there a follow-up to ensure the correctness of the amended plan?
Other types of collaborative development practices
- Walkthrough;
- Code reader;
- Public demonstration;
Points
- Collaborative development time can often be found with more defects than testing, and more efficient;
- Collaborative development practices found in the type of error is usually found with different tests, which means you need to use both the amount of detailed investigation and testing to ensure the quality of your software;
- Through the use of an official inspection checklists, preparation, roles clearly defined and continuous improvement of the method, the defect detection efficiency gains to the highest;
- Typically, and detailed investigation of the pair have the same programming costs, and can produce a considerable quality code;
- Official checks can be applied to gnaw on the outcome of a lot of work outside of the code, such as requirements, design, and test cases and so on;
- Walk-code reader and are detailed investigation of alternatives. Read the code more flexible, effective use of everyone's time.