Difference between revisions of "PKC PMO"

From PKC
Jump to navigation Jump to search
Line 48: Line 48:
===How to build a project process===
===How to build a project process===


Projects scope must be described on PKC on the following structure ([[PKC templates |/PKC Project page structure]]):
Projects scope must be described on PKC on the following structure ([[/PKC Project page structure/]]):


* Intro (no title)
* Intro (no title)

Revision as of 22:45, 21 April 2022

Integration Plan

Intro

PKC is a high complex platform with multiple purposes which requires to define clearly each branch and be able to build new ones. Integration management plan needs to create a structure for this connections between divisions and branches.

All portfolios, programs and projects will be recorded in a whole platform. 2022 it will be use Trackonperformance.com (TOP) 2023 it will use a "white label" structure to create its own independency

PKC will be managed project-oriented through PKC PMO and Project management will adopt hybrid life cycles:

  1. predicted in yearly plans or long term projects (such as education)
  2. adaptive in research projects with no date to finished, just apply time management
  3. Iterative incremental (known as Agile) during development projects, or short project cycles/iterations from main projects in order to provide faster control
  4. Iterative in lining projects such as industry or education recurrent activities

W3T3 will use a combine cycle of prediction with Agile since there is a milestone date such as G20 that can't fail, and at same time there is several steps of development to take care where short iterations will be done using AGILE methodology.


PKC PMO responsibilities will make sure that:

  1. the projects initiate with the proper plan, with estimations, milestones, allocations and budget approved, but also with the proper technical documentation register, concluding visual support
  2. the projects will be finished on time, with the proper quality defined and with the proper documentation of all learning experiences in order to avoid redundancy
  3. can prevent any project collapse in time and solve it, either with fast tracking or crashing, having always management reserves or the cause.


Allocations

PKC resources will be composed by:

  1. Development team (Dev)
  2. PMO team (PMO)
  3. Education team (Edu)
  4. Marketing/PR/Social media (if necessary) (MKT)
  5. Invited guests (Guests)

Teams will be composed from different countries and different skills

Facilities

Most of the work will be virtual, however, it is planned to exit 4 facilities in Indonesia: Bali (head), Jakarta, and

The Facilities will be essential for the education development

Time management

All tasks will be recorded according to estimated time and Real time TOP will be the instrument to record that data, essential to control requirements of compliance

How to build a project process

Projects scope must be described on PKC on the following structure (/PKC Project page structure/):

  • Intro (no title)
  • History factors (in case it needed or if exists)
  • Logic Model (Purpose, Problem-solving or how project differ from others, success criteria; inputs, process, Outputs) There is a template for the logic model in here.
  • Define project needs (resources, time, costs)
  • Define context (if needed e.g. education - What, How, why, etc... of curriculum or programs)
  • Quality issues or boundary conditions
  • Stakeholders identification
  • Budget
  • References
  • Related pages




SCOPE

PKC PMO is the managing structure of PKC, based on a state-of-the-art project management approach called Disciplined Agile [[[DA]])

PKC PMO operates all the environment and events management using PKC engine and using the concept of Ouroboros (or, producing what it's build by its own) to produce its products and projects.

PKC PMO is also open-source based which means that all the process of data governance and reporting is explicit demonstrated and register in PKC



Schedule (time) Management

Cost (Budget) Management

Quality Plan

Resources (HR/Materials/Team) Management

Team composition/ HR

For 2022 and W3T3:

  1. Project Leader/Owner = Ben Koo
  2. Project/PMO Director = Pedro Faria
  3. Special guests = Jacob AppelBaum; Brendan Novak; Alex Pentland?; ...
  4. Cyber security architect =
  5. Cyber security white hat =
  6. UXUI experts =
  7. FullStack Developer I =
  8. FullStack Developer II =
  9. DevOps Admin =
  10. PMO assistant =
  11. Office assistant (Bali) (maybe not necessary) =
  12. Office assistant (Jakarta) (maybe not necessary) =
  13. Project Leader assistant (task manager) =
  14. Accountability =
  15. Admin and legal issues =
  16. PR assistant =
  17. Content media =
  18. Community manager =


Materials and Services Trips and hospitality Hardware Cloud Services



Communication plan

Principles:

  1. Everybody is self accountable therefore it is expected to know their job avoiding unnecessary redundancy
  2. Everyone is self accountable on planning and reporting daily operations for quality control


Risk Management

Procurement

Structure of PKC PMO is managed by...


Contract template can be found here


Stakeholder Registers