103522096 吳仲理 Using Lean in Application Development to achieve competitive advantage and customer delight N. Balaji Ganesh, WIPRO Technologies 20/12/2013.

Slides:



Advertisements
Similar presentations
The 4 T’s of Test Automation:
Advertisements

Metrics and Databases for Agile Software Development Projects David I. Heimann IEEE Boston Reliability Society April 14, 2010.
Adaptive Testing Technique Ajay Chhokra and Jitender Danwani.
PROCESS FRAMEWORK Lecture - 3. Topics covered PROCESS FRAMEWORK PROCESS MODELS DIFFERENCE.
PROJECT TITLE Project Leader: Team: Executive Project Sponsor (As Required): Date: Month/Day/Year 110/17/2014 V1.
Presentation to HRPA Algoma January 29, My favourite saying… Fail to plan, Plan to Fail. 2.
1 Software Processes A Software process is a set of activities and associated results which lead to the production of a software product. Activities Common.
McGraw-Hill/Irwin © 2006 The McGraw-Hill Companies, Inc. All rights reserved BUSINESS DRIVEN TECHNOLOGY Chapter Nineteen: Building Software to Support.
BUSINESS DRIVEN TECHNOLOGY
Continuous Value Enhancement Process
Roadmap to Continuous Integration Testing and Benefits Gowri Selka, Walgreens Natalie Koltun, Walgreens May 20th, 2014 ©2013 Walgreen Co. All rights reserved.
Object-oriented Analysis and Design
F29IF2 : Databases & Information Systems Lachlan M. MacKinnon The Domain of Information Systems Databases & Information Systems Lachlan M. MacKinnon.
Unit Five – Transforming Organizations
Illinois Institute of Technology
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Validating and Improving Test-Case Effectiveness Author: Yuri Chernak Presenter: Lam, Man Tat.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Lean Manufacturing Case Study Prototype Design-Build.
Change Request Management
Effective Methods for Software and Systems Integration
Development of integrated design methodology for various types of product- service systems Author: Tuan A. Tran and Joon Y. Park – DGU, Korea Teacher:
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
1 Portfolio Management – Agile How to plan like a VP Highsmith, Ch 12 CSSE579 Session 6 Part 2 One company’s software product portfolio.
Chapter 2 The process Process, Methods, and Tools
Maintaining Information Systems Modern Systems Analysis and Design.
CLEANROOM SOFTWARE ENGINEERING.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
© 1998 by Prentice-Hall Inc Russell/Taylor Oper Mgt 2/e Chapter 15 Lean Operations in Services and Support Functions.
Understand Application Lifecycle Management
 There are many definitions of marketing. The better definitions are focused on customer orientation and the satisfaction of customer needs.
LEAN for Competitive Advantage and Customer Delight – Case study of an Application Development (AD) project Agile India 資工四 黃泓霖 1.
Presenter: 王秉森 Progression towards Agility: A comprehensive survey.
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem Darwish.
Software Project Management Lecture # 7. What are we studying today? Chapter 24 - Project Scheduling  Effort distribution  Defining task set for the.
Redesigning the Website Matt “The Cat” Pittner Dr. Carl “Arizona” Rebman MSIT 573 Summer 2005.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
Visualization and Agile Practices to the Rescue of Traditional Project Balaji.M, Srinath C HCL Technologies, Pvt, Ltd 資工碩一 林成馨.
TESTING LEVELS Unit Testing Integration Testing System Testing Acceptance Testing.
9. Applying scientific tools & techniques for improving customer satisfaction.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
PROJECT TITLE Project Leader: Team: Executive Project Sponsor (As Required): Date: Month/Day/Year 16/25/2015 V2.
PRJ566 Project Planning & Management Software Architecture.
Software Engineering Lecture # 1.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Agile Adoption G8way Health Project.
Software Testing Process
An Agile Requirements Approach 1. Step 1: Get Organized  Meet with your team and agree on the basic software processes you will employ.  Decide how.
Management Information Systems Islamia University of Bahawalpur Delivered by: Tasawar Javed Lecture 3b.
1 SCR756 – Enhancements to the MarkeTrak application –Fondly called - MarkeTrak Phase 3 –ERCOT CEO determined that SCR756 is not necessary prior to the.
Cisco Consulting Services for Application-Centric Cloud Your Company Needs Fast IT Cisco Application-Centric Cloud Can Help.
Systems Development Life Cycle
Choosing Lean Manufacturing Presented to you by : Vrunda Consultancy Service, Ahmedabad.
Developing and Implementing Marketing Plans. Learning Outcomes To be able to discuss the meaning of a marketing plan (E) To be able to analyse the internal.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Change Request Management
Methodologies and Algorithms
Agile Scrum Management
Transforming Organizations
Владимир Гусаров Директор R&D, Dell Visual Studio ALM MVP ALM Ranger
Software Development Life Cycle
Quantifying Quality in DevOps
Automated Testing and Integration with CI Tool
Welcome to the Ericsson journey towards an Agile WoW!
Software engineering -1
Open Source Tool Based Automation solution with Continuous Integration and end to end BDD Implementation Arun Krishnan - Automation Manager Maria Afzal-
Industry Engagement Program Medical Diagnostic Imaging (MDI) Equipment
Open Source Tool Based Automation solution with Continuous Integration and end to end BDD Implementation Arun Krishnan - Automation Manager Maria Afzal-
Presentation transcript:

吳仲理 Using Lean in Application Development to achieve competitive advantage and customer delight N. Balaji Ganesh, WIPRO Technologies 20/12/2013

Outline Abstract Background Approach Feedback Conclusions

Abstract According to an IBM study, only 40% of projects meet schedule, budget and quality goals. 20 to 25 percent don’t provide ROI up to 50 percent require material rework.

Abstract With competitive pricing and cut throat competition eroding margins and denting market share cost of delivery reduction with best in class quality has become an imperative for any service company in the IT outsourcing space.

Background Based on the success stories from various accounts across the organization that had implemented LEAN tools / techniques to reduce defects, time to market and eliminate waste to maximize business outcomes, the project team felt that “LEAN” was the way to go to address the business challenges and deliver world class quality within schedule.

Background ❖ The team was performing requirements gathering for the first time. ❖ Significant code reuse from previous releases. ❖ High degree of dependencies between the modules impacted by the enhancements. ❖ High proportion of fresh or new developers in the team. ❖ Test execution timelines were aggressive and included regression testing for states already in production ❖ Good number of data combinations to be considered for testing.

Approach The following tenets were identified for implementation based on the challenges listed above: -Visual Controls -Mistake Proofing -Design Structure Matrix -Orthogonal Arrays

Tenet 1 – Visual Controls It was observed that the tasks were allotted in an ad-hoc manner which led to uneven workload across the team. This also created bottlenecks for smooth flow of work. With the requisite inputs and ideas from the team, Kanban visual boards were designed to create views of the work in progress across the various phases of the lifecycle, highlight the backlogs and create flow.

Tenet 2 – Mistake Proofing The top contributors were design documentation errors, implementation errors, inappropriate code reuse, merge issues, and false positives due to incorrect environment configuration. ensure adherence to relevant coding standards and guidelines APIs / code proposed for reuse were reviewed and validated

Tenet 3 Design Structure Matrix DSM is a mathematical and visual representation of the forward and reverse dependencies between the various elements in the system grouped according to the increased order of dependency. Elements could be components / modules, features, use case scenarios, Agile stories.

Tenet 3 Design Structure Matrix

Tenet 3 Design Structure Matrix Module level complexity factors helped towards optimum task allocation / distribution. The general thumb rule was to have the more complex modules or ones with cyclic dependencies allotted to the collocated teams.

Tenet 4 – Orthogonal Arrays The traditional method of test case development based on screen navigations was quite cumbersome and effort intensive with the risk of missing out some crucial combinations. OA with strength of array 3 was deployed on the regression test suite to reduce the number of test cases by 64%.

Benefits The number of defects was reduced by 69.3% for comparable releases leading to significant reduction in rework and test execution effort. Development productivity was enhanced by 33.33%.

Conclusions Overall, this project resulted in increased customer goodwill, reduced time to market, reward payments, enhanced repeat business and high employee satisfaction. “Small things make a big difference”