Rework

Process

Priority and release version should be frozen

Requirements should be accepted through ticket/document

Environment should be defined correctly & informed during the initial phase

NFR should be properly defined before sign off

Identify dependencies and prioritize accordingly

Source/target details should be available before start of testing

FSD should be frozen before including NFRs

Survivorship rules between integrated systems should be defined properly during initial phase

Scope of the releases and the dependent interfaces should be clearly defined

Ensure beforehand that full data file is there

Data profiling should be done before starting the build

SPOC for each interface

Technology

Maintain Project folders and proper version tool/change log

Automation to get count of records

People

All stakeholders should be present in requirement stage

Reasonable resources - both time and environment should be allocated in Dev phase

BA/Functional team should be involved during requirements discussion.

The stake holders should be informed about the dataload being done

functional and technical team to provide quick turn around.

Train the developers on all the features

Communication/Information

Detailed session for understanding documents/program in initial phase

Proper internal communication

Source teams should be intimated in advance

Inform for change in SIT start date

Documentation

Availability

Proper test data should be available

Debugging utility should be made available to the developers

Maintain Project folders and proper version tool/change log

FSD should be upto date

click to edit