process tailoring in process development example

process tailoring in process development example

Examples of Process Tailoring in Development Projects

 Development projects use the processes for gathering and analyzing the owner agreements, and then develop that into a software application(s). The process followed will be care of requirements, design, development, testing, implementation, and warranty support for the project Different literature and survey of practices indicate that there are different models are for development projects. Some of these models are waterfall, iterative, spiral, prototyping, RITE, and so forth, explanation of these models is given in Chapter 1. The most un model is size or spiral model and traditional stages are broken into smaller processes so that the parallel creation of the processes can take place without losing sight of the customer needs. After choosing the sand processes (which are already defined by the organization based on the past openers in en g similar development projects), a coloring process from previously defined coring guidelines is selected. This way, the project gets flexibility but in a restricted manner and at a high level, essentially prepares subgroups among standard development processes. On the basis of not, a project manager can choose one or more of these subprocesses.

Tailoring processes is a way of adjusting the standard processes of the organization so that double effective process can be defined for a project. This tailored process will help in meeting business needs and technical specifications of the project. The tailored process is arrived at either by adding deleting or modifying the defined standard process such that the final process is best suited for achieving the objectives of the project. A decision is taken during the tailoring process as to what level of tailoring is allowed in the process definition. Unlimited tailoring will imply that it is free for all and there is no standard process available. Tailoring guidelines are sued to control this level of deviation from standard processes. These sets of guidelines are nothing but a combination of permissible rules for modifying rules. Thus, one can explain that the tailoring guidelines are a set of permissible deviations of the organization-wide defined standard processes so that the bene

effective, and the optimum process can be defined for a new project. For example, let the construction or code-writing phase of a development project. As per the standard pro a code review process for each and every line of code being written. Code review is a process for a development project because, before sending the code for testing, any defect to specifications in the design phase will be detected in the code review process. Also, code detects any discrepancy with respect to code-writing standards that need to be followed by writing codes. Thus, the process adds a lot of value for quality for all deliverables. But sometimes the code review process is time-consuming and may not add value to the quality already existing in the code. This could be because code could have been written by an experienced and skilled team member or the code could have been generated using a code generator. In these circumstances, code review becomes a burden to the project as it increases total project effort and affects the schedule of delivery. Also, the review can be done by a single person or a group. In these cases, tailoring guidelines can help to fine-tune the standard processes and define an optimum process such that both high quality and productivity can be achieved. Tailoring guidelines can suggest that a project can do code review for complex and difficult programs while simple and easier programs can be reviewed by the developer himself. The guidelines can also suggest that a complex program can be group reviewed in which a group of team members will review the code and detect any anomalies with respect to design specifications.

Tailoring guidelines also records experience and knowledge of a team members who have executed similar projects in the past. These team members, who have used similar tailoring guidelines, share their experience, and these are recorded in the process repository. Using these experiences, new project members can decide as to which processes need to be tailored so that optimum results can be achieved. Steps involved in the tailoring process are as follows:

 (1) identify the standard process that needs to be applied,

 (2) identify unique characteristics of the project,

(3) discuss among team members and experienced personnel (often from quality department) to decide which tailoring guidelines need to be applied,

 (4) take approval from senior management,

 (5) record the tailored processes in the project plan document, and

 (6) Share this plan with all the team members.