The brief

The business needed to bring inventory, vendor management, production, sales and compliance records into a more connected operating model. The requirements included support for traceability and FDA audit preparation.

My role

My contribution was to understand the operation and prepare a Product Requirements Document. The requirements package was separate from the later build and implementation.

What I did

The supporting material includes meeting notes and recordings, with the PRD referring to meetings on 23 and 30 October 2024. I used the operational context to develop the requirements.

I reviewed the supplied inventory worksheet to inform the requirements. It compares stocktake information and includes product, quantity and vendor fields; the records helped connect the requirements to the existing operation.

The output

The PRD contains twelve sections and ten user stories covering warehouse, operations, quality, purchasing, production, sales, customer service, compliance and management perspectives.

It describes six functional areas and five non-functional requirement categories. The 1,000 concurrent-user and 99.9% availability figures are proposed requirements, not measured system performance. Predictive scheduling and direct marketplace integrations are excluded. The proposed plan allocates sixteen weeks across requirements, development, testing, and deployment and training.

What happened next

The PRD was delivered as the requirements package for a proposed build. The build did not proceed on the vendor side; these are documented requirements rather than evidence of an implemented system.