{'fraction_non_alphanumeric': 0.016098484848484848, 'fraction_numerical': 0.001893939393939394, 'mean_word_length': 5.109826589595376, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Agile ERP systems development: a technical perspective

This paper analyzes different technical quantitative aspects of ERP systems development and maintenance in agile approach context. ERP systems usually have huge numbers of tables and related classes, with a growing complexity that easily gets difficult to manage. The problem is to identify what are the things that are used often, what are the things that not used, and which ones are worthy of investing our time in improving. To determine these points precisely from technical perspective this paper analyzes the data from several technical aspects.
 Usually an upgrade is worth up to 1/3 of initial investment and this approach has helped us achieve productive ERP system development environment, and enabled us to perform an ERP system upgrade to second next version, skipping a whole version, which is even more worthier. The analysis that was performed is shown to be advantageous in the way of quantitative technical approach, in comparison to previous, more soft skills oriented, approaches.