Essential building blocks of a lean and efficient test process


Published on

Lean and efficient test process framework (TestSmart)

1.Provide quality gates across the Application Lifecycle to prevent the problems faced currently
2.Incrementally builds the missing requirements and test cases
3.Improved defect containment resulting in increased customer satisfaction
4.Reduces overheads and consequently cycle time

Published in: Business, Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Essential building blocks of a lean and efficient test process

  1. 1. © 2013. Maveric Systems LimitedHari Babu TPrincipal, Test Process ConsultingEssential Building Blocksof a Lean & Efficient TestProcessThis presentation and supporting material is owned by Maveric Systems and is for sole use of intended audience only.The presentation may contain content that is confidential or proprietary and may not be distributed or copied without the permission of Maveric Systems.
  2. 2. © 2013. Maveric Systems Limited 2Testing ChallengesSolution to these ChallengesBuilding Blocks of a Lean & Efficient Test ProcessSummaryAgenda
  3. 3. © 2013. Maveric Systems Limited 3ChallengesTesting Challenges▸ Large number of applications in production▸ Lack of test case definitions/obsolete test case definitions for applicationsin production▸ Large number of Change Requests, Enhancements & Production issueresolutions incorporated into applications in production▸ Lack of requirements definitions for applications in production▸ Multiple levels of testing with either overlapping or missing testing coverage▸ Inadequate impact analysis▸ Absence of regression test packs based on impact▸ Up gradation or Replacement of application is required every few years▸ Cumbersome paperwork/Non-integrated tool set
  4. 4. © 2013. Maveric Systems Limited 4AgendaTesting ChallengesSolution to these ChallengesBuilding Blocks of a Lean & Efficient Test ProcessSummary
  5. 5. © 2013. Maveric Systems Limited 5MTS – Solution to ChallengesSolutionLean and efficient test process framework (TestSmart)▸ Provide quality gates across the Application Lifecycle to prevent the problemsfaced currently▸ Incrementally builds the missing requirements and test cases▸ Improved defect containment resulting in increased customer satisfaction▸ Reduces overheads and consequently cycle time
  6. 6. © 2013. Maveric Systems Limited 6AgendaTesting ChallengesSolution to these ChallengesBuilding Blocks of a Lean & Efficient Test ProcessSummary
  7. 7. © 2013. Maveric Systems Limited 7Single Stage ToolAided DesignTest CubeNotationOrganizationLevel TestStrategyIntegratedtoolsetRequirementsTaxonomyDefine and use“Build Quality”MetricsTest Organizationaligned with teststrategyConfigurationManagementacrossApplication LifeCycleBuilding Blocks of aLean & Efficient TestProcessBuilding Blocks of a Lean andEfficient Test Process
  8. 8. © 2013. Maveric Systems Limited 8Test Organizationaligned with teststrategyBuilding Blocks of a Lean andEfficient Test ProcessDefine and use“Build Quality”MetricsConfigurationManagement acrossApplication LifeCycleOrganization LevelTest StrategyBuilding Blocks of aLean & Efficient TestProcessRequirementsTaxonomyIntegrated toolset Test Cube NotationSingle Stage ToolAided Design
  9. 9. © 2013. Maveric Systems Limited 9Organization Level Test Strategy▸ Lack of clarity on the levels, typesof testing that are to be performedby the vendor/development andtesting teams▸ Majority of the defects aredetected at the UAT stage▸ Test effort is not used optimally orcompromised under pressureWhy needed?▸ Clear identification of test levelsand types applicable and theresponsibility for each of them▸ Applicability of the various testtypes based on size, impact andcriticality of the feature beingchanged▸ Coverage type and coveragerequirements for each test level areidentifiedWhat is addressed?
  10. 10. © 2013. Maveric Systems Limited 10Test Organization Aligned withTest Strategy▸ Testers are not assigned to beresponsible for a test type▸ Testers do not have the requiredskill set for the assignedtest typeWhy needed?▸ Testers perform the intended testtype▸ Testers skills are assessed andimproved based on the test type▸ Better quality of testingWhat is addressed?
  11. 11. © 2013. Maveric Systems Limited 11Requirements Taxonomy▸ Requirements are documented inword documents and not in aparticular order▸ Difficult to extract, updaterequirements and build traceability(bidirectional and requirementstraceability)Why needed?▸ Requirements, Test Cases, Defectsand Incidents are organized basedon the Requirements taxonomy▸ Facilitates easy traceability,storage, retrieval and maintenance▸ Requirements and test cases areupdated on the existing baselineand rebase lined (not to beduplicated)What is addressed?
  12. 12. © 2013. Maveric Systems Limited 12Single Stage Tool Aided Design▸ Very little understanding of formaltest design techniques▸ Difficult to gauge the quality andcoverage of manual test design▸ Multiple levels of test designresulting in redundant work anddifficult to maintain artifactsWhy needed?▸ Quality and coverage is assuredand consistent▸ Test Design effort can be reducedby upto 50% (over the applicationslife span)▸ Unified framework for test casedocumentation▸ Significant reduction of test casemaintenance effortWhat is addressed?
  13. 13. © 2013. Maveric Systems Limited 13Test Cube Notation▸ No defined approach to develop,use and manage test sets▸ Testers consider the test set as aproduct which arises automaticallywhen specifying test cases▸ Switch from “Project” to “BAU”mode and vice versa resulting indiscrepancy between theapplication & the test setWhy needed?▸ Specify test cases & execute testcases on the basis of prioritizing▸ Report progress of testspecification and/or test executionquickly and adequately▸ Plan and estimate test projectsaccurately▸ Compose regression test setsquickly and flexibly▸ Incorporate changes of the testobject easily in the test setWhat is addressed?
  14. 14. © 2013. Maveric Systems Limited 14Integration of Toolset▸ Mostly standalone tools used forIncident Management, ChangeManagement, ConfigurationManagement and TestManagement▸ Toolset is incorrectly configuredcorrectly▸ No roadmap for toolset▸ Same data replicated in multiplesystems with inconsistent dataWhy needed?▸ Single stage data entry▸ Reduction of data inconsistencies▸ Better traceability and MIS▸ Reduced documentation overheadsWhat is addressed?
  15. 15. © 2013. Maveric Systems Limited 15Improved ConfigurationManagement▸ Traceability missing betweenobjects tested and objects movedto production▸ Requirements/Test set not underconfiguration managementresulting in test set becomingquickly obsolete▸ Test environments not underconfiguration managementresulting in inconsistenciesbetween production and testenvironmentsWhy needed?▸ Clear identification of baselines▸ Build numbers used as a basis totrack the movement of test objectsbetween development  testing production environments▸ Anytime availability of the latest/previous baseline requirements/test set▸ Clear traceability to the testenvironment used reducingenvironment related issuesWhat is addressed?
  16. 16. © 2013. Maveric Systems Limited 16Define and Use “Build Quality”Metrics▸ No mechanism to gauge the qualityof the builds being provided bydevelopment/vendor▸ Pressure on the organizationsbusiness and testing teams toensure timely release to productionleading to a number ofrequirements/defect fixes beingdeferredWhy needed?▸ A transparent mechanism tomeasure the quality of the builds▸ Development contracts aremanaged better resulting indecreased need to defer defectsWhat is addressed?
  17. 17. © 2013. Maveric Systems Limited 17AgendaTesting ChallengesSolution to these ChallengesBuilding Blocks of a Lean & Efficient Test ProcessSummary
  18. 18. © 2013. Maveric Systems Limited 18SummaryHow TestSmart maps to lean principlesOrgLevelTestStrategyTestOrganizationalignedtoteststrategyRequirementsTaxonomySingleStageToolAidedDesignTestCubeNotationIntegratedtoolsetConfigurationMgmt.acrossapplicationlifecycleDefineanduse“BuildQuality”MetricsEliminate waste  Amplify learning  Decide as late aspossible Deliver as fast aspossible  Empower the team  Build integrity in   See the whole 
  19. 19. © 2013. Maveric Systems LimitedThank