
Sign up to save your podcasts
Or


Open, restricted, negotiated, competitive dialogue and the other procedures: which one for which purchase. The three value bands below the thresholds, the minimum number of candidates, and the narrow cases where a contract can be negotiated without publication.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
How PM² frames outsourcing, and which rules the EU institutions follow when they buy: the Financial Regulation, not the procurement directive. Principles, the ban on splitting contracts, lots, mixed contracts and the key vocabulary.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
The engineering practices a project manager must recognise: life cycle models, architecture artefacts, continuous integration, version control and code review. Technical debt, open source licences and what DevOps really means.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
From project to operations: the Transition Plan, provisional acceptance and the transfer of ownership in PM². Release versus deployment, go-live strategies, rollback, data migration with reconciliation, early life support and handover.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
How testing is organised and how a go or no-go is decided: the test process, severity versus priority, entry and exit criteria that must all be met. Test data and personal data, performance, security and accessibility testing.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
The testing vocabulary a project manager needs: error, defect and failure, verification and validation, the seven principles, the five test levels and the forms of acceptance testing. Confirmation versus regression testing, test techniques, and testing in agile teams.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
Who accepts a deliverable, against which criteria, and what happens when defects remain. The Deliverables Acceptance Plan and conditional acceptance in PM², then the Scrum Increment, the Definition of Done and how it differs from acceptance criteria.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
Quality is planned and built in, not tested in at the end. Quality assurance versus quality control, the Quality Management Plan, checklists and review reports in PM², with the three responsibility lines that are easy to mix up.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
A change request is not a change: how requests are assessed, decided and traced in PM², and who approves what. Then configuration management, which keeps track of versions, and how change is handled in programmes, portfolios and agile teams.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
What to do when something has already gone wrong: the Issue Log, the Decision Log and the difference between a decision and a change. When to escalate, to whom and how, and when escalating is the wrong answer.
Hosted on Ausha. See ausha.co/privacy-policy for more information.
From the publisher's feed