Just enough documentation to move fast and clear the gate
OLYM3 Nexus is built with Scrum on two-week sprints, tied to the Blueprint gate review mechanism. The documents below are the single source of reference for the delivery team and for the board.
- 12
- documents in the set
- 8
- product epics
- 20
- user stories written
- 188
- story points estimated
Document catalogue
Every document lives in the repository as Markdown so it can be reviewed by pull request, on the same lifecycle as the code.
Product Charter
Problem statement, vision, in/out of scope, how success is measured and who decides.
docs/agile/00-product-charter.md
Personas & ICP
The ideal customer profile and 8 user personas with their needs, pains and success criteria.
docs/agile/01-personas-and-icp.md
Product Backlog
8 epics, user stories in the role – need – value format, acceptance criteria and MoSCoW priority.
docs/agile/02-product-backlog.md
Release Plan & Sprints
A plan for 8 two-week sprints, sprint goals, the mapping to gate reviews and release criteria.
docs/agile/03-release-plan-and-sprints.md
Definition of Ready / Done
The conditions for a story to enter a sprint and to be considered complete, with no exceptions.
docs/agile/04-definition-of-ready-done.md
Team & Ceremonies
Roles, the RACI matrix, the Scrum cadence and how the team works with the board through gate reviews.
docs/agile/05-team-and-ceremonies.md
Test Strategy & UAT
The test pyramid, acceptance criteria for the 10 PoCs, the UAT process and defect management.
docs/agile/06-test-strategy-and-uat.md
Risk & Governance
Risk register, the G0–G4 gate mechanism, change control, budget discipline and audit trail.
docs/agile/07-risk-and-governance.md
Metrics & Reporting
KPI dictionary, velocity, burndown, quality metrics and the stakeholder reporting cadence.
docs/agile/08-metrics-and-reporting.md
Design System
Colour tokens, typography, spacing, component inventory and accessibility rules.
docs/design/design-system.md
Google Stitch Prompts
The prompt set to regenerate each screen in Google Stitch and the workflow to bring designs into code.
docs/design/stitch-prompts.md
Solution Architecture
The five-layer architecture, Azure workloads, data model, security and environment strategy.
docs/architecture/solution-architecture.md
Personas and success criteria
Every user story in the backlog is written for one of these personas, with a measurable criterion to avoid vague requirements.
| Persona | Primary need | Measured by |
|---|---|---|
| Board of members | Make investment decisions on evidence rather than promises | Gate reviews with complete evidence, TCO and risk register |
| Product Lead | Keep scope and budget within the committed cap | No breach of the 1.5B ₫ cap before G2 |
| Enterprise Architect | Hold the fit-to-standard principle and a scalable architecture | Customisation index below the threshold of 45 |
| Business Analyst | Turn business needs into verifiable requirements | 100% of critical requirements have a matching PoC |
| QA / UAT Lead | Make sure no critical scenario is skipped | 95%+ critical test pass, 90%+ automation |
| Integration Engineer | Stable integration at real scale | 99.9%+ message success on critical flows |
| Chief Accountant | Close fast, reconcile cleanly, comply with e-invoicing | Month-end close in 5 days or fewer |
| Production Manager | See OEE and downtime causes per shift | OEE of 75%+ with drill-down to the incident |
Epics and product backlog
Nexus Assessment Engine
Standardise 35 requirements and score platforms on a 100-point framework
3/3 stories complete
Nexus PoC Lab
Design, run and sign off 10 PoCs on real data
3/4 stories complete
Nexus Insight Control Tower
KPIs with an owner, an alert threshold and drill-down to the source document
1/2 stories complete
Nexus Connect
A reusable connector library with reliability telemetry
0/2 stories complete
Nexus Gate Governance
Gate reviews G0–G4 bound to evidence, releasing budget conditionally
1/2 stories complete
Nexus AI Copilot
An AI assistant answering operational questions with citations
0/2 stories complete
TCO & Business Case
A five-year TCO model and a business case refreshed at every gate
1/2 stories complete
Platform Foundation
Landing zone, security, CI/CD and observability on Azure
3/3 stories complete
User stories and acceptance criteria
Every story follows the role – need – value format with verifiable criteria.
- NX-101MustSprint 0 · 8 points · Cloud Engineer
As a Cloud Engineer, I need a standards-based Azure landing zone so every environment is isolated and cost-controlled
- Four environments (Dev/Test/UAT/Prod) split by subscription or resource group
- Budget alerts fire at 50/80/100% of the monthly budget
- Key Vault holds every secret; no secrets in source code
- NX-102MustSprint 0 · 5 points · Developer
As a Developer, I need a CI/CD pipeline so every change is built, tested and deployed automatically
- The pipeline runs lint, typecheck, unit tests and build on every pull request
- Merging is blocked while the pipeline is red
- Automatic deployment to Test on merge into the main branch
- NX-103MustSprint 0 · 8 points · Enterprise Architect
As an Enterprise Architect, I need Entra ID and RBAC so permissions follow roles across the whole portal
- SSO through Entra ID works for 4 roles
- The RBAC matrix is approved and enforced at the API layer
- Every material action writes an immutable audit trail
- NX-111MustSprint 1 · 8 points · Business Analyst
As a Business Analyst, I need NERP requirements with identifiers so every assessment is traceable
- Every requirement has a code, domain, dimension, criticality and weight
- Critical requirements must link to a PoC or carry a documented waiver
- The requirement catalog exports to a file for the gate pack
- NX-112MustSprint 2 · 13 points · Enterprise Architect
As an Enterprise Architect, I need a 100-point scoring framework so platforms are compared with transparent weights
- The 8 dimension weights always sum to 100
- The total score updates the moment a requirement's fit level changes
- Critical gap count and the customisation index are displayed
- NX-113MustSprint 2 · 8 points · Leadership
As a Board member, I need fit-gap and platform benchmarks so decisions do not rest on self-assessed scores alone
- Platform benchmarks are shown with their data source
- State clearly that the OLYM3 Architecture score measures architecture capability, not an ERP score
- Every critical gap has a treatment and a cost converted into money
- NX-121MustSprint 3 · 13 points · QA/UAT Lead
As a QA Lead, I need to manage the scenarios of all 10 PoCs so the pass rate is visible in real time
- Each PoC lists its scenarios, expected results and status
- Pass rate and automation rate are computed per PoC
- A PoC cannot be marked as passed while a critical scenario is still open
- NX-122MustSprint 3 · 5 points · Product Lead
As a Product Lead, I need each PoC to declare its data source so we can prove no demo data was used
- Each PoC records its dataset, scope and the person who confirmed the data
- A warning appears when a PoC uses unconfirmed simulated data
- NX-123MustSprint 4 · 13 points · BA Finance
As a Finance BA, I need the intercompany and costing PoC to prove reconciliation across two real accounting periods
- Matching entries are generated automatically in both legal entities
- The reconciliation difference is zero after the period is closed
- Actual costing separates price, quantity and efficiency variances
- NX-124MustSprint 5 · 8 points · QA/UAT Lead
As a QA Lead, I need the quality PoC to block shipment of unreleased lots so the end customer is protected
- 100% of held lots are blocked at the issue step
- Each NCR has an owner, a deadline and a corrective action
- A closed CAPA loop carries evidence of effectiveness
- NX-131MustSprint 5 · 13 points · Leadership
As leadership, I need a control tower showing KPIs with owners so every metric has someone accountable
- Every KPI has an owner, a target, a trend and a next action
- On-target and off-target metrics are visually distinct
- Filtering by Product, Business and Customer value groups is possible
- NX-132ShouldSprint 5 · 8 points · Department head
As a department head, I need alerts when a KPI breaches its threshold so I can act before the month is affected
- The alert reaches the owner through Teams within 5 minutes
- The alert includes a drill-down link to the source document
- Alerts can be snoozed with a reason and an expiry
- NX-141MustSprint 6 · 13 points · Integration Engineer
As an Integration Engineer, I need per-connector reliability tracking so we can prove 99.9% before rollout
- Success rate, message count and latency are shown over 30 days
- Failed messages land in a dead-letter queue and can be reprocessed
- Retries use backoff and remain idempotent
- NX-142MustSprint 6 · 8 points · Chief Accountant
As a customer, I need the e-invoicing connector so my team never has to enter data twice
- Invoices are issued with a digital signature and acknowledged successfully
- Invoice status syncs back into the system
- Issuance failures display a specific cause
- NX-151MustSprint 2 · 13 points · Leadership
As a Board member, I need gate reviews to release budget only on evidence so funding risk stays controlled
- Every gate criterion is bound to specific evidence
- A gate cannot move to approved while a criterion is unmet
- The decision, the approver and the timestamp are recorded
- NX-152MustSprint 6 · 5 points · Product Lead
As a Product Lead, I need to track pilot spend against the 1.5B ₫ cap so we never breach it
- Spent, remaining and end-of-pilot forecast are displayed
- An alert fires when the forecast exceeds the cap
- NX-161ShouldSprint 7 · 13 points · Leadership
As leadership, I need to ask KPI questions in natural language and get answers with citations
- Every answer carries its data source and last-updated time
- The assistant declines to answer rather than guessing when data is insufficient
- Questions and answers are logged for audit
- NX-162CouldSprint 7 · 8 points · BA Procurement
As a Procurement BA, I need AI to detect anomalies in purchasing spend so I can review them early
- Transactions deviating abnormally from history are detected
- Each alert carries a confidence level and a reason
- NX-171MustSprint 4 · 13 points · Leadership
As leadership, I need a five-year TCO model with scenarios so options can be compared before deciding
- At least 3 cost scenarios are compared
- Customisation cost is converted into both money and risk
- Changing the user count recalculates the whole model
- NX-172ShouldSprint 7 · 5 points · Founder
As a Founder, I need the business case refreshed after each gate so I can present to investors and partners
- The business case is bound to the latest KPI data
- An investor-ready deck can be exported
Sprint plan
Two-week sprints, each with a single goal. Sprints tied to a gate end with a gate review with the board.
| Sprint | Goal | Window | Committed | Completed | Gate |
|---|---|---|---|---|---|
| S0Foundation | Landing zone, D365 sandbox, CI/CD and security baseline ready | 18 Aug – 31 Aug 2026 | 26 | 26 | G0 |
| S1Requirement Catalog | 35 NERP requirements with identifiers, dimensions and evidence criteria | 1 Sep – 14 Sep 2026 | 34 | 34 | — |
| S2Assessment Engine | The 100-point framework runs and the fit-gap matrix can be exported | 15 Sep – 28 Sep 2026 | 38 | 36 | G1 |
| S3PoC Lab v1 | P1 and P5 pass every critical scenario on real data | 29 Sep – 12 Oct 2026 | 40 | 40 | — |
| S4Finance & Manufacturing PoC | P2, P4 and P8 pass; costing and intercompany reconcile | 13 Oct – 26 Oct 2026 | 42 | 39 | — |
| S5Control Tower & Quality | P9 passes; P3 and P6 reach at least 60% of scenarios | 27 Oct – 9 Nov 2026 | 40 | 33 | — |
| S6Integration & EAM | P10 and P7 complete with message success of at least 99.9% | 10 Nov – 23 Nov 2026 | 38 | 21 | G2 |
| S7MVP Packaging | Package the MVP, ship the first industry template and AI assistant v1 | 24 Nov – 7 Dec 2026 | 36 | 0 | — |
Quality and working cadence
Definition of Ready
- The story follows the role – need – value format and links to an epic
- Acceptance criteria are verifiable and unambiguous
- The related NERP requirement or PoC is identified
- Sample data or a data source exists for testing
- Estimated in story points and no larger than 13 points
- No unconfirmed external dependencies
Definition of Done
- Every acceptance criterion is verified with retained evidence
- Automated tests for critical flows are written and passing
- Typecheck and lint are clean
- Security: no secrets in source code, access follows RBAC
- Documentation and screenshots are updated in the evidence pack
- Demoed in Sprint Review and accepted by the Product Owner
- Deployed to the Test environment with no regressions
Scrum ceremonies
Sprint Planning
Monday of sprint week 1, 2 hours
Sprint goal and an estimated sprint backlog
Daily Standup
Daily at 09:15, 15 minutes
Progress update and impediments
Backlog Refinement
Wednesday of week 1, 90 minutes
Stories meeting the Definition of Ready for the next sprint
PoC Evidence Review
Every Friday, 60 minutes
PoC evidence confirmed or returned
Sprint Review
Final Friday of the sprint, 90 minutes
Increment demo for stakeholders with feedback captured
Retrospective
Final Friday of the sprint, 60 minutes
At most 3 improvement actions, each with an owner
Gate Review
End of each phase
A G0–G4 decision and the budget released
Need the full text of each document? Everything lives in the docs/ folder of the repository, reviewed by pull request alongside the code. Open Nexus Console to see these documents live, bound to the programme's real data.