← Selected work
Product EngineeringProduct/UAT Collaboration

Modular ERP — Product and UAT Collaboration

I contributed product reviews and User Acceptance Testing to a modular ERP for service-oriented businesses. The product covers customer and project management, scheduling, inventory, expenses, invoicing, payroll, and administration.

Overview

I contributed product reviews and User Acceptance Testing to a modular ERP for service-oriented businesses. The product covers customer and project management, scheduling, inventory, expenses, invoicing, payroll, and administration.

Attribution

My role was product collaboration, workflow review, testing, and User Acceptance Testing. Rasmad Ibnu and the Naestra team developed the software in the private repository. I did not author the application code described here.

Context

An ERP workflow can span several screens and user roles. During UAT, I checked whether those steps matched the expected business process, including permissions, validation, and the result visible to the user.

My Role

  • Reviewed business workflows and product behavior.
  • Exercised end-to-end scenarios from an operational user's perspective.
  • Reported usability, validation, navigation, and workflow issues.
  • Checked whether expected outcomes matched product requirements.
  • Contributed feedback for onboarding, invoicing, dashboard, and operational flows.
  • Distinguished implementation defects from product decisions requiring clarification.

UAT Approach

Business scenario
  -> prerequisites and test data
  -> user journey execution
  -> expected-versus-actual comparison
  -> issue classification and evidence
  -> retest after correction
  -> acceptance or follow-up decision

Results

I turned business expectations into test scenarios, compared expected and actual behavior, and reported issues for the engineering team to review and retest.

Limitations

  • This is not presented as my software implementation.
  • Private product architecture, customer configuration, screenshots, and source code are excluded.
  • UAT evidence and production status are not published without team approval.

Technology Context

The private product uses a TypeScript monorepo with Next.js, NestJS, PostgreSQL, background processing, reusable modules, and role-aware multi-tenant workflows.

Publication Note

This page is limited to my collaboration and UAT responsibilities. More detailed product material requires explicit permission from the product owners and implementation team.

Checks and current status

Verified Local

Workflow assessment

My work covered product review and UAT scenarios.

I reviewed workflows, ran UAT scenarios, and reported issues. Rasmad Ibnu and the Naestra team developed the application code.

Role

Product / UATWorkflow review, testing, and acceptance activities are clearly attributed.

Implementation

Team-ownedRasmad Ibnu and the Naestra team are credited.

Public UAT result

Not publishedPrivate evidence requires team approval.

Limitations: No customer configuration, private screenshots, source code, or unsupported production claim is included.