
Sign up to save your podcasts
Or


The response strategies for threats and opportunities, and why transferring a risk never transfers accountability. Acceptance, contingency plans and reserves, residual and secondary risks, and how risk is handled in programmes, portfolios and agile teams.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
Risk, threat, opportunity and issue: the vocabulary that scenario questions test. The PM² risk process, the Risk Log, likelihood, impact and risk level, then expected monetary value and decision trees, computed step by step.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
How information is planned and how a group becomes a team. The Communications Management Plan, push, pull and interactive communication, the channels formula, self-organising agile teams, stages of team development, leadership styles and conflict handling.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
Who counts as a stakeholder, how they are identified and analysed, and why one analysis during planning is never enough. The Project Stakeholder Matrix, the power and interest grid, levels of engagement, and the programme and portfolio matrices.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
What a project manager actually does while the team builds: the Executing Kick-off Meeting, project coordination and information distribution in PM². Then the agile rhythm: PM²-Agile ceremonies and the five Scrum events with their timeboxes.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
What a project manager monitors, and which report goes to whom: status, progress, contractor and development reports, then programme and portfolio reporting. Leading and lagging indicators, and how to avoid the all-green report.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
Three numbers that tell whether a project is late and over budget: planned value, earned value and actual cost. Variances, indices and forecasts at completion, computed step by step, with the limits of the method.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
From estimates to a cost baseline and a budget, with the two reserves that are so often confused. The cost of quality, and how cost is controlled and overruns approved in a PM² project.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
Story points, velocity and burndown charts explained with simple calculations, and why velocity is neither a target nor a way to compare teams. How agile projects plan releases and iterations, and use scope as their contingency.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
What a requirement is, how requirements are gathered, prioritised, traced and validated, and why they should state a need rather than a solution. The agile side: features, stories, the backlog, and the difference between ready and done.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
From the publisher's feed