Udemy
Turn what you know into an opportunity and reach millions around the world.
Learn More
Your cart is empty.
Keep shopping
Requirements Engineering: User Stories, BPMN, 380+ Tools
Rating: 4.3 out of 5(2 ratings)
481 students

Requirements Engineering: User Stories, BPMN, 380+ Tools

Elicit, write and validate requirements: user stories, acceptance criteria, BPMN, BRD, workshops, surveys, AI prompts
Last updated 10/2026
English
English [Auto],

What you'll learn

  • Take away 380+ tools: procedures, question lists, templates, checklists, matrices and AI prompts, plus 21 downloadable tool files
  • Frame the request with a business problem statement, root problem diagnostic questions and a value discovery interview
  • Elicit requirements with a stakeholder register, an elicitation technique selection matrix and an interview procedure
  • Write requirements with a User Story template, an INVEST checklist, Given-When-Then acceptance criteria and BRD, SRS and PRD templates
  • Model a process with AS-IS and TO-BE process analysis, bottleneck identification questions and a process improvement proposal template
  • Run a requirements workshop with a preparation checklist, brainstorming, dot voting, affinity grouping and an action log
  • Collect input in writing with a survey design checklist, rating scales, a survey length checklist and report samples
  • Handle change with Definition of Ready and Definition of Done checklists, a change request form and stakeholder refusal scripts
  • Use 18 ready AI prompts: User Story generation, acceptance criteria generation, requirements conflict analysis, change request impact analysis
  • Learn with Mike, the #1 HR instructor on Udemy: 1,800,000+ enrollments, 170,000 students, about 200 books on Amazon

Course content

13 sections • 36 lectures • 18h 20m total length
  • Test a Vague Request: Behind the Request Card13:55

    In this lecture you work on the moment every requirement starts from: somebody has just told you what they want, and you have three answers available.

    1. This course is built from six disciplines: business analysis, interviewing, facilitation, surveys, process management and critical thinking.

    2. The map of the course

    3. A dictionary for reading lectures written about recruitment and engagement surveys as your own requirements work

    4. Three questions to ask after every lecture

    5. A short self-diagnostic that shows which sections to watch first

    6. Download the Behind the Request Card and fill it in before your next conversation.

    Tools in this lecture

    Files to download (1)

    • Behind the Request Card

Requirements

  • No formal business analysis background required: BPMN, user stories and acceptance criteria start from zero
  • A project or product where somebody has to decide what gets built
  • A spreadsheet program such as Excel or Google Sheets for the tool files
  • Nothing else to buy for the course itself: 21 tool files and the presentations are attached to the lectures

Description

This course contains the use of artificial intelligence.

386 tools for requirements engineering in one course: 275 ready-to-use procedures, question lists, templates, checklists, matrices and AI prompts, 82 models and methods, 21 downloadable tool files, and 8 services and apps shown on screen.

Open a lecture, take the tool, use it on a real requirement.

Why specifications fall apart

Nobody can tell you what they want. They can tell you what they do now, what annoys them about it, and what they saw somewhere else and liked. The requirement gets written down exactly as it was said, so it records a proposed solution and not the problem behind it. The acceptance criteria say "the system should be user-friendly", which cannot be tested. Two stakeholders want opposite things and both wishes are recorded, so the conflict moves to delivery.

What changes after this course

You start from the business problem and its metric. You get requirements in three ways, because each one brings different information: one to one in an interview, in a group at a workshop, and in writing through a survey. You write them as user stories with acceptance criteria that a developer can build from. You draw the process as it is and as it should be, and the gap between them becomes the requirement set. You check a requirement for logic and evidence before the team spends time on it.

What is inside: 386 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.

  • 275 ready-to-use tools inside the presentations:
  • 83 step-by-step procedures and workflows: requirements elicitation interview procedure, requirements workshop procedure, requirements conflict resolution procedure, change request impact analysis
  • 55 question lists and scripts: root problem diagnostic questions, value discovery interview, bottleneck identification questions, stakeholder refusal scripts
  • 51 templates and sample documents: User Story template, Use Case template, BRD template, Change Request Form
  • 36 checklists: INVEST checklist, acceptance criteria quality checklist, Definition of Ready checklist, non-functional requirements checklist
  • 19 scorecards, rubrics and matrices: power-interest grid, elicitation technique selection matrix, Requirements Traceability Matrix, risk probability-impact matrix
  • 18 ready AI prompts: User Story generation prompt, acceptance criteria generation prompt, AS-IS process description prompt, change request impact analysis prompt
  • 7 formulas and metric sets: requirements documentation quality metrics, process efficiency metrics, business analyst performance metrics
  • 6 other working tools: MoSCoW prioritization, value-added activity classification, Cynefin framework
  • 82 models and methods explained with examples: BABOK, BPMN, FURPS+, Working Backwards, Business Model Canvas, Scrum, Kanban, Minimum Viable Product
  • 21 downloadable tool files: requirements elicitation tracker, stakeholder register, requirements traceability matrix, user stories and acceptance criteria template, AS-IS TO-BE process analysis, change request impact analysis, survey report samples and others
  • 8 services and apps shown on screen, from a quick look to a detailed demo: Google Forms, Simple Poll, PeopleForce, 15Five, CliftonStrengths, Microsoft PowerPoint and others

Where the tools are

  • From business problem to documented requirement, processes and change (2 sections, 116 tools). Problem statement, stakeholders, elicitation, user stories, acceptance criteria, BRD, AS-IS and TO-BE, systems thinking, backlog and change requests. Sixteen of the tool files are here.
  • Eliciting one to one (2 sections, 48 tools). Interview structure, STAR questions, competency maps, assessing and documenting answers. The examples in these sections come from hiring interviews.
  • Eliciting from a group (2 sections, 103 tools). Preparing and running a workshop, generating ideas, reaching agreement, closing with owners, online and large sessions.
  • Eliciting in writing (2 sections, 42 tools). Survey types, question wording, scales, launch, report and action plan. The examples are employee surveys.
  • Modelling the process (2 sections, 41 tools). Methodology, BPMN, process description as a project. The examples are HR processes.
  • Validating requirements (2 sections, 40 tools). Logic, evidence, cognitive bias, sources and decisions under uncertainty.

What this course is not

It is not a certification programme such as CPRE, CBAP or ECBA. You receive the Udemy Certificate of Completion and a working toolkit.

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.

I have been on both sides of this work. At the STB TV channel I described and improved recruiting and onboarding myself. When personnel administration needed the same, a business optimization manager was brought in. She started by coming to the department, sitting next to an employee and watching a typical working day from start to finish. She saw a person standing in a queue, a form filled in by hand though the law did not require it, and we removed these steps one by one. I also saw what a written process gives. New recruiters read the described process and took vacancies into work on the third day. More time went to development and less to putting out fires.

How to use the course

Start with the first lecture and its card: it takes one vague request and turns it into something you can test. Watch the next two sections in order: they follow a requirement from the problem to the change request, and the lectures have files to fill in. Then open the way of eliciting you need now: interview, workshop or survey. Section and lecture titles show how many tools are inside, and each lecture description lists them by name.

What is included

  • 36 lectures across 13 sections, 18.5 hours
  • 55 downloadable resources: 21 tool files and the lecture presentations
  • 386 tools across the lessons, ready to copy into your own work
  • Lifetime access to all materials
  • Active instructor support in the Q&A section
  • A Udemy Certificate of Completion

Where to start

Take one request you received this week. Open the first lecture and rewrite the request as a business problem statement: what is the problem, what is the goal and how you will measure it. Enrol now and start your first lesson today.

Who this course is for:

  • Business analysts moving from documenting requests to eliciting requirements
  • Product managers and product owners whose specifications come back as questions
  • Project managers who inherited the analyst role along with everything else
  • Developers and technical leads who want clear requirements before they build
  • Consultants gathering requirements inside organisations they have just entered
  • Domain experts asked to describe how their own work should be automated