DOCSLIB.ORG

Agile Test Automation Strategy, V2.Pptx

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

MJ Half-day Tutorials 10/3/16 13:00 Test Automation Strategies for the Agile World Presented by: Bob Galen Velocity Partners Brought to you by: 350 Corporate Way, Suite 400, Orange Park, FL 32073 888---268---8770 ·· 904---278---0524 - [email protected] - http://www.starwest.techwell.com/ Bob Galen Velocity Partners An agile methodologist, practitioner, and coach, Bob Galen ([email protected]) helps guide companies in their adoption of Scrum and other agile methodologies and practices. Bob is a principal agile evangelist at Velocity Partners; president of RGCG; and frequent speaker on software development, project management, software testing, and team leadership. He is a Certified Scrum Coach, Certified Scrum Product Owner, and an active member of the Agile and Scrum Alliances. Bob published Scrum Product Ownership–Balancing Value from the Inside Out. Test Automation Strategies for the Agile World Bob Galen President & Principal Consultant RGCG, LLC [email protected] Introduction Bob Galen n Independent Agile Coach (CEC) at RGCG, LLC n Director, Agile Practices at n Somewhere ‘north’ of 30 years overall experience J n Wide variety of technical stacks and business domains n Developer first, then Project Management / Leadership, then Testing n Senior/Executive software development leadership for 20+ years n Practicing formal agility since 2000 n XP, Lean, Scrum, and Kanban experience n From Cary, North Carolina Bias Disclaimer: Agile is THE BEST Methodology for Software Development… However, NOT a Silver Bullet! Copyright © 2016 RGCG, LLC 2 1 Outline n Traditional Automation – Business Case & ROI n 3-Pillars n Agile Test Automation Pyramid n Agile Automation – Business Case & ROI n Implementation Strategy n Communication n Wrap-up Copyright © 2016 RGCG, LLC 3 Let’s start with… Traditional Automation Strategy n What are your current strategies towards: q Test Automation q Frameworks q Tooling q Maintenance q ROI q Team structure n Get together in “pairs” and chat about this for 20 minutes. List your approaches and tactics. n Then leverage SWOT or FFA analysis to capture your current position. Then we’ll gather your results… Copyright © 2016 RGCG, LLC 4 2 Let’s start with… Traditional Automation Strategy n SWOT – Often used to analyze strategic direction or positions. List the “position”, then identify aspects of: q Strengths q Weaknesses q Opportunities q Threats Often in Quadrants n Force Field Analysis – again, list a position q Forces (FOR) è q Forces (AGAINST) ç Copyright © 2016 RGCG, LLC 5 Traditional Automation Business Case & ROI Copyright © 2016 RGCG, LLC 6 3 It’s simple really… n Manual testing is: q Slow q Labor intensive q Not intellectually stimulating q Error prone q Iterative q Did I say slow? n And we’re testing software…right? q So we ought to be able to automate the testing. Copyright © 2016 RGCG, LLC 7 It’s simple really… n Automated tests are: q Fast q Low/no errors q Free after initial development q Run continuously q Did I say fast? q Did I say ‘free’? n And we’re testing software…right? q So we ought to be able to automate ALL of the testing. Copyright © 2016 RGCG, LLC 8 4 Test Automation ROI Sample Points – Manual Testing ü Capture size of the team ü Cost per tester – usually hourly ü # of Test cases to be run ü Time to run them ü Cyclical nature of the testing cycles (regression, integration, system, etc.) ü Configurations ü Number of tests run per release ü Number of releases per year n Do the math to come up with iterative testing run-time investments…and costs Copyright © 2016 RGCG, LLC 9 Test Automation ROI Sample Points – Automation Development n Then contrast that against the cost for automation: ü Time / cost to establish automation infrastructure ü Time / cost to establish automated tests ü Time / cost for ongoing maintenance and results analysis ü Cost for automation tooling – depends on ‘type’, ex: Keyword Driven ü Cost per automation developer vs. manual tester ü Automation replacement target for manual test cases n Do the simple, discrete math to come up with cost & time to replace manual testing run-time and ROI savings Copyright © 2016 RGCG, LLC 10 5 Traditional Business Case n Run more tests, faster and with fewer people (lower costs) n VALUE being driven by: Running tests! n Did I say with fewer people (testers)? q We can hire more developers with the cost savings! And get MORE done… q We can even reduce the size of the bathrooms J Copyright © 2016 RGCG, LLC 11 http://www.aspiresys.com/testautomationroi/index.php#ROI Copyright © 2016 RGCG, LLC 12 6 http://www.aspiresys.com/testautomationroi/index.php#ROI Copyright © 2016 RGCG, LLC 13 Sample of Test Automation ROI calculators n Aspire Systems seems to have pulled down their link, here are other samples… q http://sourceforge.net/projects/ta-roi/ q http://www.automatedtestinginstitute.com/home/index.php? option=com_content&view=article&id=58:roi- calculator&catid=37:calculators&Itemid=65 q http://www-01.ibm.com/software/rational/offerings/testing/roi/tool/ ROI_Rational.html Copyright © 2016 RGCG, LLC 14 7 But often there is underestimation of risks… So the ROI was always a ‘fuzzy’ estimate § Underestimating the nature of a software project § Architecture & design, complexity, risks, unknowns, ambiguity, etc. § Underestimating parallel software projects (product + automation) complexity § Integration, dependencies, coordination § Underestimating ongoing support & maintenance § Repairs & updates § Designing and adding new tests § Impact of new product technologies § Underestimating skill levels for automation development Copyright © 2016 RGCG, LLC 15 It’s also very dangerous! Will Robinson… § It’s commoditizing your testing activity. Could you imagine – § Measuring developer value by LOC…and doing ROI? § Measuring architectural integrity by complexity analysis…and doing ROI? § Measuring product owner value by number of backlog elements…and doing ROI? Based on some sort of automation introduction? Of course not. It’s insane. § Then why do we do it with tests…and testers? Copyright © 2016 RGCG, LLC 16 8 Traditional Test Automation Tools Just a quick stop… n We’re all using them, so they must be good and the approaches must be ‘correct’…right? n However, there are challenges— q Training q Size q UI-centric q COST q Can’t test everything (Back-end database code) q One-size fits all strategy q Limited developer / whole team usage Copyright © 2016 RGCG, LLC 17 Typical Deployment Level of effort MORE Typical Time & Budget Initial design Investment & Architecture LESS é Initial Test Level of Effort - Case Automation Investment ê Technology Disruption Ongoing Maintenance Copyright © 2016 RGCG, LLC 18 9 Now it may sound… n Like I’m opposed to test automation. Truly, I’m not. I think automation rocks! Or like I’m opposed to gaining a ‘return’, absolutely not. q Automation is clearly a foundation element for increased quality and going faster – releasing more often n But, this traditional model or approach of focusing on ROI…is sort of insane Copyright © 2016 RGCG, LLC 19 3-Pillars of Agile Quality & Testing Copyright © 2016 RGCG, LLC 20 10 3-Pillars Genesis n I’ve learned that “Balance” is important n A sad tale of: q Thousands of ATDD testing; Gherkin run amok q All of them are working; continuously testing; increasing “coverage’ and life is Good! n BUT q These same teams couldn’t write a cohesive User Story to save their life q So, where were the Acceptance Tests coming from? Copyright © 2016 RGCG, LLC 21 3-Pillars of Agile Quality Development & Test Software Testing Cross-Functional Team Automation Practices • Risk-based testing: • Pyramid-based Strategy: Functional & Non-Functional • Team-based Pairing (Unit + Cucumber + Selenium) • Test planning @ Release & • Stop-the-Line Mindset Sprint levels • Continuous Integration • Code Reviews & Standards • Exploratory Testing • Attack technical • Active Done-Ness infrastructure in the Backlog • Standards – checklists, templates, repositories • Aggressive Refactoring of • Visual Feedback – Technical Debt Dashboards • Balance across manual, exploratory & automation • User Stories, “3 Amigo” • Actively practice ATDD and based Conversations BDD • Whole Team Ownership of “Quality” • Knowing the Right Thing to Build; And Building it Right • Healthy – Agile Centric Metrics • Steering via: Center of Excellence or Community of Practice • Strategic balance across 3 Pillars; Assessment, Recalibration, and Continuous Improvement 22 Copyright © 2016 RGCG, LLC 11 Foundation of the 3-Pillars • Whole team view includes building it right, • Whole Team Ownership of everyone tests, everyone demo’s, etc. “Quality” • Focus on features/stories, confirmation, • Knowing the “Right” thing to conversation, and getting them staged Build AND Building it “Right” properly OVER testing • Healthy – Agile Centric Metrics • 4-tier metrics: Quality, Value, Prediction, Team • Steering Required – CoE or CoP • Agile strategies need light-handed “steering”; establish a CoE (heavier weight) or a CoP • Strategic balance across 3 (lightweight) Pillars; Assessment, Recalibration, and Continuous • Consider finding an assessment framework Improvement and then tying it to your strategy measurement, recalibration, and continuous improvement. • Make the foundation visible thru information radiators and metrics 23 Copyright © 2016 RGCG, LLC 3-Pillars of Agile Quality A central part of agile adoption is focusing on CI, 3- Development & tiered Automation development, and Dashboards to Test Automation begin incrementally building coverage for faster feedback
Recommended publications
  • Leading Practice: Test Strategy and Approach in Agile Projects

    Leading Practice: Test Strategy and Approach in Agile Projects

    CA SERVICES | LEADING PRACTICE Leading Practice: Test Strategy and Approach in Agile Projects Abstract This document provides best practices on how to strategize testing CA Project and Portfolio Management (CA PPM) in an agile project. The document does not include specific test cases; the list of test cases and steps for each test case are provided in a separate document. This document should be used by the agile project team that is planning the testing activities, and by end users who perform user acceptance testing (UAT). Concepts Concept Description Test Approach Defines testing strategy, roles and responsibilities of various team members, and test types. Testing Environments Outlines which testing is carried out in which environment. Testing Automation and Tools Addresses test management and automation tools required for test execution. Risk Analysis Defines the approach for risk identification and plans to mitigate risks as well as a contingency plan. Test Planning and Execution Defines the approach to plan the test cases, test scripts, and execution. Review and Approval Lists individuals who should review, approve and sign off on test results. Test Approach The test approach defines testing strategy, roles and responsibilities of various team members, and the test types. The first step is to define the testing strategy. It should describe how and when the testing will be conducted, who will do the testing, the type of testing being conducted, features being tested, environment(s) where the testing takes place, what testing tools are used, and how are defects tracked and managed. The testing strategy should be prepared by the agile core team.
  • Agile Test Automation Strategy for Anyone and Everyone!

    Agile Test Automation Strategy for Anyone and Everyone!

    Agile Test Automation Strategy For Anyone and Everyone! Gerard Meszaros [email protected] Much Ado About Agile 2011 1 Copyright 2011 Gerard Meszaros My Background •Software developer 80’s •Development manager Embedded •Project Manager ----- Telecom •Software architect 90’s •OOA/OOD Mentor •Requirements (Use Case) Mentor ----- I.T. •XP/TDD Mentor •Agile PM Mentor 00’s •Test Automation Consultant & Trainer Gerard Meszaros •Lean/Agile Coach/Consultant [email protected] Product & I.T. Much Ado About Agile 2011 2 Copyright 2011 Gerard Meszaros Agenda • Motivation – The Agile Test Problem – The Fragile Test Problem • Approaches to Test AutomationRough timings for Agile Test Automation Strategy Time per slide: 1.4 # of Slide # • Test Automation Strategy # Topic Time Slides Start End Motivation 11.2 8 2 9 Exercise 1 - Automation Motivation 10 1 10 10 Intro to Automation 7 5 11 15 Exercise 2 - Why not Record & Playback? 10 1 16 16 Why Automated Tests are Fragile 8.4 6 17 22 How Agile Automation Changes Things 9.8 7 24 30 Intro to Example-Driven Development 7 5 32 36 Managing Scope vs Detail in Examples 15.4 11 38 48 How to specify workflows 8.4 6 50 55 Exercise 3 - Workflow Tests (Keyword-Driven) 15 1 56 56 Using Data-Driven Tests to specify business rules 8.4 6 55 60 Exercise 4 - Business Rules Test (Data-Driven) 15 1 61 61 How Tests Interact With the SUT 7 5 62 66 Test-Driven Architecture 5.6 4 67 70 Legacy Systems (if time permits) 19.6 14 71 84 The Role of Unit Tests 8.4 6 85 90 Test Automation Strategy 14 10 91 100 180.2 97 Much
  • Test Script Debugger CBTA 3.0 SP11 Document History

    Test Script Debugger CBTA 3.0 SP11 Document History

    Test Automation - User Guide PUBLIC SAP Solution Manager 7.2 2018-12-03 CBTA - Test Script Debugger CBTA 3.0 SP11 Document History Version Date Change 1.6 2018-12-03 CBTA 3.0 SP11 Update 1.5 2018-05-15 CBTA 3.0 SP10 Update 1.4 2017-09-30 CBTA 3.0 SP9 Update 1.3 2017-03-01 CBTA 3.0 SP8 Update 1.2 2014-05-27 CBTA 3.0 SP2 Update CBTA - Test Script Debugger 2 Document History Table of Contents 1 Running a CBTA Test Script in Debug Mode..........................................................................4 2 How-to start .............................................................................................................................5 2.1 Add or remove breakpoint..................................................................................................................................... 8 2.2 Step Over............................................................................................................................................................ 9 2.3 Run...................................................................................................................................................................... 9 2.4 Stop Debugger................................................................................................................................................... 9 2.5 Error Behavior .......................................................................................................................................................10 2.6 Dynamic Report...............................................................................................................................................
  • Infotek Solutions Inc

    Infotek Solutions Inc

    Infotek Solutions Inc. Test Strategy Test Strategy is summarize or outline which describes the approach of software development cycle. Or The test levels to be performed in testing and the description of testing activities within those test levels are known as test strategy. It is created to inform project managers, testers and developers about some key points of testing process. Strategy also includes testing objective, methods to testing new functions, time and resource what will be used in project and testing environment. Test strategies describe how to mitigate the product risk at test level, which of types of test are to be performed in testing and which entry and exit criteria apply. Different Testing strategies may be adopted depending on the type of system to be test and the development process used. In this document we are going to discuss testing strategies on two different types of software testing. 1. Conventional Software 2. Object Oriented Software(OO software) Conventional Software Testing: It is traditional approach. It takes place mostly when water fall life cycle is used for development. Conventional software Testing focuses more on decomposition. Conventional software testing always takes place during the test phase of life cycle, which usually follows the development phase and proceeds the implementation phase. During the conventional testing phase, Three types of testing will be conducted 1. System Testing 2. Integration Testing 3. Unit Testing Object Oriented Software Testing: Using Object Oriented design or design along with Agile development methodology leads to Object Oriented Software Testing. Object Oriented testing is done having emphasis on Composition.
  • This Document Explains the Various Benefits That Would Accrue to a User Or Client Who Subscribes to Autorabit

    This Document Explains the Various Benefits That Would Accrue to a User Or Client Who Subscribes to Autorabit

    ® Salesforce Release Automation BENEFITS DOCUMENT This document explains the Various Benefits that would accrue to a user or client who subscribes to AutoRABIT. [email protected] www.autorabit.com Copyright © 2016 AutoRABIT. AutoRABIT Table of Contents About AutoRABIT.............................................................................................................................................................3 AutoRABIT functionality..................................................................................................................................................3 Key Features of AutoRABIT............................................................................................................................................4 Metadata Deployment.....................................................................................................................................................4 Promotion of Builds .........................................................................................................................................................4 Full Deployment..........................................................................................................................................................4 Selective Deployment................................................................................................................................................4 Sandbox Back-up & Restore...........................................................................................................................................5
  • Marrying Devops and Test Automation

    Marrying Devops and Test Automation

    ARTICLE Marrying DevOps and Test Automation - a t t e n t i o n. a l w a y s. Is It The Right Thing To Do? Practice Head: Author: Janaki Jayachandran Sharon Paul Independent Testing Services Research Analyst We are all aware of the indifferences among the IT operations and other software development communities that prevail right from the traditional IT era. When developers, operations and testing teams work on different independent silos, focus on individual objectives and performance indicators, they fail to understand the importance of being accountable for any unplanned outages that causes production deployment failure and heavy loss to the company. There had to be a methodology or a practice that facilitated continuous improvement of the delivery cycles by enabling members across the IT and operations feel responsible and accountable for quality of their work. This thought gave rise to the concept of DevOps that fosters cross functional collaboration in order to speed up the delivery cycles through regular customer feedback. How DevOps Culture Impacts Product Quality? DevOps is simply an extension of agile methodology which became quite popular since 2009. It was the solution that resulted due to a series brainstorming sessions by few agile experts who wanted to end the dysfunction in the IT industry. The key reason for the dysfunction was found to be a lack of accountability in terms of quality among the different operations and IT team. Aspire Systems - Marrying DevOps and Test Automation - Is It The Right Thing To Do? 1 Marrying DevOps and Test Automation - Is It The Right Thing To Do? Elisabeth Hendrickson, founder of Quality Tree Software, presented an interesting paper, where she clearly cites a real life scenario of how developers develop a sense of negligence towards quality and they focus more on pushing their features into ‘test’ without taking an effort to evaluate them.
  • API Testing Guide an Automated Approach to API Testing Transformation

    API Testing Guide an Automated Approach to API Testing Transformation

    API Testing Guide An automated approach to API testing transformation. From Monolith to Microservice The consumerization of IT has changed the way we write applications today. Instead of building a single, monolithic system that is installed on a server in a back office or call center, modern When testing APIs, testers are faced with applications are scattered within mobile devices and web browsers numerous discrete units of work. Some so users can gain access to services at anytime from anywhere. of these APIs may have been created by a third party, while the possible And modern applications are no longer self-contained; they are ordering and combinations of different composed of multiple service components that are tied together versions of APIs can cause the number of at runtime. Therefore, the end-user experience is not powered by combinations that need to be tested to the elegant UIs we all use, but by APIs that facilitate interactions skyrocket to an impossible number. between code modules, applications and back-end IT systems. The ability to identify these combinations Because of this, the way we test must change. Quality assurance and then reduce them to a realistic (QA) and development teams must expand their capacity to test number without compromising quality each layer of the application, as well as the end-to-end business requires testers to adopt a transactions. Modern applications then require comprehensive API new model-based approach and invest in testing in addition to traditional UI testing. But API testing presents automation technologies. many challenges for testers. It requires a new approach—one that is automated wherever possible and inherently data-driven.
  • A Rapid Introduction to Rapid Software Testing

    A Rapid Introduction to Rapid Software Testing

    A Rapid Introduction to Rapid Software Testing James Bach, Satisfice, Inc. Michael Bolton, DevelopSense [email protected] [email protected] www.satisfice.com www.developsense.com +1 (360) 440‐1435 +1 (416) 656‐5160 Rapid Intro to Rapid Testing ‐ 1 Acknowledgements • James Bach, Michael Bolton, Huib Schoots, Paul Holland, and Griffin Jones co‐create and teach this class. • Some of this material was developed in collaboration with Cem Kaner. • Jon Bach has been a long‐term collaborator in developing ET management and training methods. • Lenore Bach (wife of James) maintains the emotional and home environment that motivated James and enabled him to create this. • Mary Alton, Michael’s wife does the same for him, while also contributing support for our Web sites and trying to lead us towards better visual design in our materials. If what you see doesn’t look good to you, it’s probably because Mary wasn’t involved. • Many of the ideas in this presentation were also inspired by or augmented by other colleagues including Doug Hoffman, Bret Pettichord, Brian Marick, Dave Gelperin, Elisabeth Hendrickson, Jerry Weinberg, Noel Nyman, and Mary Alton. • Some of our exercises were introduced to us by Payson Hall, Ross Collard, James Lyndsay, Dave Smith, Earl Everett, Brian Marick, and Joe McMahon. • Many ideas were improved by students who took earlier versions of the class going back to 1995. Rapid Intro to Rapid Testing ‐ 2 1 Assumptions About You • You test software, or any other complex human creation. • You have at least some control over the design of your tests and some time to create new tests.
  • Devops & Software Development Tools

    Devops & Software Development Tools

    DevOps & Software Development Tools Competitive Landscape and Market Trends v2.3 – December 2018 Shea & Company DevOps & Software Development Tools Market Trends & Landscape The DevTools Market Has Reemerged ◼ Back in 2011, Marc Andreessen somewhat famously wrote “software is eating the world,” putting forward the belief we’re in the midst of a dramatic technological shift in which software-defined companies are poised to dominate large swathes of the economy. Over the intervening six years, accelerated by the cloud and a growing comfort with outsourcing human activates to machines, software has become ubiquitous. With examples like Amazon displacing traditional retailers or a proprietary “Today's large John Deere tractors have application for player evaluation named “Carmine” helping to lead the Boston Red Sox more lines of code than early space to three titles since 2004, the power of software cannot be understated. shuttles.” Samuel Allen (CEO, Deere & Company) ◼ Software is not only disrupting business models in place for centuries (or 86 years of baseball futility), but it also is enabling incumbent vendors across disparate industries to improve product offerings, drive deeper engagement with customers and optimize selling and marketing efforts. Most industries (financial services, retail, entertainment, healthcare) and large organizations now derive a great deal of their competitive differentiation from software. As Andreessen wrote, “the days when a car aficionado could repair his or her own car are long past, due primarily to the high software “Software is like entropy. It is difficult to content.” grasp, weighs nothing and obeys the second law of thermodynamics; i.e., it ◼ But as software has brought benefits, it has also brought increasing demands for always increases.” business agility – and the software industry itself has been changed.
  • Automated Software Reliability Services Using Reliability Tools Should Be As Easy As Webmail

    Automated Software Reliability Services Using Reliability Tools Should Be As Easy As Webmail

    Automated Software Reliability Services Using Reliability Tools Should Be As Easy As Webmail George Candea, Stefan Bucur, Vitaly Chipounov, Vova Kuznetsov, Cristian Zamfir School of Computer and Communication Sciences École Polytechnique Fédérale de Lausanne (EPFL), Switzerland Software quality assurance (QA) is boring, resource- ware, without human involvement from the service user’s hungry, labor-intensive, takes a long time, and is prone to or provider’s side.1 AutoSRS combines the concept of re- human omission and error. While research has offered a liability tools as a competitive, simple web service, with wealth of new techniques, few made satisfactory progress doing automated testing and debugging in the cloud, thus in all these directions, so industry still relies on relatively harnessing vast, elastic resources toward making such au- primitive techniques for software testing and debugging. tomation practical for real software. AutoSRS consists of: Little has changed in QA practice over the last 20 years. 1. Programmer’s sidekick that continuously and thor- Studies have found bug density in production-ready oughly tests code as it is written, with no upfront in- software to be staying constant over time, while average vestment from the developer; code volume of software is increasing exponentially, with 2. Debugging service that turns bug reports into 100% the net effect that the number of bugs per product is in- deterministically replayable bug scenarios; creasing. It is therefore necessary to quickly find a “dis- 3. Home edition on-demand testing service for con- ruptive technology” to reduce bug density by at least 10×. sumers to verify the software they are about to install We see two key challenges: First, few of today’s tools on their PC, phone, TiVo, camera, etc.
  • Beginners Guide to Software Testing

    Beginners Guide to Software Testing

    Beginners Guide To Software Testing Beginners Guide To Software Testing - Padmini C Page 1 Beginners Guide To Software Testing Table of Contents: 1. Overview ........................................................................................................ 5 The Big Picture ............................................................................................... 5 What is software? Why should it be tested? ................................................. 6 What is Quality? How important is it? ........................................................... 6 What exactly does a software tester do? ...................................................... 7 What makes a good tester? ........................................................................... 8 Guidelines for new testers ............................................................................. 9 2. Introduction .................................................................................................. 11 Software Life Cycle ....................................................................................... 11 Various Life Cycle Models ............................................................................ 12 Software Testing Life Cycle .......................................................................... 13 What is a bug? Why do bugs occur? ............................................................ 15 Bug Life Cycle ............................................................................................... 16 Cost of fixing bugs .......................................................................................
  • The Value of Metadata- Driven Automation for the Modern Enterprise

    The Value of Metadata- Driven Automation for the Modern Enterprise

    Solution Brief: erwin Automation Framework The Value of Metadata- Driven Automation for the Modern Enterprise Automated, meta-data driven code generation for faster time-to-value in data preparation, deployment and governance The Automation Framework: Why It Matters Data governance is more important to the enterprise than ever before. It ensures everyone in the organisation can discover and analyse high-quality data to quickly deliver business value. It assists in successfully meeting increasingly strict compliance requirements, such as those in the General Data Protection Regulation (GDPR). And it provides a clear gauge on business performance. A mature and sustainable data governance initiative must include data integration. This often requires reconciling two groups of individuals within the organisation: 1) those who care about governance and the meaningful use of data and 2) those who care about getting and transforming the data from source to target for actionable insights. Both ends of the data value chain are covered when governance is coupled programmatically with IT’s integration practices. The tools and processes for this should automatically generate “pre-ETL” source-to-target mapping to minimise human errors that can occur while manually compiling and interpreting a multitude of Excel-based data mappings that exist across the organisation. That approach introduces errors that ultimately impact data quality. Additionally, the efficiencies gained through automation, including minimising rework, can help cut system development lifecycle costs in half. An automation framework sustains data governance and accelerates project delivery through comprehensive and automated code generation for data integration, transformation and movement. Data Governance and the System Development Lifecycle Boosting data governance maturity starts with a central metadata repository (data dictionary) for version- controlling metadata imported from a broad array of file and database types to inform data mappings.