Scribd
Upload
41 views5 pages

PMO Knowledge Base

This document outlines requirements and plans for building a knowledge base integration project. It details 6 requirements including making the interface user friendly, allowing all employees to save documents and procedures, and integrating with other databases. It also defines key aspects like knowledge sources, page structures, and approval flows. Finally, it presents a macro plan to define internal resources, build an MVP, conduct a proof of concept, and schedule testing and go-live.

Uploaded by

Leonardo Rocha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
41 views5 pages

PMO Knowledge Base

This document outlines requirements and plans for building a knowledge base integration project. It details 6 requirements including making the interface user friendly, allowing all employees to save documents and procedures, and integrating with other databases. It also defines key aspects like knowledge sources, page structures, and approval flows. Finally, it presents a macro plan to define internal resources, build an MVP, conduct a proof of concept, and schedule testing and go-live.

Uploaded by

Leonardo Rocha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 5

WE ARE VENTIENT ENERGY

PMO Knowledge
Base
Integration - Project Summary
Date – dd/mm/yyyy

EN_PPT008V00_M&A
Requirements

1.Requirements

•Being Build from an office 365 environment;


•User friendly interface;
•Allow all of Operation employees to save documents
•Allow all of Operation employees to record / save a procedure (Lists or forums)
•Create filters to let all of employees to research
•Create a departments structure in order to turn out to be easier to find out the information
•Create a workflow so as to ensure the knowledge and lesson learned has to be approval by the
manager before publishing
•Create automate flow to receive updates when a forum was updated by user with a remark
regarding a knowledge that was released before
•Split the knowledge base between Project and Business as usual
•Build the forums or lists considering a research with key users
•Take into considerations integrations with others database or SW such as Modern PMO
•Ensure that will be integrated with teams

Generating renewable energy to secure the future of people and the planet
2
|

EN_PPT008V00_M&A
Definitions

1. Create a new Sharepoint on line page


2. Define source of knowledge: Project lesson learned and BAU knowledge. Will you consider
others, such as training?
3. Define pages embedded in SP. We can create department embedded pages and inside these one
create one page for Project and other for BAU.
Heads up: In case of BAU we will define BAU as only technical task performed by Asset Management
in order to make an preventive or corrective maintenance or we will consider any kind of routine
tasks done in all operations

4. Will the knowledge will be shown up by frequently asked questions F&Q with filters to research or
will use also documents saved in libraries?
Inside the Knowledge internal pages;
 BAU »» we are going to define knowledge source: Only F&Q filled in by operations teams with
documents embedded or also others kind of source : Publishing in the page such as newsletter or
procedures attached in library?
 Projects »» we are going to define how the project lesson learned will be captured and where. I.e
Lesson learned gathered in Modern PMO in this case we will have to build a flow in order to send
this information to a list in Knowledge Base
Generating renewable energy to secure the future of people and the planet
3
|

EN_PPT008V00_M&A
Definitions

5. Will we define an approval flow to approve the information that will be published Identification »»
Classification »» Validation »» Dissemination
6. Integration with teams?

Generating renewable energy to secure the future of people and the planet
4
|

EN_PPT008V00_M&A
Macro Plan
2. Plan

•Define internally if PMO is able to build the Knowledge base by themselves


•Close mandatory requirements to launch MVP and build a release roadmap with wishes features
•Define a POC so as to allow PMO to make a trial
•Trial Evaluation and Knowledge base adjusts
•Build a schedule
•Present to the heads
•UAT
•Go live

Generating renewable energy to secure the future of people and the planet
5
|

EN_PPT008V00_M&A

You might also like