Short, applied courses with a verifiable certificate. Search for a topic, or narrow by category, level, duration and price.
Learn to run sessions that produce genuine group decisions instead of a stack of individual opinions. You will master the facilitator's neutral role, a divergent-then-convergent structure that fits most workshops, and a reusable session-design template you can apply to any IT meeting.
Learn to validate product ideas with small, fast experiments before committing to full-scale build-out. Understand the trade-off between an experiment's speed and cost and the strength of the evidence it produces, and how to pick the right test for the size of the bet.
Master the backlog hierarchy — Epics, Features, Stories and Tasks — and how each level serves a different planning horizon and audience. Learn to trace a single Epic down to Tasks and back up so progress rolls up honestly, and avoid the over-deep hierarchies and mislabelled items that break the trace.
Learn why dependency visibility gets harder, not easier, as the number of coordinating teams grows — and how a portfolio-level dependency tracker succeeds where a pile of team RAID logs fails. Build a single shared tracker that surfaces cross-team conflicts before they become blocked sprints.
Turn the Sprint Review from a polite one-way demo into a working session where stakeholders inspect the real Increment and shape what gets built next. Learn to invite backlog-changing feedback and build a facilitation guide that makes it stick.
Understand what DevOps actually is — a culture of shared responsibility between development and operations — and why it is defined by how people work together, not by the tools they buy. Learn to explain DevOps to a non-technical sponsor in plain English and reframe it from a shopping list into a workflow and culture change.
Understand who the Developers really are in a Scrum Team, what they are accountable for, and how self-management turns a group of specialists into a team that owns its plan. Learn to run Sprint Planning so the Developers, not a manager, drive the work.
Learn to spot the "Four Horsemen" of damaging interaction — criticism, contempt, defensiveness and stonewalling — as they appear in technical teams, and understand why contempt in particular predicts breakdown. Practise naming a Horseman in the moment without escalating, and build a reference card that keeps your team honest.
Turn the Daily Scrum from a status meeting into a 15-minute planning event the Developers actually own. Learn the Scrum Guide 2020 purpose, replace the rote three questions with a Sprint-Goal focus or a board-walk, and redesign a broken daily around a reusable canvas.
Learn to measure how work really flows through your team using the three core flow metrics — lead time, cycle time and throughput. Pull the numbers from your existing tracking tool, read them honestly, and use them to expose delays that velocity and story points hide.
Learn what a Product Goal really is in the 2020 Scrum Guide — the single long-term objective that sits above Sprint Goals and gives the Product Backlog a target to emerge against. Master a practical structure for writing goals that are outcome-based, time-bound and measurable, and learn to spot and fix the fake goals that are really just roadmaps in disguise.
Learn what a product vision really is — the long-term reason your product exists — and why it is distinct from a roadmap or a backlog. Build a clear vision statement and a one-page Product Vision Board that refocuses every prioritisation debate on why the product exists in the first place.
