Skip to content

Repository files navigation

AMRIT SDLC — Interactive Process Board

A Miro-style, infinite-canvas visualization of the AMRIT platform's Software Development Lifecycle. Pan, zoom, and click through every stage of the process — who owns it, what actions happen, what goes in, and what comes out.

Source of truth: the AMRIT Software Development Lifecycle SOP on Confluence.

Views

View What it shows
Ticket Lifecycle Two segments on one board: the per-ticket workflow (BRD → Closed — tickets close right after QA approval) and the release-level workflow (Release UAT → Release Approved → Production Release), tracked on a release ticket and rendered in a dashed zone. Four swimlanes — Business & Product, Engineering, QA, IT/DevOps — with animated flow and rework edges. Press ▶ Follow a ticket to watch the entire journey with camera follow.
Roles All 12 roles with responsibilities, deliverables, and tools, grouped by function. The Scrum Master function is a hat worn by the Project Manager.
Git & Releases Branching model (main / release-X.Y.Z / `feature
Incidents The L1 → L2 → AMM Engineering escalation flow, severity-based handling (JIRA priorities: Blocker · Highest · Medium · Low · Lowest · Minor), and the RCA-before-closure gate.
Agile Cadence The 2-week sprint loop: grooming → planning → standups → work → review → retro.

Every card opens a detail panel with responsibility · actions · inputs · outputs · tools · exit criteria. Views are deep-linkable (#/gitflow, #/incident, …). Dark and light themes.

Stack

Vite · React 19 · TypeScript · React Flow (@xyflow/react) · Framer Motion · Zustand · IBM Plex. Edge animations are pure CSS/SMIL — zero React renders per frame — and respect prefers-reduced-motion.

Updating the content

All SOP content lives in typed data files under src/data/ — components never hardcode process text. When the SOP changes:

  1. Edit the relevant file: lifecycle/stages.ts, roles.ts, gitflow.ts, incident.ts, or agile.ts.
  2. Run npm test — integrity tests verify every reference (stages, roles, lanes, edges) still resolves.
  3. Push to main — GitHub Actions builds and deploys automatically.

Development

npm install
npm run dev        # http://localhost:5173/sdlc/
npm run typecheck  # strict TS
npm test           # data integrity tests (vitest)
npm run build && npm run preview

Deployment

Pushes to main trigger .github/workflows/deploy.yml: typecheck → tests → build → rsync dist/ to the AMRIT tools server. Live at https://amrittools.piramalswasthya.org/sdlc/.

Repo secrets used by the workflow: DEPLOY_SSH_KEY, DEPLOY_KNOWN_HOSTS, DEPLOY_USER, DEPLOY_HOST.


🤖 Built with Claude Code

About

AMRIT SDLC lifecycle board — interactive React Flow visualization of the AMRIT software development lifecycle

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages