{'fraction_non_alphanumeric': 0.022340425531914895, 'fraction_numerical': 0.0, 'mean_word_length': 6.075187969924812, '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': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Agile Commitments: Dealing with Business Expectations Risks in Agile Development

Agile methods have been proposed to increase customer satisfaction and deliver business value early, yet usually don’t focus on progress visibility other than software deliverables. However, many customers demand risk visibility over the main aspects that define their expectations: functionality (scope), budget, time-to-market, and product quality. This article proposes an agile commitment framework based on structured definition and follow-up of commitments among customers and developers. The framework uses commitment management to improving risk management by enhancing visibility of business expectation risks, by providing a negotiation baseline among customers and developers, and by allowing mitigating action when appropriate. Finally, we summarize several case studies run to evaluate the proposed framework in academic and industrial settings.