Testing That Adds Value

Welcome to SIGiST Israel
International Testing Week 2014


  • Welcome Words
  • About Us
  • Organizing Team

Dear SIGiST Israel Members, Colleagues, Professionals, Ladies And Gentlemen.

Following a successful conference in 2013, I am proud to introduce to you a new event that SIGiST Israel is initiating from 2014, which is the International Testing Week 2014. We are bringing you speakers from all over the world, covering hot topics in testing today, with seminars that will enable you to get the knowledge and know-how on those topics. Some of the seminars are with hands-on exercises using laptops/PC, while others include important knowledge and methodology/processes/cognitive tools for you to use.

This year, starting the event for the first time, I invited two known speakers: Lloyd, from UK, whom you know from 2 years ago, coming with two great topics: Exploratory testing and Estimation and Dashboards. Also coming Leo Van der Aalst, from Netherlands, with additional great topics: Agile testing and Business Driven Test Management.
I hope you will find these topics relevant for you currently, or preparing you for future implementation of those topics within your companies.
I would like to wish us all a great event. Come to participate in the seminars and most importantly – take advantage of the networking with other colleagues and fellow professionals.

I encourage you to register to the event today and enjoy the benefits of the registration discounts (see registration form). For members, you may enjoy the membership discounts on top of that as well. The registration form with the seminars is provided as well, for you to choose from.


Alon Linetzki
SIGiST Israel Chairman | alonl@sigist.org.il

The SIGiST Israel Story - The Israeli Testing Forum

SIGiST Israel was founded in June 2000, by Mr. Alon Linetzki, and was self-sponsored, for the first few meetings. Today, after many meetings [out of which several events were sponsored by RadView, Rational (IBM) and Mercury (HP-Software)], SIGiST Israel is the official and largest professional testing community forum in the Israeli market.
The SIGiST board includes Mr. Alon Linetzki, founder and managing director Best-Testing, as SIGiST Chair and Mr. Yan Baron, Test Manager, Aternity.
Since 2005, SIGiST Israel has joined up with two main partners: the ITCB (Israeli Testing Certification Board) – on the professional aspects, and with SELA College and technology center on the business aspects.

SIGiST Israel meets every quarter; meetings are usually sponsored by testing companies, testing services companies and testing tool vendors. Once a year, SIGiST Israel is conducting its yearly conference, and invites international speakers and Israeli testing community speakers to discuss hot testing topics. The conference is being held in its current format (4-5 days), since 2006.

SIGIST Israel purpose and goals are to create a place where testing professionals can meet, speak on common issues, suggest solutions to common problems, and be a place where they can come up with a request for an answer, and get it! It aims to be the driving force and the trigger for recognition of the testing profession in Israel and is working to increase the awareness toward certification for the different levels of testing (using the ISTQB® certification scheme).

SIGiST Israel is the strongest testing forum in the Israeli testing community, and the largest (payable) conference of the testing community, committed to bring the best knowledge on testing world-wide and to cooperate with: other SIGiST boards, conferences organizers worldwide, and professional testing associations - to achieve its goals.

We Are Happy To Present SIGiST Israel International Testing Week 2014 Organizing Team, That Is Working To Make This Event Possible:

Alon Linetzki, SIGiST Israel Chair
Sigal Garusi, Marketing, Coordination & Logistics Supervisor Lead
Merav Di Capua, Registration Team Lead
Avi Drucker, Technical Supervisor Lead
Ortal Levi, Production, Logistics & Administration
Sveta Kaplan, Graphical Design & Media Lead


For Conference and Seminar registration, please fill up the registration form and fax it back to the number inside the form.
For further information, fill up the contact us below and SEND it to us.
* Name:
* Company:
   Job Title:
* Phone:
* Email:
* Message:

Seminars (Will be held at: Sela House, 14 Baruch Hirsh, Benei-Brak)

click for more info Leo Van der Aalst
18 March, 2014
Business Driven Test Management
Seminar Description

Often, test strategies, plans and reports fail to appeal to the client. The reason is that testers still tend to reason from the perspective of IT. Too often the test process has an inward focus and is rife with test and IT jargon, making it difficult to communicate with non-IT clients such as users while clear communication is of utmost importance.
Clients language
The Business Driven Test Management approach devotes explicit attention to communication by speaking the 'language' of the client. When formulating the assignment and writing the various reports, for instance, the 'language' of the client himself is used instead of the jargon. BDTM's starting point is that the selected test approach should enable the client to manage the test process based on the BDTM aspects of result, risk, time and cost. As a consequence, testing becomes more business focussed. The information that is necessary to achieve this is delivered by the test process.
BDTM advantages

The advantages of the BDTM approach are as follows:

  • The test process is transparent to the client and the client can control the test process on the basis of all of the BDTM aspects.
  • The test manager communicates and reports using the terminology of the client, with information that is makes sense in the client's context. For example by reporting on the basis of the BDTM aspects and in terms of test goals realised, rather than combinations of object parts and characteristics or numbers of defects.
  • The master test plan can be as detailed as desired or possible; this may mean that less effort is required to do a product risk analysis or formulate a test strategy for the separate test levels, or even to skip these steps altogether.
Purpose of testing
If we are to understand the BDTM approach correctly, it is important, to keep in mind at all times the final purpose of testing - i.e. giving a quality assessment and risk advice with respect to a system. Since it is impossible to test everything, an adequate assessment can only be achieved by dividing the test effort, in terms of time and money, as adequately as possible over the parts and characteristics of the system to be tested. The steps of BDTM aim to achieve this.
Practical case studies will ensure that the Test Manager can perform all steps in the BDTM process independently
The workshop "Business Driven Test Management' focuses on the execution of a large number of cases. Each case is preceded by a brief theoretical explanation. After the workshop, the participants understand why certain steps in the BDTM process are performed and how they can steer on the various BDTM aspects. In the end the participant will be able to execute all steps in the process BDTM independently.

During the workshop, all steps in the BDTM process will be addressed:
  • Establishing the assignment and collecting test goals
    The client formulates the assignment, taking account of the four BDTM aspects: result, risk, time and cost. Establishing the test goals aims to determine what, in the eyes of the client, are the desired results of the testing activities. A test goal is a success criterion for the test assignment specified in the client's language.
    The result of this step is the formulation of the assignment and a test goal table.
  • Determining the risk class
    Based on a product risk analysis, it is established what must be tested (test goals) and what must be examined (characteristics). The risk class related to the combination of test goal and the relevant characteristic. If multiple test levels are involved, the test levels that must be set up are determined in a plan that covers all test levels (the Master Test Plan). The test strategy also defines, for each combination of a test goal/characteristic, an indication of the relative intensity of testing in a specific test level.
    This step results in a risk table.

What follows is an iterative process - formulating the test strategy:

Determining the test intensity
Deciding whether a combination of test goal and characteristic must be tested lightly, moderately or intensively. This is called the test intensity. The risk class for each test goal as defined in the previous step is used as a starting point to determine the test intensity. The initial principle followed here is: the greater the risk, the more thorough the required testing.
Estimation, planning and feedback
An overall budget is established for the test, which is plotted in a planning. This is agreed with the client and other stakeholders and, depending on their views, adjusted if necessary. In the latter case, steps 3 and 4 are repeated. This gives the client emphatic control of the test process, enabling him to manage it on the basis of the balance between result and risk versus time and cost.

End of iteration

These steps result in a strategy table.

  • Allocating test design techniques
    If the client and other stakeholders agree to the budget and planning, the test intensity is translated into concrete statements regarding the desired coverage. This involves allocating test design techniques to the combinations of test goal and characteristic, taking account of circumstances such as the available test basis. The techniques are used to design the test cases at a later stage.
    This step results in a test design table for each test level.
  • Providing insight and control options
    Throughout the test process, the test manager provides the client and other stakeholders with adequate insight into and control options for the IT Governance aspects:
    Result:  the test goals achieved
    Risk:     the risks covered
    Time:    whether the end date - or deadline - is realised
    Cost:    whether the test project remains within the agreed budget.

Target audience

This workshop is intended for anyone involved in setting up and running of (large) test projects. We think Test Managers, Senior Test Coordinators, Test Consultants, Test Project Managers, QA Managers and IT Managers who want to develop themselves in the testing profession.


Basic knowledge of the testing process is assumed. Furthermore, the participants are expected to have experience with testing and experience in leading (test) projects. Moreover, we assume that the participants possess analytical skills and ability to abstract.
click for more info Lloyd Roden
18 March, 2014
Exploratory Testing

Exploratory Testing Workshop


This 1-day workshop is aimed at those wanting to understand this approach to testing, how to apply this to projects and how to manage exploratory testing sessions.
The workshop aims to dispel any misunderstandings people might have with this approach and how it can be applied to both traditional and agile projects.

Applications are provided throughout the workshop. However, increased benefit can be achieved from this workshop if your own application can be accessed and tested during the session. 

Individual, Paired and Team Exploratory Testing will be explained and tried during the workshop. Every exploratory testing session will include a debrief to determine the quality of the applications under test together with the quality of the testing performed.

Since this is the main approach used within an Agile project, this will be discussed at length as to how Exploratory Testing can be more effective and efficient.

1 day


QA Staff, Test Analysts, Senior Test Analysts, Developers and anyone who wants to understand the concepts of Exploratory Testing

• Understanding what Exploratory Testing is and what it is not
• Generation of Exploratory Testing charters
• Performing individual, paired and team exploratory testing sessions
• How to report to management regarding progress during Exploratory Testing

Course Outline
Morning (1): Key concepts of Exploratory Testing
Morning (2): Performing individual Exploratory Testing using charters
Afternoon (1): Performing paired Exploratory Testing
Afternoon (2): Performing team Exploratory Testing and reporting
click for more info Leo Van der Aalst
19-20 March, 2014
Agile Testing in Practice

Workshop Agile testing in practice

Seminar Description:

Agile Testing: flexibility by structure
Agile methods are becoming increasingly popular. In an agile environment an information system is delivered incrementally and in short cycles in close collaboration with the customer. In this way, organizations can release their information system into production more quickly, without reduction of the quality. In addition, changes can be integrated seamlessly during the development process. Although it seems contradictory, structure and discipline are required to ensure such flexibility. During the workshop Agile Testing in Practice you will learn how to effectively test in an agile environment and what skills are required. Furthermore, you get practical tips how you can design agile testing in your own practice correctly.

Flexibility and discipline are essential skills
One of the features of the agile method is that changes during the development can be integrated seamlessly. However, this is not a license for an unorganized project. In agile projects structure and discipline make the required flexibility possible. Because too much structure brakes the project, it is important that you find the right balance between flexibility and structure. The success of an agile project also depends on the consensus between the team members on the selected practices. Agreements on the structured testing method and way of working are very important. During this workshop you will learn how to use your testing skills in order to achieve such consensus and effective collaboration.

Grip on your own agile testing process
Many organizations that use an agile method are losing their grip on the testing process. During this workshop you will learn how to use structure and discipline to keep a grip on your agile testing process. You will discover how to integrate agile testing into your own agile practice. You will also learn how to keep control of the testing process without the flexibility of the agile process is lost.

Risk poker
The development team estimates, often with the aid of planning poker, the amount of time required for each task of a sprint backlog. The amount of time required is influenced by factors such as whether the test has to be thorough or light, which, in turn, is related to the product risk. Therefore, it is advisable to include the risk classification of a backlog item — particularly in the case of user stories — in addition to the priority specified by the product owner, before the planning poker is initiated. In this workshop you will learn how to apply risk poker as an aid to determine the product risks.

Structured exploratory testing in an agile environment
Exploratory testing is a testing technique much used in agile environments. It appears if "structured" and "exploratory testing" contradict each other. A good agile tester does, however, have a certain degree of structure in exploratory testing. During this workshop you will learn how you can apply a structured way of exploratory testing. In addition, you will learn when you can use exploratory testing, and when it is better to use another test technique.

Experience the agile effectiveness by doing
A standard training often does not reflect the current work and thinking of the team members of the agile team. During this workshop theory and interactive assignments therefore alternate as much as possible. Among others, the following topics are discussed:

• Introduction agile.
• Scrum:
  1. Sprint Planning.
  2. Risk Poker.
  3. Planning Poker.
  4. Daily Scrum.
  5. Sprint Review (Demo).
  6. Sprint Retrospective.
• Agile Testing:
  1. The role of the Agile Tester.
  2. The role of the Test Manager.
  3. Test Strategy and Product Risk Analysis.
  4. Test Documentation.
  5. Evaluation of User Stories.
  6. Exploratory testing.
  7. Agile testing process.
• Team composition and location.
• Test automation.

Target audience
This workshop is intended for Testers, Test Coordinators and Test Managers testing who (are going to) perform testing activities in an agile environment and who want to deploy their testing skills effectively in this environment. In addition, this program is suitable for agile team members, Scrum Masters and anyone interested in testing activities in an agile environment.

The workshop is designed for individuals with at least one year of testing experience. Knowledge of a structured test method as TMap NEXT® or ISTQB® is a plus.

click for more info Lloyd Roden
19-20 March, 2014
Test estimation and Dashboards

Test Estimation and Dashboard Workshop

This 2-day workshop is aimed at those wanting to understand the key principles of test estimation and reporting. Test Estimation is one of the hardest activities to do well in testing, the main reason is that testing is not an independent activity and often has destabilising dependencies. During this workshop we shall uncover some of the common problems in test estimation, how to overcome them together with 8 ways we can estimate test effort.

Gathering and presenting clear information about quality—both product and process— may be the most important part of the test manager's job.

Join Lloyd Roden as he challenges your current progress reports—probably full of lots of difficult-to-understand numbers—and asks you to replace the reports with a custom Test Manager's Dashboard containing a series of graphs and charts with clear visual displays.

Both estimation and dashboards will be discussed at length as to how these apply to an agile project and how they differ.

2 day


QA Staff, Test Managers, Test Team Leaders, Test Coordinators and anyone wanting to understand and master the principles of test estimation and reporting

• Uncover the common problems/destabilising dependencies in test estimation and how to overcome these
• How to communicate test estimation with senior management and how to appreciate their perspective making us even more effective when it comes to estimating our test effort.
• Discover 8 powerful ways to estimate test effort; some relatively easy methods and some more detailed and complex methods
• Learn how appropriate each method is to the various lifecycles (traditional, iterative and agile)
• This session will also discuss various issues that arise in the initial phases of test estimation and how the test manager/tester can negate these issues
• Understand the difference between monitoring and control and how good monitoring techniques can lead to effective and timely control
• Discover 8 powerful ways to monitor progress and how to represent these on a dashboard
• Learn the art of prediction which is essential for all Test Managers and how to do this with confidence and ease
• Learn how to tailor your dashboard so that it is accurate and relevant to the person receiving the information

Course Outline
Day 1

Having been a test manager for nearly 12 years, test estimation was one of the hardest things to do well. This workshop is based upon experience (usually painful) and research. It uncovers some of the common destabilising dependencies we encounter during test estimation such as quality of the code or quantity of the code being delivered. We shall look at how different methods of estimating are appropriate to the various lifecycles we find ourselves in (Sequential, Incremental and Iterative).
We shall look at 8 powerful ways to estimate test effort, some being easy and quick but prone to abuse. And others being more detailed and complex but taking longer to administer.
Various Estimation Methods:

• FIA (Finger in the Air)
• Formula or Percentage
• Historical
• Consensus and planning poker
• Work Breakdown Structures
• 3 point estimation
• Estimation Models
• Assessment Estimation

We shall also look at how we can approach the "authorised deadlines" that are often presented to us. Spreadsheets and utilities will be given out during this workshop to help the tester and the test manager. It is hoped that by the end of this session people will feel that the painful experience of test estimation could in fact become a more pleasurable experience.

Day 2

Your dashboard needs to report quality and progress status that is accurate, useful, easily understood, predictive, and relevant. Learn about Lloyd's favourite dashboard graphs—test efficiency, risk progress, quality targets, and specific measures of the test team's well being.

Learn to correlate and interpret the various types of dashboard data to reveal the complete picture of the project and test progress. By creating a Test Manager's Dashboard, you will provide significant long-term benefits to both the test team and the organization—and make your job easier and more fulfilling.
During the workshop a series of tools and utilities will be demonstrated and provided for the participants to help them produce the information needed for the intended recipient. Learn how to correlate graphs and interpret the results correctly.

Speakers (Click picture to open biography)


Leo Van der Aalst
Leo Van der Aalst
Leo van der Aalst has more than 25 years of testing experience. He is experienced in international – consultancy – projects and developed amongst others services for agile testing and the implementation of test organizations.

Leo is lector "Software Quality and Testing" at Fontys University of Applied Sciences (Eindhoven, The Netherlands) and he is a co-author of the "TMap NEXT® in Scrum", the "TMap NEXT® for result-driven testing" and "TMap NEXT® Business Driven Test Management" books.

He is also a member of the Dutch Country Board of ISO/NC 381007 "Software and System Engineering", member of the Research & Development unit of Sogeti Netherlands and Development Lead of the ISTQB® Foundation Level Agile Tester Extension Syllabus. 

Finally, Leo is a much sought-after teacher of international test training courses, a regular speaker at national and international conferences, and he is the author of several articles (a.o. testing in agile software development environments and software testing as a service – STaaS)
Lloyd Roden
Lloyd Roden
With more than twenty-eight years in the software industry, I have worked as a Developer, Test Analyst and Test Manager for a variety of different organisations. From 1999 to 2011 I worked as a consultant/partner within Grove Consultants. In 2011 I set up Lloyd Roden Consultancy, an independent training and consultancy company specialising in software testing.

My passion is to enthuse, excite and inspire people in the area of software testing and I have enjoyed opportunities to speak at various conferences throughout the world including STAREAST, STARWEST, EuroSTAR, AsiaSTAR, Belgium Testing Days and Better Software as well as Special Interest Groups in software testing in several countries.

I was privileged to be Programme Chair for both the tenth and eleventh EuroSTAR conferences and won the European Testing Excellence award in 2004.

My Values

I believe that any work that I do, whether it be in the form of consultancy or training, must be relevant, practical and must make a difference to the individual as well as the organisation. It is important to me that people not only enjoy the courses that I run but they improve their skills in software testing which will ultimately reflect on the improved quality of the products being delivered by the organisation.

I also aim to be at the leading-edge of latest ideas and methodologies within the IT industry so as to remain relevant and real in what I deliver in the testing community.

Contact Us

Registration Center:

Merav Di Capua:
Tel: +972-(0)3-6176066,   Email: merav@sigist.org.il,   Fax: +972-(0)3-6176677