Tailoring Processes - Modifying Standard Processes to Suit a Project

Tailoring Processes - Modifying Standard Processes to Suit a Project

Product Competency 9:

Tailoring Processes - Modifying Standard Processes to Suit a Project

As discussed with competency 1, "Assessing Processes" it is often useful to customize or tailor processes, procedures, and life cycles to meet the specific requirements of a project. The tailoring activity usually begins with the project manager's selection of the most apposite life cycle for a project. "Selecting Software Development Life Cycles" covers the features of various software project life cycles and provides guidelines for selecting an appropriate one for a given software project.

Typical organizational formations are not appropriate for all software projects. It is important for the project manager to recognize the type of organizational formation best suited for the project at hand, bearing in mind the environment in which it will operate. The forms of organization defined in "Choosing an Organizational Form" contain: functional, project expediter, project coordinator, and matrix. Each of these will be described and discussed in terms of advantages and disadvantages.

Tailoring the project processes and environment must be done with consideration to all dependencies. Most tasks are not carried out in isolation on a project. Identifying proper dependencies is a key part of getting the schedule right. "Considering Dependencies" talks about some of those "tailorable" dependencies common in software development projects, including: company-wide support, configuration management, project management, and SQA; potential problem identification - high fan-in or fan-out, circular relationships, identifying the critical path, and the critical chain through unique resources; and contracting relationships.

There are no instructions here, but only suggestions as to how the modification of tried and true methods can benefit the project. Flexibility and "out of the box" thinking are often required for appropriateness, effectiveness, and efficiency.


configuration management, life cycle, software development project
The contents available on this website are copyrighted by TechPlus unless otherwise indicated. All rights are reserved by TechPlus, and content may not be reproduced, published, or transferred in any form or by any means, except with the prior written permission of TechPlus.
Copyright 2018 SPMInfoBlog.
Designed by TechPlus