
In this lecture you build the Agile Reality Ladder, mark the level your own team works at, and write the single move up from it.
This course is built from six disciplines: agile delivery, product leadership, business analysis, facilitation, goal cycles and working with leadership.
The map of the course
A dictionary for reading lectures from other fields as delivery work
Three questions to ask after every lecture
A short self-diagnostic that shows which sections to watch first
Download the Agile Reality Ladder and fill in one line after each lecture.
Tools in this lecture
Files to download (1)
What Agile is: the basics and the artefacts
How it differs from the classical plan-driven approach
Where it applies and where it does not
What counts as a product, the product owner role, and working with an internal customer
Tools in this lecture
Ready to use on the slides (1)
Services and apps shown in this lecture (1)
Models and methods explained (4)
Product vision
The prototype and the minimum viable product
Customer needs and product features
Building the roadmap
Tools in this lecture
Ready to use on the slides (9)
Models and methods explained (6)
Creating a Kanban board and using a board tool to automate it
Filling the backlog
Backlog prioritisation
Sprint planning and story points
Tools in this lecture
Ready to use on the slides (7)
Services and apps shown in this lecture (1)
Models and methods explained (4)
How often to release, and what that choice costs
The launch plan
Very large-scale launches
Tools in this lecture
Ready to use on the slides (9)
Models and methods explained (7)
The daily meeting and what it is actually for
Reviewing sprint results
The sprint meetings and how they connect
Tools in this lecture
Ready to use on the slides (4)
Models and methods explained (5)
Applying it to hiring work
Applying it to training and development
Applying it to rewards and talent work
Applying it to automation projects
Tools in this lecture
Ready to use on the slides (2)
Models and methods explained (2)
Evolution of the role from product manager to product leader
How it differs from technology, marketing and chief executive roles
The product leader as the voice of the customer inside the company
Balancing business, users and technology
Tools in this lecture
Ready to use on the slides (1)
Models and methods explained (3)
Product vision and mission
Finding product-market fit and sustaining it
Strategic priorities and product goals
Linking product strategy to business goals
Tools in this lecture
Ready to use on the slides (21)
Models and methods explained (4)
The product life cycle
Portfolio matrices and other approaches
Decisions to invest, maintain or retire
Balancing core, adjacent and innovation bets
Tools in this lecture
Ready to use on the slides (13)
Models and methods explained (2)
Methods for researching the market and customer needs
Jobs to be done and design thinking
Customer journey mapping
Tools for validating hypotheses before anything enters the backlog
Tools in this lecture
Ready to use on the slides (11)
Models and methods explained (15)
Roles: product managers, designers, analysts, researchers
Building the organisation with tribes and squads
Agile and lean as the operating model rather than a ritual
A culture of experimentation and learning
Tools in this lecture
Ready to use on the slides (12)
Models and methods explained (6)
The north star metric and its supporting metrics
The pirate metrics framework
Product analytics platforms
Data-driven decisions inside the delivery cycle
Tools in this lecture
Ready to use on the slides (9)
Models and methods explained (3)
Monetisation models: freemium, subscription, transactions, licences
Growth loops and product-led growth
Unit economics and the lifetime value to acquisition cost ratio
Financial accountability for what the team ships
Tools in this lecture
Ready to use on the slides (4)
Models and methods explained (10)
The product as the company scales
Supporting global expansion
Managing technology and market risks
Embedding security and compliance into the delivery process
Tools in this lecture
Ready to use on the slides (9)
Models and methods explained (2)
The product leader as a driver of digital transformation
Innovation: artificial intelligence and platform business models
Building partner ecosystems and open innovation
Where the role is heading
Tools in this lecture
Ready to use on the slides (1)
Models and methods explained (1)
The analyst as a translator of business value into solutions
Problem thinking versus solution thinking
Telling a symptom from a problem
The problem, goal, constraint and metric framework
Tools in this lecture
Ready to use on the slides (11)
Models and methods explained (6)
Stakeholder mapping and influence analysis
Elicitation techniques
Asking the business the right questions
Handling conflicting requirements, and prioritising value against effort
Tools in this lecture
Files to download (4)
Ready to use on the slides (17)
Models and methods explained (2)
Types of requirement: business, functional, non-functional
User stories: structure, examples and anti-patterns
Acceptance criteria in given-when-then form
Requirements documents that get used, and a definition of ready
Tools in this lecture
Files to download (3)
Ready to use on the slides (15)
Models and methods explained (4)
What a business process means for an analyst
The as-is and to-be approach
The minimum necessary set of notation
Finding bottlenecks and waste, and proposing improvements rather than diagrams
Tools in this lecture
Files to download (3)
Ready to use on the slides (10)
Models and methods explained (2)
The system context diagram and functional decomposition
User flows and scenarios
Data objects and business rules
Non-functional requirements and traceability from requirement to solution
Tools in this lecture
Files to download (3)
Ready to use on the slides (12)
Models and methods explained (1)
The analyst's role in Agile, Scrum and plan-driven projects
Working with the backlog and with changing requirements
Change requests and impact analysis
Managing scope and expectations, and defending requirements to both sides
Tools in this lecture
Files to download (3)
Ready to use on the slides (13)
Models and methods explained (8)
How facilitation relates to decision-making
The basic principles
The role of the facilitator and what it is used for
The single most important facilitator skill
Tools in this lecture
Ready to use on the slides (9)
Models and methods explained (1)
The main preparation stages
Formulating the goal of the session
Selecting participants
How to open a session so it does not drift
Tools in this lecture
Ready to use on the slides (15)
Models and methods explained (1)
Keeping participants focused
Managing the group and taking notes at the same time
Gathering information and generating ideas
Choosing priorities out of what was generated
Tools in this lecture
Ready to use on the slides (23)
Summing up so the result survives the room
Assigning owners for the actions
Evaluating the session itself
Dealing with difficult participants and unexpected turns
Tools in this lecture
Ready to use on the slides (28)
How the group makes a decision
How to maintain the atmosphere while pushing for one
Exercises that move a stuck group
Tools in this lecture
Ready to use on the slides (9)
Models and methods explained (2)
Building the agenda and estimating timing
Facilitating online
Facilitating large meetings
Working with an international team across time zones
Tools in this lecture
Ready to use on the slides (15)
This course contains the use of artificial intelligence.
Many teams adopt the rituals of agile, stand-ups, sprints and boards, and keep making decisions the old way. Here are 510 tools to make agile work: 369 ready-to-use procedures, templates, question lists, checklists, matrices and AI prompts, 111 models and methods, 13 services shown on screen and 17 working files.
Open a lecture, take the tool, run your next sprint planning with it.
Why agile turns into rituals
The board is full and nobody knows what matters most. Stories are too big to estimate, ceremonies end without decisions, and requirements change quietly mid-sprint. Goals live in a separate document, so saying "not this quarter" feels like refusing work.
What changes after this course
The backlog is prioritised by value, stories have acceptance criteria, ceremonies end in decisions and changes go through impact analysis. An OKR cycle above the sprints makes priorities explicit, and you lead and influence stakeholders without formal authority.
A note on the structure
The core method lessons were recorded for teams running internal projects, so the cases are hiring, training and reward projects rather than software features. The mechanics are the same: board, backlog, prioritisation, sprint, story points, daily meeting and review.
What is inside: 510 tools, counted lecture by lecture
You do not have to take this number on trust. Open any lecture and read its description: every tool inside is listed there by name.
Where the tools are
Agile and Scrum foundations (2 sections, 62 tools). Product owner, Kanban, backlog, release planning, stand-ups and reviews.
Agile product strategy (3 sections, 125 tools). Vision, product-market fit, discovery, jobs to be done, metrics and growth.
Agile business analysis (2 sections, 116 tools). Problems, user stories, acceptance, BPMN and requirement change.
Ceremony facilitation (2 sections, 103 tools). Decision sessions, alignment and difficult participants.
OKR for agile teams (3 sections, 56 tools). Goal cycles, check-ins, retrospectives and tools.
Leadership and influence (2 sections, 62 tools). Focus, priorities, briefs, trust and influence without authority.
Who is teaching
I am Mike, the #1 HR instructor on Udemy, with 1,800,000+ course enrollments from 170,000 students, and the author of about 200 books on Amazon. I built the people system at Preply as it became a unicorn and worked at Wargaming, iDeals and Alfa-Bank across 20 years in HR. I hold PHRi, SHRM-CP and HCI sHRBP certifications and represent HRCI in Eastern Europe.
At Preply I ran Delegation Poker with managers myself: we printed the free cards, each manager drew a delegation level for real situations, and the discussion about why people chose different levels was the point. At iDeals our first OKR cycles reached only 30 to 50 percent, because leaders spent about 30 percent of their time on goals and the rest on daily work; I had not explained that this is normal at first.
How to use the course
Start with the Agile Reality Ladder and the foundations, then go to product, analysis, facilitation or OKR sections as your team needs them. Section and lecture titles show how many tools are inside, and each lecture description lists them by name.
What is included
Where to start
Take your current backlog and mark the five items you would cut if the team lost a third of its capacity. Enrol now and start your first lesson today.