Presentation is loading. Please wait.

Presentation is loading. Please wait.

Why change, Why agile? Background to the Leading Enterprise Agile Programme (LEAP)

Similar presentations


Presentation on theme: "Why change, Why agile? Background to the Leading Enterprise Agile Programme (LEAP)"— Presentation transcript:

0 Evolution of Test Services to Quality Assurance Practice
Schroders Enterprise Agile Transformation Melinda Chapple, Head of Global Quality Assurance 25th May 2017

1 Why change, Why agile? Background to the Leading Enterprise Agile Programme (LEAP)

2 Overview of LEAP LEAP The Drivers Why LEAP? What was LEAP?
LEAP was the response to a demand for a more efficient & effective Global Technology (GT) capability - Business value must be delivered sooner - Cost effectiveness is paramount - GT alignment with the Business is critical to success What was LEAP? LEAP was a Programme focused on - Speed: Implementing enterprise Agile - Value: Product / Service Operating Model - Engagement: Changing how Business & GT interact LEAP When was LEAP? LEAP commenced in Q1 16 & was run in three month cycles or Planning Increments (PI) - Formal Programme ran through to Q1 2017 - Transformation self-sufficient from Q2 2017 - Programme was implemented using the SAFe framework Status of LEAP? LEAP completed its fourth (and final) PI in April 17, we are now in BAU mode - Delivered in 2016: Investment, Corporate Finance, HR, Fund Services, Distribution and Digital delivery teams transformed to Schroders Agile Methodology. - Delivered in Q1 2017: Data ART, Digital ART, Product ART & independent Portfolio Services agile teams

3 LEAP transformation complete 2017
Overview of LEAP Our journey to Agile It’s time to transform Schroders Global Technology 1 WHY Delivered through three key initiatives 2 WHAT Implemented using an Agile approach 3 HOW Benefits are well documented 4 BENEFITS The new (Agile) ways of working will be different 5 LEAP transformation complete 2017 IMPACTS

4 The Evolution to Quality Assurance Practice
Test Services response to Agile

5 Quality Assurance vs Testing
Creating a common understanding Quality Assurance is the maintenance of a desired level of quality in a service or product, especially by means of attention to every stage of the process from Planning to Run Quality Assurance is about the refinement of both the process and the product VS. Software testing is an investigation conducted to provide Stakeholders with information about the quality of the product or service under test Testing is about proving the product meets requirements

6 Global Quality Assurance Practice
Introduction The Global Quality Assurance Practice was created as a response to the LEAP Programme with the key aims: Improved quality and speed end-to-end: Work with Teams & Practices to implement continuous integration, test and delivery of code/products to Users in two weekly intervals Quality Mind-set: work with Agile Teams to develop quality into their way of thinking, their processes and their product Quality is not an act, it is a habit (Aristotle)

7 Global Quality Assurance Practice
Three Pillars People and Services Tools & Governance Community of Practice QA Coaches Engage with Agile teams to promote best practices across the change lifecycle Provision of training to teams or individuals Provision of Test Management capabilities across ART’s QA Engineers QA Engineers embedded into Agile teams & supported by the Practice QA Engineers provided to teams upon request to deal with spike activity Services Provide and maintain QA environments Training to Agile teams (automation, tooling, best practices, frameworks) Continuous improvement pathways Aligns tools and use cases to ensure the best fit Promotes Shift left automation Creation of foundational Best Practices that can be adopted by Agile teams Ensures the scalability of all automated solutions Ensure there are foundational best practices that Implements continuous improvements through information gathered from Agile teams Making connections between members; ensuring the topics are relevant & valuable Group discovers value in exchanges of knowledge and information. The value can be enhanced by engaging in experiences external to the office environment To share knowledge and promote learning within the specialist area in a way that is accessible to all members of the organisation

8 Global Quality Assurance Practice
Interactions with Agile teams New to Agile or Newly formed team Agile Maturity - medium Agile Maturity - high QA Interactions: QA Engineer is an embedded role within the Agile team with a focus on test automation QA Practice in collaboration with the Agile team works to iteratively improve quality QA Practice works with team to identify where efficiencies can be made (eg: opportunity for automation, provisioning of environments) QA Interactions: QA Engineer is transitioning out as a specific role and all team members have the mind-set and skills to perform test execution and/or…… QA Engineer is embedded in the Agile team with a focus on specialist non-functional testing QA Practice continues working with the team in a coaching & governance role QA Interactions: Light touch: coaching, governance & communities as needed ** This is where we have our biggest opportunities to collaborate & innovate **

9 Global Quality Assurance Practice
What we wanted to achieve An environment that facilitates fast feedback loops between team members & teams High levels of automation left to right, including Business Process testing Quality is embedded as a mind-set, therefore its embedded into the delivered product Agile Teams with T-Shaped team members, who deliver as a team To offer specialised Test Services that are difficult to accommodate within sprints

10 The Evolution to Quality Assurance Practice
Evolving our team members

11 The journey of our team From waterfall analyst to Agile team member 1
Creation of new roles aligned to the Capabilities of the Practice 1 LEADERSHIP Test Analysts & Test Managers converted to new roles 2 TEAM MEMBERS Intensive Training programme for all team members 3 TRAINING Embedded QA Engineers in teams 4 ROLLOUT Provision of Tools, Environments & Governance 5 SUPPORT Evolution Continues

12 The journey of our team The challenges & benefits INITIAL CHALLENGES
Team members did not want to convert to Agile ways of working Capacity management: LEAP Transformation, QA Transformation, Stakeholder Change, Keeping up with the demand from Agile Teams for people & services Education around what QA is and isn’t FADING CHALLENGES Breaking down the traditional barriers that exist in Agile Teams (Dev/Test) Breaking free from the “waterfall” reputation Making distributed teams work Teams maturing at different rates BENEFITS Morale within the QA Practice are high QA Engineers are up/cross skilling Teams are now focussing on automation Collaboration is high The importance of quality is being understood and embraced

13 The journey of our team Key to our success
Implementing training programmes Investing in Change Management activities Mentoring team members Forming strong relationships with other “enabler teams” Published End State of Quality Assurance Practice Enabling teams to be self sufficient

14 Quality Assurance Practice
Concluding Messages

15 Conclusion Key Takeaways What would we do differently
Implementation of automation tools and training Include a proposal for environment provisioning Include a solution for Test Data management capabilities Benefits of Transformation Team members are more engaged We have attracted new talent into our Practice Testing is shifting left Agile Teams are actively look for guidance on Best Practices, Automation and Training Change is being delivered to our Business communities in an expedited manner

16

17 QA Financial Forum Singapore
Melinda has over 25 years’ experience in technology change, with 17 years specialising in software testing and quality assurance within the finance domain. Melinda is a highly motivated individual who is passionate about the evolution of software testing in today’s Agile environment. Melinda has extensive experience in managing and delivering large scale testing programmes, and has worked across UK, Europe, AsiaPac – bringing a global perspective to change programmes. In her current position as Head of Global Quality Assurance at Schroders Investment Managers, Melinda has played a key role in the adoption and implementation of Agile across Global Technology and the wider organisation. A key part of that transformation was ensuring that test services evolved with the development teams; transitioning from a provider of people to a Quality Assurance Practice that supports Agile and DevOps principles Melinda Chapple Head of Global Quality Assurance

18 Melinda Chapple Head of Global Quality Assurance T M Schroder Investment Management Limited, CapitaGreen, 138 Market Street, Singapore. schroders.com


Download ppt "Why change, Why agile? Background to the Leading Enterprise Agile Programme (LEAP)"

Similar presentations


Ads by Google