Agile Maturity and the Quality custody-battle

Size: px

Start display at page:

Download "Agile Maturity and the Quality custody-battle"

Sheila Simmons
5 years ago
Views:

Agile Maturity and the Quality custody-battle SoftTest 2016 -

1 Agile Maturity and the Quality custody-battle SoftTest Adapting & Innovating for Change 13 th October th October 2016

2 How do we know we can Go Live? 2

3 HPE TSS R&D Overview Our Agile SAFE journey so far. How our QA transformation happened Introduction of System team Highs and Lows Any questions? 3

4 Technology Services Support R&D what are we? HPE Automation provides 24x7 coverage, proactive problem prevention, accurate problem diagnosis and faster problem resolution, as well as interactive support portals and tools Services and Support for all HPE and Multivendor purchases Simplified and standardized portfolio of support services across all technologies, offered uniformly in all geographies TSS R&D is chartered with automation of the delivery of Technology Services 4

Support Automation Solution Overview Information Harvesting Retrieves, encrypts and submits

Information Processing Receipt, processing, cleaning, normalizing & modeling of incoming

Contracts, Configuration, Product, Shipping, Partner, etc.

5 Support Automation Solution Overview Information Harvesting Retrieves, encrypts and submits relevant service information such as events & configuration from Customer Data Centers Information Processing Receipt, processing, cleaning, normalizing & modeling of incoming Customer Enterprise information Information Analysis Continuous and Time critical analysis such as Events, flooding, correlation, etc. Information Storage Single authoritative source for all normalized SA data including Events, Contracts, Configuration, Product, Shipping, Partner, etc. Reporting & Analytics Create Customer report deliverables Data Mining, Program & Quality reports Content Presentation Portals and/or Notifications presenting content, plus overall system Administration & User management

6 The Vision! 6

7 HPE TSS R&D Agile Transformation Timeline Before Agile 0-6 months 7-12 months Year 2 Present 400 R&D personnel 16 time zones Complex technology Silo d subsystems Immature Lifecycle development Lengthy time to market QA cycle Agile teams stood up Component team focussed Inconsistent application of requirements definition and tracking QA improvements but still lengthy Validation cycle Consolidation of teams by location Data driven approach tools and metrics Introduction of ARTs and formation of 20 scrum teams Focus on architectural backlog as well as feature delivery In-sprint QA and cleaner Validation cycle Teams structured by feature Maturation in use of tools including focus on Inspect & Adapt Adoption of program and portfolio layer in SAFE 645 R&D personnel 4 value streams with 7 ARTs (release trains) 11 ARTs in total 44 scrum teams Combination of Agile / Kanban in use Continuous Delivery model in place 7

9 QA drilldown Before Agile 0-6 months 7-12 months Year 2 Present Separate QA teams and activity executed after Development Late emergence of critical, high impact issues Paper / ceremony heavy change request process QA cycle duration anything between 6 months and 1 year QA resources assigned to scrum teams New functionality automated testing Existing functionality manual tests Teams commence training on various technologies Legacy Solution QA Validation Cycle 14 weeks In sprint resources working through new automation and automating existing manual tests being used Team established to automate the balance of legacy manual scripts (circa 3000) Legacy Solution QA Validation Cycle 6 weeks TecOps team established System team model trialled on one ART Performance Testing Framework (Elastic Search; Logstash; Kibana) Security Testing Framework Test Data Tool Test Automation Frameworks Selenium, Fitnesse Environment Mgt Legacy Solution integration / hardening cycle of 6 weeks between code freeze and go live (3 week sprints) System team per ART QA fully integrated with scrum teams and trains Continuous Delivery framework in place New architecture: Master always releasable Fully automated test suite Legacy solution integration / hardening cycle of 2 weeks between code freeze and golive (2 week sprints) 9

10 TSS R&D Pillars of Continuous-X Continuous Build & Integration Continuous Test Data Continuous Testing Continuous Deployment GHE GH Flow Unit Test Auto B&I Test Data Accp Test Auto Deploy Perf Test UAT ALM GitHub Webhooks WebInspect Agile Manager Infrastructure as a Service Container as a Service

11 Change Drivers Resources Communications Tools Quality Strategy Culture 11

12 Converting from Manual Testing to new world of Automated QA Delivery Framework SAFE overview Scrum Suggested readings blogs / books e.g. Agile Testing, The Phoenix Project Tools Basic or Advanced Java development Fitness Selenium Jenkins Ansible Github Application specific technology HP Agile Manager Leankit Soft Skills Communication skills Teamwork Project Management principles Leadership Conflict Management Alternative career paths SM, PO, etc. 12

13 Evolution of Team Structure Development Agile Release Train App1 App2 Dev QA Dev QA App3 App4 Dev QA Dev QA Agile Release Train Scrum 1 Scrum 2 Scrum 3 System Team QA Validation QA U.S. Galway India Functional Performance 13

14 More on the System Team The System Team is a special Agile Release Train team typically chartered to provide assistance in building and using the Agile development environment infrastructure including continuous integration, build environments, testing platforms and test automation frameworks as well as integrating code from Agile Teams, performing end-to-end system testing, and demonstrating solutions in the System Demo at the end of each iteration. Supports the teams and other stakeholders by providing quick feedback with respect to the efficacy and integrity of the evolving, end-to-end solution. The system team may also have a special role in assisting with each Release. However, these efforts should be shared between the system team and Agile teams; otherwise, the system team will become a bottleneck, and the Agile teams cannot be fully capable, or accountable, for real value delivery. 14

15 System Team Responsibilities Create and maintain infrastructure Create platforms and environments Automate deployment Facilitate collaboration with 3 rd parties for hosting, etc. Building Development Infrastructure System Integration Define branching models Run System level integration scripts Assist with inter-component interfaces Create automated test scenarios Take individual tests and collate them into an ordered suite Maintenance of tests NFR testing End-to-End and System Performance Testing System Demo Assure demo environment adequate Assist teams with ability to demonstrate solution 15

Challenging Areas ScrumFall Losing the Labels QA vs.

TecOps activities into an Agile Release Train with SAFE framework

Transitioning Resources Knowledge Sharing and Training Actual vs

16 Challenging Areas ScrumFall Losing the Labels QA vs. Development System Team establishment Pace of Change Trying to map TecOps activities into an Agile Release Train with SAFE framework What Went Well! Transitioning Resources Knowledge Sharing and Training Actual vs Plan results embedding QA in the planning process improved the accuracy of estimates Adoption of automated testing Employee Satisfaction 16

17 Final Message Take The Plunge! 17

18 Thank You! 18

A 7-STEP FRAMEWORK TO IMPLEMENT CICD IN ETL TESTING

VIEW POINT A 7-STEP FRAMEWORK TO IMPLEMENT CICD IN ETL TESTING Kiran Beemanakolly, Senior Project Manager, Infosys Limited Vasuki Rao, Technical Test Lead, Infosys Limited Abstract Organizations are increasingly