{'fraction_non_alphanumeric': 0.01804812834224599, 'fraction_numerical': 0.0, 'mean_word_length': 5.537117903930131, '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}}
Maturing the Scrum Framework for Software Projects Portfolio Management: A Case Study-Oriented Methodology

In the modern era, information technology-based solution providers are encountering a growing request for satisfying the versatile requirements of their customers in terms of software applications. To this end, specific approaches have been designed to streamline the way of accomplishing software projects in an efficient manner, i.e., agile-oriented frameworks. Even though previous studies have highlighted variations of such a framework, the literature has not addressed the adaptations required in response to the gradual maturity of a wide-ranging case study dealing with software applications. Following a case study-oriented methodology, this paper focuses on elaborating a set of workable maneuvers to mature the Scrum framework when applied to portfolio management. Particularly, we highlight how Scrum should be adapted from its basic setting to a vision and goal-oriented configuration or Scrumban under certain conditions. As a maturing practice, we propose a heuristic scoring technique to determine the sprint length of subprojects with different characteristics in the context of a portfolio. The study also introduces a multi-level refinement structure to enhance the monitoring of the teams’ performance under the proposed mature framework. The results obtained display a considerable spike in the realization rate of release planning in light of the actual performance.