Sharing of project information is of utmost importance to the organization.Project knowledge is shared on multiple systems, services, and apps. The array of locations is becoming hard for some of the project team members. what are the options for the project manager to manage the project knowledge in this situation? Saving Changes...
Shadav,
Are you asking regarding project plan information, or technical product knowledge details that have to be shared between contributors? Those can be two very different questions. Saving Changes...
Anton OosthuizenSenior Business Analyst / Project Manager| Self EmployedPretoria, Gauteng, South Africa
Obviously having a good collaboration platform is important when sharing knowledge and I found that tools like MS Sharepoint, IBM Connections and Jira/Confluence works well. While the first two works well for document management the Jira/Confluence combination works well in an Agile environment where it allows you to keep the link between issues/backlog/sprints and the relevant artifacts.
But the biggest issues I've always found with collaboration platforms is that they are REALLY bad is not setup correctly. Finding something on them can become a nightmare and knowledge sharing goes out the window since you cannot share what you cannot find. So implementation is crucial. Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
This is a decision that should be made at the organization/PMO level, then supported by the projects. There is certainly a need for practicing Knowledge Management at all times for maintaining related content; with accessibility, continuity, and findability, avoiding disconnected and disparate information. There are tools to enable and support such as SharePoint, Confluence, etc. Either direction, there should be a standard process with education.
What kind of story will you have if there are missing pages? Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
My recommendation is creating a knowledge management system, where system is not software, software could be a component into the whole system. Key thing is to support the whole process. That tool does not matter, believe me. Saving Changes...
Sripriya NarayanasamyAuthor, Say Yes to Project Success| Director, KeyResultzChennai, Tamilnadu, India
Sharepoint, Confluence are great options to share the project knowledge. But, even with big delivery organizations, most of the time, people do not look through these internal tools.
Though not having enough time to plan is often the excuse given, I feel when you want it, you should find the time. Saving Changes...
Hi All,
Thanks for your goods points. Saving Changes...
Daniel GustProject Portfolio Manager| Previously at Intrepid Solutions and ServicesLand O Lakes, Fl, United States
Shadav, I would say Sergio hit the nail on the head by pointing out that knowledge management systems are the key. Although I disagree with his point that the tool doesn't matter (if a tool is not intuitive, people will not use it), the key is getting members to contribute their knowledge on different aspects of the projects. It also helps when bringing on new team members to have them spend some time creating a project history from their background that highlights their successful and unsuccessful projects as well.
Learning from the past is critical to future successes; using the KM system as an archive of projects, to include the best practices and failures helps those that come after us to better position themselves for success. Saving Changes...
