User Scenario: one of the team is working on SAP and other team is working on SharePoint Online. It is often required to communicate between two teams but most of the times I see that there is a huge gap and data never comes on time or not in proper format. Team meeting is not so easy since both have different reporting managere.
What is the best way to break the ice so that work should not hamper? Saving Changes...
RAJESH K LProject Manager, PMP| Bharat Electronics, Bengaluru, IndiaBengaluru, Karnataka, India
Best is have a face to face discussion and openly discuss all contentious issues. 2 or more sittings may be required to resolve all outstanding issues Saving Changes...
The first step when the project was conceived should have been a proper, documented expectation setting that would cover possible risks. Charter should have handled it. Was it created? Saving Changes...
Deepesh RammoorthyICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood ServiceTarneit, Vic, Australia
Who best knows the dependencies between the two projects?
If there is at-least one person each from the SAP side of the Fence and SharePoint Online Side of the Fence, they should be having a chat first thing in the morning everyday.
Is it possible to appoint a single Program Manager to oversee both these projects? Their main function is to keep an eye on the dependencies between projects in their program. Then in the Steering committee meetings , the projects in the program should be presented and the management then knows what exactly is happening in both projects Saving Changes...
A lot of good points above. To me it looks like some silo's have formed and if possible I would recommend just like above a quick standup meeting each day with each lead and if not possible or teams are remote sharing daily and weekly updates and if there are any common goals they should be highlighted and communicated across the teams to help with collaboration. Saving Changes...
Not only for SAP and SharePoint Online, communication breakups due to different systems being used often occur.
From a technical point of view, some information sharing will be possible through the use of the automatic reporting features that come with the product.
I also think that those systems can be interconnected.
However, I feel that the essence of this problem is not that information cannot be shared due to differences in systems, but that important information that is relevant to decision making for each team cannot be identified.
First of all, it is necessary to define what kind of information is to be shared. Saving Changes...
Hi Ashutosh-
Conduct meetings that would collect metrics for all the communication platforms that are used and determine how they would be used in the project. Saving Changes...
Focus on resolving WHY there is a gap. More meetings won't help you if the root cause hasn't been fixed. This doesn't need to be complicated by having huge meetings with lots of managers. Brainstorm on how can you/your team make it easy for those people to give you correctly-performed deliverables? Saving Changes...
Denathayalan RamasamyChief Technology Officer| Atal Incubation Centre -CIICChennai, Tamilnadu, India
My proposal will be take 3 lazy (they will give more smart ideas) people from each team; brainstorm the ideas for common communication format using tools like MS teams or JIRA, then document it Team Charter for consolidated one & communication planning documents Saving Changes...
Justin FuSenior Systems Engineer| ParsonsBristow, Va, United States
