How do we get earlier involved as testers - horizontal and vertical Ole Chr. Hansen Managing Consultant September 4th, 2014
Who am I? Ole Chr. Hansen Managing Consultant, Sogeti Danmark A/S Fellow, SogetiLabs Global Innovation Network Blog: www.ochansen.blogspot.dk LinkedIn: www.linkedin.com/in/ochansen Twitter: www.twitter.com/ole_chr_hansen ISTQB Accredited Trainer in Software Testing ISEB Practitioner Certificate in Software Testing ISTQB Foundation Certificate in Software Testing TMap NEXT Test Engineer Certified TPI NEXT Foundation Certified PRINCE2 Foundation Certified Certified Scrum Master Certified Lead Assessor (ISO 9000) Sogeti, ATP, Nordea, BRFkredit, WM-data, CRI, LEC Test Manager (15+ years), Project Manager (10+ years) Mail: ole.hansen@sogeti.dk Mobile: +45 52 18 94 59 2
35 / 30 Years Ago English - 1979 Danish - 1984 Good condition for software testing in Denmark or..? 3
Degree of Involvement Global vs Denmark Source: Sogeti Global TPI Benchmark Source: Sogeti Denmark TPI Benchmark 4
Involvement Statement Outside the project Inside the project (value chain) 5
Involvement Statement Tight involvement of testing in the project helps to improve the product quality from the beginning, and helps to keep test activities off the projects s critical path. 6
Involvement Statement 7
Result Risk Time Cost The key to success is balance 8
Bridging the Communication Gap 9
Tester Language Management Language Tester Language Management Language 10
Testing is not an Island 11
Testing is not an Island Testing has many stakeholders. Inside (horizontal) and outside (vertical) the project. 12
For Whom Do We Test? Stakeholder Analysis Fellow testers Test leads and managers Developers, development leads and managers Database and system architects Marketing and business analysis Project managers Technical support and help desk staff Sales managers, engineers and staff Executives, officers, ministers and/or directors Company shareholders Elected officials and voters Regulators and law enforcement Users Vendors Customers and sponsors Public and society 13
Stakeholder Management The tester knows the stakeholders and their objectives and expectations for testing. The tester works with the stakeholders to ensure realistic objectives and expectations, and define metrics to measure effectiveness and efficiency. 14
Stakeholder Management Stakeholders objectives (examples) Reliable and secure IT-systems Effective automated solutions Improve costs efficiency of IT Shorten time-to-market Improve transparency and understanding of IT. Know them understand them 15
How to benefit from involvement of testers The test assignment, scope and approach are negotiated early with the principal stakeholder as one of the first test activities. Test activities are started early, timely before test execution, with the goal of keeping the test activities off the project s critical path. A tester is involved in project planning, and dependencies between the test process and other processes are taken into account. A tester is involved in the analysis and mitigation of overall projects risks. 16
How to benefit from involvement of testers Testers contribute to impact and risk analysis of change requests and changes to the test basis. Testers contributes to the impact analysis of defects. Testers are actively involved in optimizing the test basis (more than a testability review), in which the object under test is described. The test team is involved in the evaluation of the project. The lessons learned from the test process are valued and used for future projects. 17
Show it Give value for money and show it 18
Showing Benefit Case Study Life & Pension Industry Statement from chairperson of Steering Commitee: You have to test all combinations within the timebox of 15 working days Me: 6.720 combinations each 2 hours = 13.440 hours 15 days / 7 hours pr. day = 105 hours 128 FTE Chairperson: What you are kidding me - right? Me: No Chairperson: Can you do something? Me: Combinatorial test techniques pairwise: 38 triple wise: 178 356 hours 4 FTE Chairperson: Great Risk? Benefit: Save testing time and resources - 128 4 = 124 FTE Risks: Limited (Source: NIST) 19
Visibility Be visible to your stakeholders 20
Reporting Risk Wheel 21
Result Risk Time Cost The key to success is balance 22
Conclusions Know your stakeholders and their objectives Be visible to the stakeholders Be pro-active to the stakeholders Show the benefits of involving testers Train the managers in tester language Train the testers in management language Give value for money and show it 23
Questions Ole Chr. Hansen Managing Consultant ole.hansen@sogeti.dk +45 52 18 94 59 24