Short, applied courses with a verifiable certificate. Search for a topic, or narrow by category, level, duration and price.
Learn how the core constraints of any IT project — scope, schedule, cost and quality — are locked together, so that changing one always forces a change in another. Build the judgement to expose impossible asks, negotiate honest trade-offs, and steer delivery with a simple constraints triangle.
Learn what IT governance really is — risk management and decision rights — and why heavy stage-gate sign-off destroys the agility it is meant to protect. Redesign oversight as lightweight checkpoints aligned to natural Agile cadences, and build a governance checkpoint template your organisation will actually use.
Learn to find, visualise and actively manage the cross-team and cross-system dependencies that quietly sink IT delivery. Build a dependency map at planning time so hidden hand-offs surface as decisions, not as missed dates.
Learn why one stage in a workflow usually governs a whole team's delivery speed, and how to find it. You will read cumulative flow diagrams for the widening bands that betray a growing bottleneck, diagnose a slowed IT workflow, and build a reusable reading guide your team can trust.
Learn to treat product initiatives as testable hypotheses rather than guaranteed features, using a simple structure that makes your assumptions and success signals explicit. You will practise turning vague backlog items into falsifiable hypotheses and designing the smallest experiment that could prove you wrong.
Learn why the initiation phase is where an IT project is really won or lost, and how a lightweight project charter turns vague ambition into shared, testable agreement. Master the practical skill of aligning sponsor and delivery on purpose, scope and success before the first line of code is written.
Failing IT projects rarely recover by working harder on the same plan. Learn a structured recovery sequence — confirm viability, reset expectations, redefine done, fix the backlog and control work in progress — and why the order matters more than any single fix.
Learn why vague, personality-based feedback fails and how specific, behaviour-based feedback changes what people actually do. Master the Situation-Behaviour-Impact (SBI) model to give feedback that lands, and learn to receive feedback without becoming defensive.
Understand what generative AI really is — large language models that predict text one token at a time — without needing a data science background. Learn how tokens, context windows and hallucinations shape what these tools can and cannot do, and how a well-structured prompt turns a disappointing experiment into genuine capability.
Learn to tell functional requirements — what a system does — apart from non-functional requirements — how well it does it — and why the second kind is the one teams forget. You will work through the categories that get omitted, build a reusable checklist, and diagnose a real system that passed every test and still fell over.
Learn why funding and organising IT work as temporary projects quietly damages the long-lived systems those projects create, and what changes when you treat software as a persistent product instead. Build the reframing skill — and a one-page canvas — that turns a project mindset into a product mindset for a real initiative.
Learn to answer the manager's real question — "are we improving?" — using system-level flow metrics rather than activity or output numbers. Build a flow dashboard that tracks cycle time, throughput and WIP as trends, and avoid the trap of turning flow data into individual surveillance.
