
Sign up to save your podcasts
Or


How a schedule is really built: dependencies, the critical path, total and free float, all worked out on one small network. Then how to shorten it, by crashing or fast-tracking, and what each one costs.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
Breaking down the work, estimating it and scheduling it, in that order. Work breakdown structures, four estimation techniques with the three-point formula, and the difference between an estimate and a commitment.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
The start of the Planning phase: an official kick-off meeting, then the Project Handbook, the document that says how this project will be managed. The six management plans, the project-specific plans, and how to tailor without cutting out.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
What really happens when a project ends: the review meeting, lessons learned, post-project recommendations, the Project-End Report and administrative closure. Why a programme closes on benefits rather than deliverables.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
How an organisation chooses which programmes and projects to fund: identify, evaluate, plan capacity, prioritise, approve. Selection criteria, weighted scoring, capacity limits, and who actually decides.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
A project delivers outputs; the benefits come later, when people work differently. Who prepares the Business Implementation Plan, how it differs from the Transition Plan, and how programmes and portfolios track benefits with owners, metrics and a benefit log.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
How projects are compared in a business case: payback period, return on investment, net present value and internal rate of return, each computed step by step on simple numbers. What each measure cannot see, and why money already spent never counts.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
The first phase of a PM² project, from the idea to the first gate: the Project Initiation Request, the Business Case and the Project Charter. What each document answers, who writes and who approves it, and what to do when someone wants to skip a step.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
Governance versus management, with COBIT and TOGAF in one line each. Then the security roles of Commission Decision 2017/46: the two boards, the head of department, the system owner, the data owner and the local security officer.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
The people of the two upper levels: programme owner, programme business manager and programme manager, then the portfolio directing group, steering committee, manager and support office. Who chairs, who appoints, who proposes and who approves at each level.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
From the publisher's feed