Agile-Scrum in QA – Case study at TraderToolsAgile-Scrum in QA – Case study at TraderTools

Amitay ItskovitchTraderTools LLCQA ManagerEmail: amitay@tradertools.comPhone: +972-9-7408880, ext. 107

2

Presentation OverviewPresentation Overview

• TraderTools – Streaming Executable Rates today

• Scrum Agile Methodology

• How TraderTools Integrated QA into Scrum Agile

3

Who are we?Who are we?

• The Company's STPlatform™ enables the streaming of executable rates

from multiple sources, enabling any bank, broker or financial institution to

become an electronic liquidity provider.

• TraderTools™ LLC (TraderTools) is one of the world's leading suppliers of

electronic Foreign Exchange (eFX) white-label, software solutions.

4

5

Current Methodology – V Model / Water FallCurrent Methodology – V Model / Water Fall

• Pros:

– Clear process

– Clear division for responsibility

– sets of requirements are predefined

• Cons:

– Not flexible :

• Change requests in last minute

• Bugs in UAT

– Full cycles when finding Bugs

– Risks at the end of the process – new system

– Less time for QA

6

Presentation OverviewPresentation Overview

• TraderTools – Streaming Executable Rates today

• Scrum Agile Methodology

• How we in TraderTools Integrated QA into Scrum Agile

7

What is Agile?What is Agile?

• Mini Projects

• Iterations

– Each iteration is an entire software project: including planning,

requirements analysis, design, coding, testing, and documentation

• Dynamic

• Flexible

8

Scrum-Agile ElementsScrum-Agile Elements

• Time box

Limited time of 30 days for Specification Reviews, Coding and Testing

Date Driven!

• Sprints

Each month there is new sprint , the contents are from the product backlogs

(list of requirements)

• Drops

Each sprint will contain X number of drops (mini pieces of the module /

function ) for testing

• Backlog – Product Backlog – list of required features– Development Backlog - sprint scope, updated every day

Scrum-Agile Elements (2)Scrum-Agile Elements (2)

10

Team members

• Responding reliably to change instead of conforming to plan

• The team is making decisions instead of taking instructions

• More individual responsibility and Self management

• Collective responsibility

Scrum-Agile Elements (3)Scrum-Agile Elements (3)

11

Scrum-Agile Elements (4)Scrum-Agile Elements (4)

• Daily Scrum Meetings

– Daily 15 minutes15 minutes status meeting

– Same place and timeSame place and time everyday

– No discussionsNo discussions

– Keep chickens QUIETchickens QUIET

– Three questions:

• Things I have done since yesterday’s meeting

• Things I am going to get done today

• Obstacles that I need someone to remove

12

The full Process CycleThe full Process Cycle

13

Presentation OverviewPresentation Overview

• TraderTools – Streaming Executable Rates today

• Scrum Agile Methodology

• How TraderTools Integrated QA into Scrum Agile

14

Facing the Agile Challenges in QAFacing the Agile Challenges in QA

• Change tests methodology: Move from V- model to Scrum

• no chronological order

• Requirements are not finalized

• No customer

• Hard to plan test scenarios

15

Sprints 1-2Sprints 1-2

16

Lessons Learnt – Sprints 1-2Lessons Learnt – Sprints 1-2

• If you can’t test it don’t deliver it!!!

• QA wasn’t part of the sprint !

• Dev had to take their own time to adjust

• Ad hock Dev time re-evaluations and extensions

• Not enough time for QA

• No time for Dev to fix bugs (only blockers)

17

Sprints 3-4Sprints 3-4

18

Lessons Learnt – Sprints 3-4Lessons Learnt – Sprints 3-4

• Not enough time for QA

– write the docs took too much time

– do we need complete docs?

• QA overload – still single person

• No time for dev to fix bugs (only blockers)

– MUST assign time for bug fixes

• Timing of sprints and drops

• QA Backlog

19

Sprint 5Sprint 5

20

Lessons Learnt – Sprint 5Lessons Learnt – Sprint 5

• Sprint final delivery (2nd drop) to QA should equal delivery to

customer

• QA write only Test cases

• Start work with drops

• Bugs from drop 1 aren't to be fix till drop 2

• 2nd drop for QA should be finalized (requirements and code)

21

More ConclusionsMore Conclusions

• Do we need STP/STD?

– No requirements

– Takes too much time

• Better define and clarify Dev 2 QA

– Insist on Dev performing unit/integration tests

• Be part of the team: P.R. QA

• Lot of automation

– Nightly builds

22

AdvantagesAdvantages

• To product - stability

• To Developers – understand the requirements

• To QA – better knowledge of the product

• Flexible /Dynamic

• Clear state of code

• Quality: finding issues at the beginning

23

DisadvantagesDisadvantages

• No final view

• Hard to implement

• Human perspective

• No Team Leaders

• Challenge in managing the product

24

SummarySummary

• It won’t reduce time of Dev/QA.

• It will increase the product stability.

• Discover major issues at early stages.

• It will increase confidence in the product .

• It will reduce customers dissatisfaction (no design issues).

THANK YOU!THANK YOU!

Any questions?Any questions?Agile-Scrum in QA – Case study at TraderToolsAgile-Scrum in QA – Case study at TraderTools

Amitay ItskovitchTraderTools LLCQA ManagerEmail: amitay@tradertools.comPhone: +972-9-7408880, ext. 107