Putting it into practice

Managing parallel development can be very simple and easy if one adheres to the guidelines listed below:

·         Create separate environments for each parallel thread of development.

·         Document all changes in a central change-tracking tool and assign each a unique reference number.

·         When modifying source ensure that this source is mod marked to cross-refer to the change reference.

·         Generate weekly reports to identify new items, those items that have changed in one release only and those that have changed in both releases.

·         Set the synchronisation and retrofitting point as high in the life cycle as possible.  End of system test is a good point.

·         On a weekly basis generate reports to identify the level of parallel development

·         On a weekly basis copy new items from the current release to the next.

·         On a weekly basis copy items that have changed in the current release only.

·         On a weekly basis retrofit changes that have to items that have been modified in both releases.