1. Copyright BSPIN 2009 1 Agile Practices Benchmarking Case Study by Mazataz – Tesco

2. Copyright BSPIN 2009 2 About Organization -Tesco General Organizational Information Captive / Non Captive Captive About Business Products/Services Major Verticals Groceries, consumer goods, financial services, telecoms Number of Employees 500,000 Quality/Process Models embraced Agile – Scrum/XP Others 1 Others 2 Contact for this Presentation mjan@mazataz.com

3. Copyright BSPIN 2009 3 Agile Penetration @ Organization Agile Related Information Type of Project (please elaborate) ATG ecommerce implementation. Re- platform website, in-store and customer services. Domains Retail Ecommerce Technologies ATG, Java. Practices Behavior Driven Development (BDD), TDD Agile Institutionalized since 2010 Key success factor 1 Rolled out TDD & BDD to few Engineering teams Key success factor 2 Enabled Continuous Delivery Key success factor 3

4. Copyright BSPIN 2009 4 Agile Execution @ Project A Project NameCustomer Service Center – Returns/Replacements Project Size 50 Project Structure Various Scrum teams spread across UK and India(Bangalore, Hyderabad). Agile Approach SCRUM, TDD, BDD Agile Practices Spike solution, Sprint, Standup meeting, continuous integration, Automated Testing, code refactoring, design refactoring Agile Metrics Product velocity, burn down, various levels of Automation ( Smoke Tests, Sanity Tests, Functional Tests) Agile Tools Scrum Works, Jbehave(BDD), Mockito (TDD), Hudson (CI), Rally. Agile Skills TDD, Story Breakdown, Scrum Planning Why Agile in this project Business Feedback, Reliable Delivery

5. Copyright BSPIN 2009 5 Behavior Driven Development It is an evolution of  Test Driven Development (TDD)  Acceptance Test Driven Development (ATDD). It makes TDD and ATDD easy for new comers and experts

6. Copyright BSPIN 2009 6  Created small vertical stories of business value.  Agreed & documented business rules.  Agreed & documented the behavior.  Agreed how story would be accepted.  Created executable scenarios for each behavior.  Given, When and Then.  Verified it by the stake holders and rest of the teams.  Developed the behavior and verified the scenarios.  Show & Tell of completed scenarios to Truth.  Reacted to feedback.  Accepted story’s scenario added to regression suite. How we did it

7. Copyright BSPIN 2009 7 The BDD Framework

8. Copyright BSPIN 2009 8  BDD simplified functional testing.  BDD also simplifies JUnit testing.  JUnit is testing java components at the unit level.  JUnit verifies components behavior without deployments.  It does not need any dependencies to be available. Tools used : Mockito The JUnit Framework

9. Copyright BSPIN 2009 9  Enables creation of Mock objects, verification of behavior and stubbing.  Provides BDD style structure.  Enables testing of unit level components.  Like Server side components, Database components etc..  Mock all objects that a component uses and verifies its use according to specified behavior. Why Mockito

10. Copyright BSPIN 2009 10 The Big picture – what we achieved

11. Copyright BSPIN 2009 11 Significant Benefits  Focused on development and delivery of prioritised, verifiable business stories.  Focused on providing a common vocabulary that bridges the gap between business and technology.  Focuses on exposing business rules to review by stake holders and Testing Teams.  Encourages collaboration between developers, testers, architects, BA ’ s and Business.  Made it easy to Automate End to End functional testing.  Simplified Test Driven Development.  All integrated well on Continuous Integration  The Business where satisfied to see the status of project.

12. Copyright BSPIN 2009 12  Due to time constraints we could not automate all scenarios.  Due to Infrastructure limitations could not run automated regression suite on every check-in.  Due to time constraints not all teams followed TDD.  Some legacy application testing could not be fully automated.  Not all teams where empowered to take decision of TDD.  Given tight deadlines the some teams abandoned TDD. Limitations

13. Copyright BSPIN 2009 13  More stake holder involvements in defining test scenarios.  More encouragement from management to engineering to adopt TDD/BDD.  To user business friendly tools like Fitnesse or Cucumber.  Invest in CI infrastructure to run automated regression suite on every check in. Recommendations

14. Copyright BSPIN 2009 14 Thank You