With the popularity of mobile devices consumers are able to access information anytime, anywhere using any digitally capable device. Not only that consumers expect a smooth and seamless experience across all possible channels information can be accessed through. Although availability of information via multi-channels is good for end users it can potentially have an adverse effect on quality assurance and testing teams. By surveying 1560 senior IT executives across 32 countries and receiving insights and analysis from numerous SME’s worldwide, the World Quality Report 2015 – 16, a global market research study from Capgemini, Sogeti and & HPE attempts to reveal answers to these important questions and provides valuable insights on today’s global testing landscape and trends of the future.

Coming Soon....

As the number of projects adopting agile practices has increased rapidly throughout Dell Software, there have been some challenges in terms of testing for these projects. Transitioning testers away from simply being test executors to becoming quality assistants throughout sprints required a framework reinforced by some practical steps – Lee decided to try the the Agile Testing Ecosystem (Bach/Bolton) as our way to do this and, in this case study, he will describe how this model has been introduced and some lessons learned in adopting it. Key takeaways: Testing is not just about "executing tests" In an agile team, a tester can be a very valuable asset, helping everyone in the team to understand what good testing looks like * By acting as a "quality assistant", testers can more easily show their value and gain more respect

Lee Hawkins is a Principal Test Architect for Dell Software. He is responsible for testing direction & strategy and is based in Melbourne, Australia. Lee has been in the IT industry since 1996 in both development and testing roles and his testing career really started in 2007 after attending Rapid Software Testing with Michael Bolton. When he is not testing

I would like to talk about:

1. Improving the effectiveness & efficiencies of testing team

2. Building automating capabilities

3. Getting the test team ready to support Agile development

User my time tested and proven approach including following initiations:

4. Forming Tester-Developer pair

5. Transforming testers into subject matter expert (SME)

6. Training and supporting testers to build Test Automation Framework using open source tools

7. Implementing a personal development plan for all test team members

8. Changing the management style to Situational Leadership (Ken Blanchard)

Passionate about improving software quality and user experience by implementing quality process, conducting end-to-end testing and communicating with stake holders

Skilled in:

Slicing heuristics are explicit policies that help teams "slice" work Just-In-Time for consistency, a shared language and better predictability.

Acceptance tests help us develop software incrementally and collaboratively to meet customer needs. By using acceptance tests as a basis for slicing, we can replace deterministic estimation rituals with valuable conversations about the software we are building, ensure every increment we deliver is complete and bug free, and use empirical measurement of actual cycle times to help product owners make forecasts and teams to improve their throughput of value.

This talk will equip teams and organisations who are established on their Agile journey with a robust, clear and repeatable method for improving the quality and time-to-market of their software development efforts.

Neil is a passionate Agile and Lean thinker, manager, coach, blogger (neilkillick.com), tweeter (@neil_killick) and international speaker.

He has been developing software professionally for over 19 years across a wide variety of roles and industries, in companies ranging in size from startup to large corporation. Neil is one of the early pioneers of the #NoEstimates movement and is the creator of the Slicing Heuristic method. He is an invited speaker at conferences worldwide including Dev Day Sri Lanka, Agile India, Agile Singapore, ScanAgile, Agile Australia, 1st Conf, DDD, SIGiST and LAST.

His mission is to help organisations become better at delivering software while creating more humane, happy workplaces. To achieve this, Neil focuses on providing the people doing the work with an environment which allows them to thrive.

For a long time we've struggled with testing in prod-like environments, where differences between test, staging and prod cause failures. Learn how Docker changes things by combining your application with its dependencies, providing you with the confidence that what you've tested is what gets deployed. Rethink your DevOps approach, throw out unnecessary tooling and automate your way to quicker feedback cycles and faster deployments.

James Holmes is an Senior Developer/Ops Lead at REA Group. He's Into Lean, Agile, DevOps, Kaizen, Kanban, Aikido, Kenjutsu and other Japanese words.

This session will briefly introduce the audience to exploratory testing and the power of such an approach. More significantly, we will present a real practitioners' perspective coupled with a couple of case studies where the speaker has himself led a team to leverage this approach for a $5Billion company.

Exploratory testing is gaining acceptance as a part of a broader “Agile Testing” skill set at a very past pace. As the agile movement sweeps through the world of software engineering, many traditional testing tasks e.g, automation of unit and functional tests, are increasingly being taken over by developers.

Testers, now have a big opportunity to use exploratory testing to raise the level of testing and therefore quality to the next level. Exploratory tests are more consistent with the spirit of Agile, just as 'scripted tests' are more consistent with a waterfall approach.

- It emphasizes the tester's autonomy, skill and creativity, much as other Agile practices emphasize these qualities in developers

- It recommends performing various test-related activities (such as test design, test execution, and interpretation of results) in an interleaved manner, throughout the project, rather than in a fixed sequence and at a particular "phase"

- It emphasizes the mutually supportive nature of these techniques, and the need for a plurality of testing approaches rather than a formal "test plan".

Ayush cut his teeth in management consulting with Ernst & Young, DC Strategy & in health insurance with Medibank Private, before diving head first into his entrepreneurial journey. He joined forces with Avaneesh Dubey, who spent 16 years at SAP and left after 4 years as the head of SAP's global testing team, where he innovated to reduce testing headcount from 600 to 250 and cycle times from 3 months to 6 weeks. Together they have reimagined how software testing should be performed and this led to the creation of the end-to-end Qsome enterprise software testing platform, which enables sharper, faster & smarter software testing.

Behaviour Driven Development aka BDD tests have come a long way. From being a buzzword at the conferences to becoming the de-facto way of writing tests. BDD tests act as a living documentation and provide tremendous value when done right. However, they can also become a significant bottleneck in smooth delivery of the software system if some of the anti patterns are allowed to creep in.

Thus, as part of this talk we would like to re-iterate the core principles of BDD and the best practices surrounding them. At the same time, we will discuss the common anti-patterns that are usually found in the BDD ecosystem, and more importantly how can we abstain from falling in those troughs.

An ardent advocate of quality first, Jatin enjoys creating beautiful software using lean and agile principles. Having worked for clients ranging from small start-ups to big enterprises, he has worked on a variety of domains including finance, telecom, retail, ecommerce, mobile and business consulting. He has been pivotal in helping teams adopt agile practices while baking quality in. Having worked in the testing space for several years, he appreciates participating in various stages of a project life cycle, juggling many hats, and is currently involved as a business analyst/ iteration manager on one of the product teams at MYOB. Before joining MYOB, he was working as a senior consultant at ThoughtWorks.

Priyanka is a test automation expert and has been working with agile teams for over 8 years. She strongly sponsors the idea of shifting quality to the left. She is passionate about finding better ways to write tests, creating scalable automation frameworks and identifying opportunities of continuous improvement. She has worked on an array of test automation tools including Specflow, JBehave, Selenium and QTP. Before joining MYOB as a senior QA on one of their flagship products, she worked for organisations such as Royal Bank of Scotland, Sapient and HCL technologies.

Quick delivery is a key aspect of an agile environment, and automation tests are a key aspect of quick delivery. Unfortunately when an automation test fails, there is a good chance the failure is due to a broken test script, rather than a broken build. When these tests fail the process of correcting them can be an expensive delay: the original build needs to complete, changes are reverted, scripts are update, changes are pushed and the build is started again. With some build systems this build process can take hours. So how can we minimise failures due to broken scripts? Adaptive Automation! Scripts that detect failures and employ intelligent techniques to recover and correct themselves.

Paul Crimmins is a context driven tester who is continually learning about the craft. He works at the Australian Health Practitioner Agency as a Team Lead. He is an aspiring leader who has been working in the test industry for almost ten years and co-authored an article, with Rajesh Mathur, called "The Thing Called Leadership".

Paul is a member of the Association for Software Testing and is an active assistant with the Test Engineering Alliance Melbourne (TEAM) meetup. His Twitter handle is @Paul_Crimmins.

Scott is an passionate automation expert who is always looking for new ways to improve automation frameworks. He has been working on improving the maintainability of test automation to allow testers more time performing sapient testing and less time correcting automated test scripts. He is currently working with Aconex, one of Melbourne's leading agile development houses and is an organiser of the Test Engineering Alliance of Melbourne.

DevOps as a culture and mindset has been around for quite some time now (since 2009), but in terms of the IT Industry it is still at a nascent stage and maturing gradually. In the Agile and Lean world a lot is spoken and discussed about on this new culture that DevOps is fostering; along with its use and usefulness to the IT Industry in general. If we ask people, we get varied answers on what they mean by DevOps - some interesting, some more out of a textbook. DevOps being a relatively young field, it’s definition has as yet not matured to be consistent across the IT Industry and the various Organizations which have started to develop the DevOps mindset. In a nutshell, the concept of DevOps came from the need to deliver a Project/Product inside a complex changing environment & requirements and to deliver it fast.

Today the DevOps culture is becoming an integrated approach along with Agile Software Testing, within the IT World; without each other neither can survive the vagaries of the newly fangled Projects coming out to bite the IT Industry, based on the timelines for delivery and the quality which needs to be maintained for large or small iterative Project lifecycles. In this paper, we plan to outline how Agile Testing practices and culture forms an inseparable bond with DevOps and how it has become an integral part of the Project lifecycle to deliver better quality products, with the mindset oriented towards Continuous Integration and Delivery (CI/CD).

Gagneet Singh has been working in the Quality Assurance/Test field for the past 11 years (with an additional 5+ years in System Tools development) and has been involved with companies such as Toshiba, Adobe (Macromedia), McAfee, Oracle, Yahoo!, Microsoft, NSW Govt. RMS and recently Tech Mahindra.

He likes to blog and to write about the experiences he faced in the various organizations and situations. His work has mostly been with Automation and Performance QA in Agile environments as also Security Testing over "Cloud Computing" (using Hadoop and Azure) has figured in his work area