Project integration can be tricky when you combine multiple technical components, processes, or both. Most people focus on the technical side of an integration. Yet, the problems in integrations are often technical errors caused by communication and human elements. Here are some actions that help prevent technical issues with integrations.??
- Specifically assign ownership. Two or more teams serving as owners on an integration exercise is asking for trouble. Like with project tasks, assign one owner to coordinate integration efforts and guide the teams. That way, decisions are made on time and you avoid the “left hand thinking the right hand was working on this” type of issue.??
- Create a communication plan specific to each integration. Communication between all teams is critical for success in integrations. Create a communication plan so all parties know how, when, and who will direct integration teams. It doesn’t have to be overly detailed. Make sure that team communication is managed and kept in a version-controlled central location. Assign primary and backup points of contact. Share issues related to people or technical issues between teams with critical project personnel even if they aren’t a member of an integration team (think project manager).?
- Create cultural alignment. Teams from different companies or geographies will have different cultural norms. As a result, decision-making, problem-solving approaches, and engagement with different companies can vary dramatically. Creating cultural alignment around how the teams operate is important for integration success, but often overlooked. Work with the people assigned as integration owners to create cultural alignment between teams in an integration exercise.?
- Don’t skimp on travel. Integration teams must work together smoothly, and technical integrations must work perfectly to achieve project success. Allow the teams to work in the same space and examine the same technical tools and components together. This makes a huge difference when it comes to working efficiently. You can avoid expensive technical misinterpretations by co-locating integration team members at various times during their work. The efficiencies gained and the technical errors avoided will more than make up for the travel expense.
- Assemble the best possible change management review team. Integrations are complicated. Effective change management is crucial. A review team with knowledgeable team members and management is essential. Experienced integration project managers will often have a different review team for integration changes because of the depth of knowledge required to make appropriate decisions. This often means two change reviews, one with the integration review team and the second with the standard project review team. The extra time is worthwhile to ensure the best minds review integration-related changes.
Office Hours Live - Survival Tips for Managing a Difficult Boss
Wed, Dec 4, 2024, 9:00 AM MT
We’ve all had at least one – a boss that makes our jobs challenging if not impossible. They come in several forms, each with their unique challenges, such as the clueless chameleon, the MIA boss, the meddlesome micromanager, the wishful thinker, and more. In this Office Hours, Dana Brownlee
joins me to talk about the different types of difficult bosses and what we can do to work with them successfully. To sign up, click here
.
This article belongs to the?Bonnie’s Project Pointers newsletter series
, which has more than 80,000 subscribers. This newsletter is 100% written by a human (no aliens or AIs involved). If you like this article, you can?subscribe
to receive notifications when a new article posts.
Want to learn more about the topics I talk about in these newsletters? Watch my courses
in the LinkedIn Learning Library and tune into my LinkedIn Office Hours live broadcasts.
Great perspective Bonnie, the focus on the tech often means the people side of integration is underserved.
Applying Systems Engineering Principles, Processes & Practices to Increase Probability of Program Success for Complex System of Systems, in Aerospace & Defense, Enterprise IT, and Process and Safety Industries
1 周The challenge is: ? Assign ownership to "what" outcomes and processes to produce those outcomes ? What communication processes are needed, and who defines those? Contractual requirements, all the way to 5 people in the same room ? Aligned around what outcomes. In our domain, Capabilities-Based Planning is mandated, stating what capabilities are needed to accomplish the mission or fulfill the strategy and what are the Measures of Effectiveness and Measures of Performance are before any work starts. ? Change management can range from sticky notes on the wall to processes requiring signoff to the chief of operations, which is highly domain-dependent. These are all great principles but practices are critical . Great quote Yogi Berra In theory there is no difference between theory and practice. In practice there is.
strongly agreed and great posting
Healthcare IT Professional | Senior Clinical Informatics Specialist
1 周Certainly, by focusing on communication and teamwork, you can avoid many technical problems in project integrations
Desenvolvedor Full Stack Java
1 周Excellent article. I'm seriously considering transitioning to the field of project management.