Business Analyst
Process modelling (BPMN) questions
116 questions on Process modelling (BPMN) for business analysts, easiest first.
Easy 35
- Why map the as-is processeasy
- Finding the root causeeasy
- Actors in use case diagramseasy
- BPMN event shapeeasy
- Lanes in BPMNeasy
- What SIPOC stands foreasy
- Using a fishbone diagrameasy
- Why swimlane diagramseasy
- The shape of a BPMN taskeasy
- The X gatewayeasy
- Start and end eventseasy
- The solid arrow in BPMNeasy
- Showing a document in BPMNeasy
- The plus sign on an activityeasy
- What a pool representseasy
- The double circleeasy
- A clock inside an eventeasy
- The envelope iconeasy
- User task vs service taskeasy
- Who maintains BPMNeasy
- What a to-be model iseasy
- Value-added or noteasy
- The wastes of Leaneasy
- The DMAIC cycleeasy
- UML's process diagrameasy
- Why model in levelseasy
- End-to-end lead timeeasy
- What kaizen meanseasy
- Process or procedureeasy
- Labelling an exclusive gatewayeasy
- The box in a use case diagrameasy
- Checking a draft process mapeasy
- Turning a model into a procedureeasy
- A task done with no systemeasy
- Going to see the workeasy
Medium 46
- Gap analysismedium
- Reading a BPMN diagrammedium
- The BPMN parallel gatewaymedium
- Choosing an inclusive gatewaymedium
- Communicating between poolsmedium
- Escalating a slow approvalmedium
- Which UML diagram for messagesmedium
- Modelling a status lifecyclemedium
- Include vs extendmedium
- Process cycle efficiencymedium
- Capacity of a team stepmedium
- Modelling reworkmedium
- Handling a failed paymentmedium
- A reminder that does not stop the taskmedium
- An event sub-processmedium
- Reusing a processmedium
- Three lines on an activitymedium
- The loop markermedium
- Separating rules from the flowmedium
- Tokens after a parallel splitmedium
- Starting when a message arrivesmedium
- Stopping all paths at oncemedium
- Data store or data objectmedium
- A pool with nothing insidemedium
- Calculating takt timemedium
- How busy is the countermedium
- Data needed for process miningmedium
- A good candidate for RPAmedium
- Straight-through processing ratemedium
- The slash on a sequence flowmedium
- The line of visibilitymedium
- Thick bars in an activity diagrammedium
- Arrowheads in a sequence diagrammedium
- A guard on a state transitionmedium
- Reading a Pareto analysismedium
- Mistake-proofing a stepmedium
- Maker and checkermedium
- When automation failsmedium
- Off-page connectors in BPMNmedium
- Parts of a data flow diagrammedium
- A spaghetti diagrammedium
- Where to start a process mapmedium
- When an inclusive join continuesmedium
- Agreeing where a process startsmedium
- Muda, mura and murimedium
- A script taskmedium
Hard 35
- A metric with a side effecthard
- Waiting for the first eventhard
- Parallel split, exclusive mergehard
- Exclusive split, parallel joinhard
- 'Make it work like the old one'hard
- Duplicate customer recordshard
- Finding the bottleneckhard
- Fit-gap for an off-the-shelf CRMhard
- Undoing a hotel bookinghard
- DMN hit policyhard
- Signal or message eventhard
- Demand above capacityhard
- Comparing logs to the modelhard
- Automating a broken processhard
- Rolled throughput yieldhard
- Running approvals in parallelhard
- A diagram at three levels at oncehard
- A model for people or for an enginehard
- Conditions that overlaphard
- A transaction sub-processhard
- The asterisk gatewayhard
- Message flow between two laneshard
- Escalation vs error eventshard
- Data moving between two storeshard
- Steps with no fixed orderhard
- Testing a design before launchhard
- Optimising for staff or customershard
- The cost of a weekly batchhard
- Not every case needs full reviewhard
- A good design that nobody followshard
- Leading vs lagging process measureshard
- Cost per case from the modelhard
- Reacting to a control charthard
- Two flows into one taskhard
- Proving the redesign workedhard