
Sign up to save your podcasts
Or


The seventeen tools of the PM² toolbox in five families, with PESTEL, make or buy and Pareto explained in full. Breakdown structures, three-point estimates, critical path and critical chain, decision trees, and where each tool is used.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
A reading of the official PM² forms: risk scales and suggested responses, the escalation model, the lifecycle of a requirement, the change request form and the status report. What is a default to customise and what is a rule of the method.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
The three levels of the PM² family side by side: what each is for, its lifecycle or processes, how it ends and who decides. The words that change meaning from one level to the next, such as phase and stage.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
The governance of a PM² project in one picture: five layers, two sides, six roles facing each other. Who is responsible and who is accountable for each artefact, and the few exceptions to the usual pair.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
One project followed from the first idea to the archive, in PM² only: four phases, three gates, the driver of each phase and the artefacts each one produces. Where Monitor and Control fits, and what really ends a project.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
Authentication and authorisation, keys and certificates, encryption in transit and at rest, zero trust. Then a map of the Union's digital legislation: electronic identity, the AI Act, the Data Act, platform rules, product cybersecurity and the once-only principle.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
The vocabulary of the people who run a system after the project: the service value system and the practices a project meets. Incident and problem, the three types of change, service level agreements, release and deployment.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
Cloud service models and the shared responsibility between provider and customer. Availability turned into hours of downtime, chains and redundancy, recovery time and recovery point objectives, business continuity and disaster recovery.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
Relational and NoSQL databases in plain words, master data and data quality, and who decides what about data. How a data migration is prepared, rehearsed and reconciled, and why a backup is not an archive.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
From the publisher's feed