Talk:Personal Knowledge Container
Daily reporting
The Purpose of these reporting is to check on daily progress until PKC PMO defines how to report its data.
It's also for some items to be better defined and/or validated
Report 13th April 2022
Summary:
- Information update about PKC and its portfolios
- Started to set up PMO definition and structure
- Updated W3T3 budget (error on Gdocs solved)
- List of points to be defined (pending issues)
Information update about PKC and its portfolios
Definition update about PKC: PKC is not a project is an Idea (a project has closure and PKC is eternal).
PKC content must be pattern and re-organize all volatile information, requiring an editing comprehension to make it more user friendly and people accessible This also intents to prevent continuous re-editing on the same context, using a “branching process” instead.
PKC is composed by the following portfolios: Meta University; Inter-Organizational Workflow; PKC Engine; PKC Spin-off
PKC is managed by a state-of-the-art PMO (PKC PMO) based on a Disciplined Agile approach (PMI)
PKC first project is W3T3
Started to set up PMO definition and structure
Create the page with PKC PMO namespace and it will define all the Knowledge Areas there (According to PMI): (not completed yet)
- Integration
- Scope
- Schedule (time)
- Cost (Budget)
- Quality
- Resources (HR/Materials/Team)
- Communications
- Risk Management
- Procurement
- Stakeholder
PKC PMO will also use Track on performance platformduring 2022 in order to learn how to operate under time management but also to understand how can it take advantage from technologies such as Apollo and APIs/BackEnd communication into third party platforms
Updated W3T3 budget
(Still Missing the discretionary budget, it's on construction just like P&L, with payments/Install per month)
List of points to be defined
Question 1:
- Technologies to be used on PKC:
- (Currently is basically PHP however to become more state of the art as a web app) are we going to work on:
- React framework
- Typescript
- Nest instead of PHP
- others, to be define...
- Objective is HR:
- Define the technologies to define your team
Question 2:
- (Mentioned before) I can allocate 1 person from my team, she is very good in React, understands well Apollo and designed many of the components in documentation/portfolio
- Engaging developers take time, if they are not aware of technology 100% they can take longer
Question 3:
- A template sample was implemented for possible contract agreement types in a new PKC templates page but instead of NDA, I wrote the fact that we are an OSS community therefore everything we do we are transparent and also because people are responsible for their own actions, therefore we don't need NDAs.
- Just confirm if you agree on the principle
Question 4:
- Define a temporary organization body:
- What is the name of the organization
- (even if it's a temp organization)
- VAT number
- (VAT numbers are necessary for financing/Billing and invoice purposes. We can't buy or pay anything without VAT number)
- Who will pay suppliers, salaries and costs
- (who issues the bank transfer is important so that it should be noted as part of a recurrent action every month or previously/after events)
- (Ben can be the releaser of the transfers, but not necessary the operational of making them, normally it's done by a financier like head of accounting or CTO that has access to companies account but can't make anything without the president or CEO or head of the organization approval)
- How to manage receipts of payments/installs
- (Before having the accounting system, in the beginning might be possible to handle with some software simpler, it depends on the country)
- (In USA it's not necessary a professional, in Portugal you have to hire a professional even for selling online used stuff)
- Contact responsible person
- (the main person accountable of that organization body, in companies it's the partners or CEO; in ONGs it's the president or similar)
- Email responsible person
- (same as previous)