Agile-Scrum in QA – Case study at TraderTools Amitay Itskovitch TraderTools LLC QA Manager Phone: +972-9-7408880,

Slides:



Advertisements
Similar presentations
Project Name Kelly Waters July Author: Date: Version:
Advertisements

Keith McMillan Principal, Adept Technologies Copyright (C) 2008, Adept Technologies llc.
Project Management with VIVA PPM Tool (Project Portfolio Management)
Iterative Development: Done Simply Emily Lynema NCSU Libraries Code4Lib 2010.
Web Development Engineering Processes Introduction to Web Development Outsourcing Processes.
Delivering Enterprise Projects Using Agile Methods Brent Barton May 23, 2006.
Software development process improvement Ville Wettenhovi Master thesis presentation Supervisor:Professor Jukka Manner Instructor:M.Sc. Markus Aalto Date:23th.
PROC-1 3. Software Process. PROC-2 What’s a process? Set of activities in creating software It involves creativity –hard to automate –Requires human judgment.
Lena Bigelow Business 550 Presentation SCRUM. -A project management process - Embraces iterative and incremental practices -Concentrates on what is important:
ITEC 370 Lecture 24 Lifecycles. Review Questions? –Grades for Requirements/Design Doc F give prototype demonstration –Testing plan for your software Maintenance.
Agile on Board or How We Do It at Intel Artem Fedko Copyright © 2013 Intel Corporation. All rights reserved Intel are trademark of Intel Corporation in.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
C O N F I D E N T I A L 4-May-15 1 Attendee Management - Being Agile Attendee Management.
Clinton Keith CTO, High Moon Studios Agile Methodology in Game Development: Year 3.
Intro to Scrum. What is Scrum? An answer to traditional “fixed cost / strict requirements” contracts which had very high rates of failure Recognizes the.
NAUG NAUG Knowledge Evening – th February 2007.
Agile development By Sam Chamberlain. First a bit of history..
Improving Process for Better Software. Who We Are An experiential learning program that provides technology solutions for our partners, and real- world.
The Product Owner prioritizes the requirements or features through feedback from the Stakeholders & interaction with the core team The Team.
Agile/Scrum Case study Code name: ninja.  2 scrum teams  One product backlog  8 months so far  Long term project  External integrations  R&D and.
PopMedNet Software Development Life Cycle Chayim Herzig-Marx Harvard Pilgrim Health Care Institute Daniel Dee Lincoln Peak Partners.
1 Waterfall/Scrum You might want to take notes, because specific aspects of the processes will be on the exam. Combining – A scrum with water…
Trusted IT Group. The challenge: 40 active, concurrent IT projects  Unsatisfactory Project Delivery.
Software Development Landscape
CSE G674/2009 Project Project Management Section Presented by: Amir Aref Adib.
Agile Assimilation & Scaling. 2  About me…  How did we start?  Bottom-up  Task Force  Learning  Pilots  First stage analysis + recommendations.
Agile Software Development Brian Link
Resource Systems.  The need for agility  History of Product Development  Delivery of EPCOT  Future Challenges & Recommendations  Reflection  Questions?
Current Trends in Systems Develpment
Alcatel-Lucent CDC Workshop, Coaching & Knowledge Transfer Project Management.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
SCRUM introduction 6 April Scrum Team are known as pigs because they’re committed to delivering Sprint Goal People who are involved but not dedicated.
Creating a Brand New Project using Scrum and Agile Techniques Matt Turner, Mark Wightman Red Gate Software.
Real World Software Development Management and Solutions Joel Semeniuk April 5, 2011.
4/23/ :45 PM © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered.
(A radical interpretation) Tomo Lennox Bow Tie computer services Why Agile Works.
Software Project Management Team 04 – K15T2. Content Summarizing your view on “Software development process”. Answer 3 question: ◦ What is Software Development.
Establishing an Agile Testing Team: Our Four Favorite “Mistakes” Kay Johansen Anthony Perkins.
Scrum Santhosh Srinivasan. Outline What is Scrum What is Scrum Why Scrum Why Scrum Scrum Practices Scrum Practices Why Scrum works Why Scrum works Pros.
With a hint of HP Quality Center Agile development and functional testing: friend or foe? Tom Vercauteren, June 26th, 2009.
Team Assignment 3 Team 4 – K15T2 Present. Introduce to project Goal of project Profitable for Honda Vietnam Company. Improved working process. Increases.
Theories of Agile, Fails of Security Daniel Liber CyberArk.
WATERFALL DEVELOPMENT MODEL. Waterfall model is LINEAR development lifecycle. This means each phase must be completed before moving onto the next!!! WHAT.
CS223: Software Engineering Lecture 5: Software Development Models.
It’s tough out there … Software delivery challenges.
Team Assignment 3 Team 4 – K15T2 Present. Introduce to project Goal of project Profitable for Honda Vietnam Company. Improved working process. Increases.
PV213 EIS in Practice: 06 – Development process 1 PV213 Enterprise Information Systems in Practice 06 – Development process.
Agenda: Overview of Agile testing Difference between Agile and traditional Methodology Agile Development Methodologies Extreme Programming Test Driven.
WHEN TITLE IS NOT A QUESTION N O ‘WE CAN’ CA Agile Vision Product Manager Michael Lester.
Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Contact US: ID: Phone Number:
 Son Nguyen, YM & Skype: ng_thanhson.
Agile CRM Applying the Scrum Methodology for Deployment Neil Benson.
#msdevcon Community Track IMPLEMENTATION OF SCRUM Bernardin Katić Insa Investment Software AG.
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Agile development: a PM’s perspective
Embedded Systems Software Engineering
Software Development.
Agile Methodology and Scrum
Wael Ellithy, Ph.D. Arx ICT
Valuable Project Management Tools and Techniques
Владимир Гусаров Директор R&D, Dell Visual Studio ALM MVP ALM Ranger
Agile Software Development Brian Moseley.
Teaching slides Chapter 1.
SUCCESS MANTRAS FOR BEING AN EFFECTIVE INFORMATION DEVELOPER IN AGILE
Agile Process: Overview
Introduction If you have got a call for an Agile testing interview, then congratulations are in order. You may be feeling nervous, but it sure to be felt.
Agile, Scrum and CMMI Methodologies
Presentation transcript:

Agile-Scrum in QA – Case study at TraderTools Amitay Itskovitch TraderTools LLC QA Manager Phone: , ext. 107

2 Presentation Overview TraderTools – Streaming Executable Rates today Scrum Agile Methodology How TraderTools Integrated QA into Scrum Agile

3 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 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 Overview TraderTools – Streaming Executable Rates today Scrum Agile Methodology How we in TraderTools Integrated QA into Scrum Agile

7 What is Agile? Mini Projects Iterations –Each iteration is an entire software project: including planning, requirements analysis, design, coding, testing, and documentationrequirements analysistesting Dynamic Flexible

8 Scrum-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)

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)

11 Scrum-Agile Elements (4) Daily Scrum Meetings 15 minutes –Daily 15 minutes status meeting –Same place and time –Same place and time everyday –No discussions chickens QUIET –Keep chickens 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 Cycle

13 Presentation Overview TraderTools – Streaming Executable Rates today Scrum Agile Methodology How TraderTools Integrated QA into Scrum Agile

14 Facing 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-2

16 Lessons 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-4

18 Lessons 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 5

20 Lessons 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 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 Advantages 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 Disadvantages No final view Hard to implement Human perspective No Team Leaders Challenge in managing the product

24 Summary 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! Any questions? Agile-Scrum in QA – Case study at TraderTools Amitay Itskovitch TraderTools LLC QA Manager Phone: , ext. 107