Shift Left Principle – Key enabler for First Time Right Dr Ramesh K Tumuluru 10 June 2013 TCS Public
Structure 1 Context Setting 2 Shift Left – What is it? 3 How to make it Work ? 4 Case Study - 2 - 10 June 2013
Context Setting 10 June 2013 3
Triple Constraint Large Programs Iron Triangle / Triple Constraint 10 June 2013
Common Symptoms Poor Quality Test Coverage Deliverables Gap Delivery Slippage Inadequate Effort Requirements Requirements Slippage Slippage Infrastructure Issues Cost Overruns Performance Many CRs Issues - 5 - 10 June 2013 5
Some metrics Standish Group Report …. The bigger they are the harder they fail………. McKinsey Quarterly Report 10 June 2013 6
Factors Contributing to Failure Standish Group Report …. Unfortunately there are no SILVER BULLETS….. 10 June 2013
Complexity “…. No one thing seems to cause the difficulty – any particular paw can be pulled away. But the accumulation of simultaneous and interacting factors brings slower and slower motion… ” The Mythical Man-Month Frederick P Brooks 10 June 2013
Shift Left Principle - ? 10 June 2013 9
Shift Left Principle SHIFT LEFT IS MUCH MORE THAN A PROCESS Or A TOOL IT IS ALL ABOUT MINDSET SHIFT 10 June 2013
Perception about a Tester ��������������������� ������������������ �������� ������ ��������� ������� ���������� ������������� ���� ����� ������������ �������������� ��������� ��� ���������� 10 June 2013 11
Software Development Life Cycle (SDLC) Requirements Review Requirement Test Strategy Analysis Define Test Strategy ent Management Define Detailed Test Plan Design Test Planning t Management Create Test Scenarios Create Test Cases / Scripts Development Development Test Design Test Design Developme Test Create Test Data Run Test Cases Raise Defects Testing Test Execution Re Test fixes Test Summary Report Production Test Completion Defect Summary Report Waterfall Model 10 June 2013
How does this model work in reality • Generally the testing team will NOT be part of requirements phase • After the requirements phase is signed off, the test lead or test manager will pick up the document and produce Test Strategy document • The testing team is ramped up much later in the cycle • They independently validate requirements and perhaps identify gaps, which might be too late in the life cycle and therefore make assumptions • The testing & development teams will work independently especially the test design phase and build phase respectively, with their own interpretation of requirement • After the requirements are provided by Business or Users, they come back only during UAT, which might be almost one year later 10 June 2013
Outcome of this model • Gaps in the requirements found during testing • Test coverage is inadequate • Multiple defects and multiple CRs raised during user acceptance testing • Due to timeline pressure most of the CRs have to be completed within the original schedule • • Work extra hours ……so on and so forth….. Work extra hours ……so on and so forth….. 10 June 2013
Outcome of this model Inadequate understanding of requirements Go Live Test Date Coverage Fixes Acceptance Test Execution from Client timelines timelines Defects in UAT Resources & Effort New CRs Availability of Controlled Additional Environment Test Cases …. Problem becomes bigger and bigger….. 10 June 2013 15
What is Shift Left principle ��������������������� ����������������������� ���������������!�����"������������ ���������������!�����"������������������ ���#�����"������$ ���������"���$�$� ����%�&��������� "�������"������ ����� ������������������ ���������������������������������������� ������������ '��������������"'�����"������� ������������ '��������������"'�����"������� ������"'�(�#����'�������)"������*������� ���������� …. Validation & Verification….. 10 June 2013
What is Shift Left principle ��������������������� ����������������������� ������������������������������������������� +�!��������,���������� �������������������� ������������-������������������� +�!�������.�����&���������������!�������� ���������� !""!�#$%! ��� +�!�������.��� !""!�#$%!&!�� ������������"�� +�!��������,������������� ���� ����� ������ �!�������(�#� +�!�������.�������������������� '&�!(�#)&� +�!�������.�������������������� '&�!(�#)&� �������������&��������� +�!�������.������������������� ��*�(!�!&�$%! �����������"� +�!���� )�$�& .��������������"�!������������� ������" +�!�������.���� ������� ���!�(!%$!+� Shift left is all about MINDSET Shift 10 June 2013
What is Shift Left principle SHIFT LEFT Requirement Analysis Test Strategy Design Test Plan Development Test Design Unit Testing Test Execution The lesser the Total Internal Refection Angle the greater the ALLIGNMENT The lesser the Total Internal Refection Angle the greater the ALLIGNMENT 10 June 2013
Shift Left Principle Requirements Review Joint Test Coverage Early Involvement of User Matrix TIME TO MKT QUALITY COST COST Early Interface Design & Testing Code Reviews Unit Test Reviews Enables high First Time Right in client’s testing 10 June 2013
Shift Left Principle SHIFT LEFT IS ALL ABOUT MINDSET SHIFT Shift Left principle enables close collaboration with Business, Developers and Testers DURING THE EARLY STAGES of development life cycle to ensure that we are building the RIGHT thing and also building the thing RIGHT . 10 June 2013
What do we need to make Shift Left happen? 10 June 2013 21
7 S model of Shift Left Structure Shared Systems Values Mind Set Strategy Style Staff Skills Mind Set is the corner stone of Shift Left Principle - 22 - 10 June 2013
Test Design Process 7 S model 1 Strategy � While constructing the test strategy there should be fundamental mindset change in terms of how can the testing add value prior to system testing phase . We need to come with up a different set of metrics to measure the alignment 2 Structure � The Test Delivery Manager should be part of core management team and should have a say in the program and it should be an independent team 3 Systems � The processes should be modified to accommodate workshops with internal and external stakeholders after the requirements phase, design reviews and code reviews � Test design phase templates should be simplified to accommodate changes in requirements 4 Skill � The testing team should understand the overall solution and should have business knowledge � The testing team should have technical skills for Unit Testing review, and to do design reviews � The testers should be techno-functional 10 June 2013
Case Study 10 June 2013 24
Program Product Driven Scope was Solution very BIG Multi Services Multiple Geographical Locations Outsourced First Time interaction interaction with 3 rd Party SYSTEM Regimented systems Contractual Obligations Urgency to Go Live Different Time Zones Requirements Evolved No baseline business Lean processes Organization 10 June 2013
Hardship First Release • Functionality 52 FSDs • % of T Ss Used 50+ • % of TCs Used 40+ • Total Effort X person months • Total Defects in UAT Huge • Total Defects in UAT Huge 10 June 2013
Recommend
More recommend