Usage of Agile in Different Technologies Prepared By: Kiran Tej Badana Naveen Kumar Sheela

Overview After introducing Agile in 2001, many companies have tried to adopt Agile in different technologies Adopting Agile for different technologies was difficult Companies tried solving these problems by combining Agile with in house process and made a customized Agile process

Introduction Agile software process model is an innovative approach for rapid application development. Agile Alliance introduced Agile many companies tried to adopt Agile process Companies had problems how to adopt Agile to meet the client expectations

Fundamentals of Agile Individual ideas are more important than process Development is more important than documentation Customer involvement is more important than customer negotiation Quick response to the changes provided by the client

Technologies using Agile Web Application (Extraction Transformation Loading) ETL (Business Process Management) BPM (Enterprise Resource Planning) ERP (Customer Relation Management) CRM

Web Application Web Application is one of the major software market where Agile is considered to be the rule This market is looking for rapid application development , where client looks forward to developing and hosting the web application in very limited amount of time

Agile in Web App Advantages: Excellent client communications Flexibility to change specification Reduce communication gap between developer and client Disadvantage: Less focus on product safety Insufficient documentation for long run projects

ETL Technology This tool extracts the data from databases present in different locations (also known as distributed databases). Converts the data into a single well know format. Stores them in a centralized location (data mart). E – Extraction T- Transformation L- Loading

ETL Process

ETL Tools

Job Roles in ETL ETL Business Analyst ETL Developer ETL Tester

Reasons for Agile Failure Agile is used in ETL Technology at Informatica Corporation and they believes that traditional Agile process is not competent enough to meet the client requirements. The major reason for traditional Agile process model failure is these projects are all long run projects and these projects needs excellent documentation and co-ordination of the team. Informatica Corporation came up with a updated version of Agile process to meet the client requirements

Improved Agile Process

Business Process Management (BPM) Technology Filling the gap between customer and sellers Considering Banking cheque processing

BPM Tools

Reasons for Agile failure Agile provides the flexibility of changing the specification at any point in the development lifecycle. BPM development is started with strong specifications and not making very frequent changes to the project counters Agile Philosophy. Flexibility to change in specs Client involvement in project Pega systems has introduced a new revolutionary IBPM process to meet the client requirements

improved BPM(IBPM) Process BPM process is combined with Agile scrum to form IBPM process

Enterprise Resource Planning (ERP) Technology ERP solution is used for resource planning in organization

ERP Tools

Agile for ERP Agile approach has been applied for few of the projects during the IT industry crises to find out more productive ways of development Surprisingly found to be very productive for developers and for short term projects.

Customer Relationship Management (CRM) Application CRM applications are used to keep track of past and current customers to keep up the business in future.

CRM Tools

Case Study 1: Failure of Agile in implementing CRM application in Sanolabor company. Reasons: Insufficient Skill of employees using it Trying to implement CRM really fast Involvement of process manager must be more for understanding requirements

Conclusion Agile process is not the perfect process for every technology Agile combined with the technology specific and domain specific rules brings up a perfectly new process which is much helpful in the IT industry

References: [1] A. Begel and N. Nagappan, "Usage and Perceptions of Agile Software Development in an Industrial Context: An Exploratory Study", First International Symposium on Empirical Software Engineering and Measurement (ESEM), (2007), pp. 255-264. [2] Anderson, S. (2006). Sanity check: On-demand or on-premise CRM, Destination CRM.com, Viepoint, available at: www.destination-crm.com (15.5.2007) [3] Anderson, D.J.: Kanban: Evolution ̈ares Change Management Organisationen. dpunkt, Heidelberg and Neckar, 1 edn. (2011) [4] M. Ruhe, et al., “Cost Estimation for Web Applications,” Proceedings of the 25th International Conference on Soft-ware Engineering, Portland, 3-10 May 2003, pp. 285-294. [5] Fowler, M., & Highsmith, J. (2001). The agile manifesto. Software Development, 9, 28--35. [6] P. Abrahamsson, et al., "New directions on agile methods: a comparative analysis," in Software Engineering, 2003. Proceedings. 25th International Conference on, 2003, pp. 244-254.