bdfinst/vsm-workshop

Última atividade de origem registrada: 2 de outubro de 2026 às 12:19

Catálogo do SkillsMP atualizado: 2 de novembro de 2026 às 18:02

skills coletadas: 8

Estrelas no GitHub: 19
Forks no GitHub: 7

Instalar com um assistente de IA

Copie este prompt para o assistente de IA que você usa.

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/bdfinst/vsm-workshop.

README do repositório

Arquivo de origem do README: README.md

Ler o README original

Expandir README completo

# Norn > **Weave the work into flow.** **Norn** maps your software delivery value stream, finds the bottleneck, and weaves the work into flow — every thread, end to end. Named for the Norse weavers of fate (Urðr, Verðandi, Skuld — past, present, future), just as Norn holds your current state and future state and the threads of work running between them. Norn is a digital workshop for creating, analyzing, and simulating Value Stream Maps (VSMs). Value Stream Mapping is a lean-management method for analyzing the current state and designing a future state for the series of events that take a product or service from its beginning through to the customer. This tool lets you visually build your value stream (or import a measured current state from real delivery data), input key metrics for each step, and run simulations to identify bottlenecks and calculate overall flow efficiency. ![Norn — an example software-delivery value stream with live flow metrics](docs/norn.png) ## What you can do - **Map your value stream** — drag, connect, and edit steps on a canvas, with process time, lead time, %C&A, queue size, batch size, and rework loops. - **Import a measured current state** — derive a value stream from a real event log (CSV/JSON), or, optionally, straight from Azure DevOps work-item history. Measured maps replace guesses with actual timestamps. - **See the flow metrics** — total lead time, total process time, **flow efficiency**, first-pass yield, queue load, and rework impact, updated live as you edit. - **Diagnose CD readiness** — a scorecard of continuous-delivery practices and signals, a **wait-time waterfall**, and DORA-metric reconciliation. - **Get countermeasures** — the constraint is highlighted and paired with concrete recommendations; WIP and batch levers are modeled with Little's Law. - **Simulate the flow** — run a real-time work-item simulation to watch items move, surface bottlenecks, and compare a **current state vs. a future state** (including a Monte-Carlo lead-time forecast). ## Getting Started Follow these instructions to get a copy of the project up and running on your local machine for development and testing purposes. ### Prerequisites This project uses `npm` as its package manager. Make sure you have Node.js and `npm` installed on your system. - [Node.js](https://nodejs.org/) - [npm](https://docs.npmjs.com/) (included with Node.js) ### Installation 1. Clone the repository: ```sh git clone <repository-url> ``` 2. Navigate to the project directory: ```sh cd norn ``` 3. Install the dependencies: ```sh npm install ``` ## Usage ### Development Server To run the application in development mode with hot-reloading, use the following command. This will start a local server, typically on `http://localhost:5173`. ```sh npm run dev ``` ### Building for Production To create a production-ready build of the application, run: ```sh npm run build ``` The optimized and minified files will be placed in the `dist` directory. ## Testing This project includes several types of tests to ensure quality and correctness. ### Unit & Integration Tests (Vitest) To run the fast unit and integration tests once, execute: ```sh npm test ``` To run these tests in interactive watch mode, use: ```sh npm run test:watch ``` ### End-to-End & Visual Regression Tests (Playwright) To run the end-to-end tests that simulate real user interactions in a browser, use: ```sh npm run test:e2e ``` These include visual-regression snapshots. CI runs the whole suite on every PR inside the pinned Playwright Docker image so rendering matches the committed baselines. Visual snapshots are environment-sensitive, so **regenerate baselines in that same image** rather than with a bare local update: ```sh npm run test:e2e:baseline # runs --update-snapshots inside the pinned image ``` ### Acceptance Tests (Playwright) To run the acceptance tests (Playwright specs in `tests/e2e/`; this builds the app first), use: ```sh npm run test:acceptance ``` To run the unit tests and the acceptance tests together, use: ```sh npm run test:all ``` ### Legacy BDD features (Cucumber) The v1 `.feature` files in `features/` run with Cucumber: ```sh npm run test:bdd ``` ### Everything at once ```sh npm test && npm run build && npm run lint ``` ## CodeGraph This repository uses [CodeGraph](https://github.com/colbymchenry/codegraph) for semantic code intelligence.

Carregando o README do repositório…