When we’re running IT projects it’s important, of course, to stay on track and follow the agreed upon customer requirements.  The goal is, after all, to deliver a system to the customer that they want and need, and that their end users can use.  Whether that is a project within our own organization (internal customer) or to another organization (external customer) does not matter.  The end goal is still the same.  A useable system and a satisfied customer and user base.



What we don’t want to do is go through the project with blinders on and forgot to consider everything possible about how the new project or new system we are rolling out will integrate with the existing business and technology infrastructure.  Do not underestimate the time and effort needed to integrate a new system into the existing business and interface it to existing systems.  On some projects this is where the rubber meets the road.  Many projects have been lost after being successful 90% of the way only to hit a wall and go way over budget just trying to get it to tie into the current systems and structure that it must interact and interface with.



Basically, project managers need to be sure that the project schedule allows some contingency for slippage and that they are informed whenever staff encounters this.  Project managers must plan for any integration tasks from the start of the overall project, not leave them until the end. The following are some considerations:

 

 





     
  •  
  • Review those interfaces used on other projects that may influence this project.




    •  
  •  

 

 

 

 





     
  •  
  • Define all project interface requirements.




    •  
  •  

 

 

 

 





     
  •  
  • Be certain that there are not too many third-party contractors all working on separate integration plans. A single, coordinated effort is more desirable.




    •  
  •  

 

 

 

 





     
  •  
  • Identify all possible risks and issues in a risk management plan.




    •  
  •  

 

 

 

 





     
  •  
  • Define the communication between all interested parties.




    •  
  •  

 

 

 

 





     
  •  
  • Define the output for each project deliverables.




    •  
  •  

 

 

 

 





     
  •  
  • Document the data conversion process.




    •  
  •  

 

 

 

 





     
  •  
  • Establish a change control procedure.




    •  
  •  

 

 

 

 





     
  •  
  • Be certain that there is a plan for integration testing.




    •  
  •  

 

 

 

 





     
  •  
  • Ensure that a contingency plan takes effect in the event of system failure.




    •  
  •  

 


Summary