Satish SharmaCertified SAP S4Hana 1909 Financials Expert| FreelanceNew Delhi, India
For project continuance in an environment of attrition, it is very important to keep project knowledge intact and retrievable to offer guide to the starter in the middle, what all are the tools and techniques employed to manage project knowledge? Saving Changes...
Deepesh RammoorthyICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood ServiceTarneit, Vic, Australia
In my view the most important artifacts can be easily held in simple Microsoft Documents (Word, excel, project, visio) on a Network Folder .
These should be elaborate enough to enable the new starter to pick up and run or get a pretty good overview of the Project.
These could be the Project Management Plan, Issue Register, Risk Register, Business Case, Financial Spreadsheets, Test Plans, Test Summary Reports, Meeting Minutes, Project Change Requests, Solution Architecture, Design Diagrams
There are off course other collaborative tools like Share Point Online, Alfresco, Confluence , Your company's intranet which can be a repository of information on the project where the very same documents can be held.
Again, depending on the type of the project you are running, you could also have other specialized repositories like Subversion , JIRA, HP Quality Centre, Smart Source Tendering, Enterprise Architect.
It also depends on what kind of information you want to store as well.
But of paramount importance is to find out what the Team is and how and where they store the information. If you are the one who is thrown into the deep end, it is incumbent on you to consolidate all the repositories into one place for your own benefit or to help in succession planning should you wish to move on Saving Changes...
