Learning & career
6 posts tagged #business-analysis on DiCodeWeb, from fundamentals to production, newest first.
6 postsUpdated Oct 8, 2026
From metric definitions precise down to the numerator, denominator and time window, through tracking plans and user identity, to real PostgreSQL for funnels, cohort retention, DAU/WAU/MAU, window functions, the Asia/Ho_Chi_Minh timezone and A/B tests with an SRM check.
A good PRD isn't long, it's clear. This post covers PRD structure, writing testable requirements, measurable NFRs using ISO 25010 (p95 performance, SLOs, security, Vietnam's Decree 13 and data protection law, WCAG 2.2 AA), traceability from goal to test, and a complete sample PRD.
Event Storming is the bridge between business analysis and software design. This post covers the three workshop levels, the sticky-note grammar, facilitation, a real clinic booking example, finding bounded contexts, context mapping, and turning the result into aggregates, commands and events in NestJS.
BPMN isn't for decorating project documents; it's for finding where a process wastes time: handoffs, rework loops, waiting. This post covers the notation subset you actually need, common modeling mistakes, a measured as-is/to-be purchase approval example, and the path from model to state machine, workflow engine and user stories.
A good user story isn't the “As a… I want… so that…” sentence, it's the conversation and the examples around it. This post covers the 3 Cs, INVEST with real bad and good examples, story mapping, splitting patterns, acceptance criteria as rules plus examples, Gherkin done right, Example Mapping and turning ACs into automated tests.
Stated requirements are rarely real needs. This post walks engineers and BAs through a business analyst's toolbox: stakeholder mapping, interview technique, shadowing, Jobs-to-be-Done, prototyping, assumption logs, BABOK-style requirement types, and a B2B invoice-approval case study from a Vietnamese company.