An international mail-order company introduces the FIFO principle (first in, first out) in the stock allocation processes for a series of its constituent companies. This replaces the allocation of stock according to specified priorities.
In the context of agile software development (scrum), there is a detailed analysis based on the requested technical functions (features). An as-is analysis is used to break the features down into packages, prioritize the features and pass them on to development in the form of stories. Self-defined functional test cases are used by the developer to accept the functions implemented in the Java application. The specialist departments are given support in creating test cases and carrying out and analyzing the results of test cases, within the context of the functional network test, administered by Mercury Quality Center. All the implemented functions are documented in the form of use case documents. Functional sequences are modeled in Agilian with the help of BPMN (Business Process Model and Notation).
Purchase order items that cannot be supplied from the stock of inventory as soon as the initial customer order is received are shifted to a subsequent delivery. These items are only awarded a stock commitment once the corresponding goods receipt is posted for the item. In this process, the oldest purchase order items are allocated stock first, and the newest last. Sometimes, stocks of inventory are overbooked, e.g. due to loss of stock. These overbooking are corrected repeatedly each day by removing the stock commitment from a corresponding number of existing items. Again, the items that were allocated last to stock are the first to lose their commitment. The oldest stock commitments are the last to be deleted. The old stock allocation system, which was independent of the order date or allocation date and followed a complex system of priorities, is hereby replaced with a simple, fairer procedure.