Browse Prior Art Database

Persuasive Software Method Adoption and Standardization

IP.com Disclosure Number: IPCOM000225092D
Publication Date: 2013-Jan-24
Document File: 5 page(s) / 104K

Publishing Venue

The IP.com Prior Art Database

Abstract

Software methods and processes refer to the activities that examine, evaluate, measure and improve software development projects. Standard methods exist in all large organizations for all important practices. However, many social and technical challenges impede widespread software method adoption. Software development team collaboration tools like Rational Team Concert©™, Microsoft Team Foundation©™ etc, provide a single, integrated environment for several aspects of the software development process, including agile planning, process definition, source control, defect tracking, build management, and reporting. Despite all their current features and capabilities, these tools however still lack a proactive method guidance and support system which can persuade users to adopt the method. They rather end up imposing rules which determine whether or not some user actions are permissible. In this paper, we present a system and method to persuade users to adopt a software method and thus promote standardization. Our method-adherence score based approach provides a guidance and support system for method, increases the knowledge level of developers and ties incentives to method adoption, thus accelerating software method adoption.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 28% of the total text.

Page 01 of 5

Persuasive Software Method Adoption and Standardization

Persuasive Software Method Adoption and Standardization

Abstract Software methods and processes refer to the activities that examine, evaluate, measure and improve software development projects. Standard methods exist in all large organizations for all important practices. However, many social and technical challenges impede widespread software method adoption. Software development team collaboration tools like Rational Team Concert©™, Microsoft Team Foundation©™ etc, provide a single, integrated environment for several aspects of the software development process, including agile planning, process definition, source control, defect tracking, build management, and reporting. Despite all their current features and capabilities, these tools however still lack a proactive method guidance and support system which can persuade users to adopt the method. They rather end up imposing rules which determine whether or not some user actions are permissible. In this paper, we present a system and method to persuade users to adopt a software method and thus promote standardization. Our method-adherence score based approach provides a guidance and support system for method, increases the knowledge level of developers and ties incentives to method adoption, thus accelerating software method adoption.


1. Introduction

Software methods and processes refer to the activities that examine, evaluate, measure and improve software development projects. Software processes are used to improve quality, timeliness, efficiency, productivity, and other project and product characteristics. A software method defines various phases, activities, tasks, work-products (and optionally other elements such as risks, outcomes), and their possible inter-relationships like "predecessor - successor dependence" between tasks and "input-output work-products" from tasks etc. Standard software methods are thus key to industrialized service delivery. All service delivery organizations strive to industrialize delivery and deliver excellence by reducing risks, promoting user collaboration and E2E traceability with standard methods and delivery processes.

Standard methods exist in all large organizations for all important practices, e.g., Application Delivery method for AIS Practice in IBM©™. Standard tools to operationalize these methods also exist. However, many social and technical factors like the following impede widespread software method adoption -

What is my knowledge level about the method? What support system for the method is available?

How easy/difficult it is to follow method guidelines? How much does the new method deviate from my current

method?

What are the incentives if I follow the method?

How confident I am and others are about the usefulness of the method?

Non-adherence to standard methods results in major business problems like -

Increased Project Risks - Project as well as Delivery Excellence te...