With all the focus on Test practices and tools getting better for the present, it is easy to forget about the Future of Testing, especially in terms of Tools and Infrastructure? A question that always comes up in my mind - “Are we so caught up in the past and present, that we will not be as effective in the future?”

In this talk, we will go on a journey to figure out what new challenges are coming up in the future, and more importantly, what do we need to do next to prepare for it. Also, just preparing for the future is not sufficient. We have an opportunity to stretch beyond our current set of skills, capabilities and boundaries to influence out future! The question is - will we make use of this opportunity? 


Outline/Structure of the Talk

  • Skills & Capabilities required for being a good QA
  • Evolution and trends of hardware & software
  • Spatial operating systems / Sixth Sense - future or reality?
  • Which life are we living - Past, Present or Future?
  • Tips and Techniques to be innovative

Learning Outcome

  • Importance to be in-sync with what is coming up next
  • What does the future look like from Testing perspective? How can we influence it?
  • Tips and Techniques for being leaders, instead of followers

Target Audience

Testers, Developers, Managers, Innovators

schedule Submitted 4 years ago

Public Feedback

comment Suggest improvements to the Speaker
  • Fincy Yousuff
    By Fincy Yousuff  ~  3 years ago
    reply Reply

    Hello Anand!

    Brilliant topic and a well fitted title!

    However, I feel that it would be good if you specifically mention about how the situation currently is in the trenches within an Agile environment. What is the situation now? For eg - " with the current structure of agile, sometimes people get caught up with product shipment and finishing of iterations in the mentioned timeline that they forget about focusing about the quatlity of testing done on the product or the future of testing at this pace... " . At present I feel the details given are more generic.

    Also, it would be great if you could fill in more information about one of the Learning outcomes that you had mentioned - "Tips and techniques to be leaders rather than followers". If you could just direct me to the slide number, I'll grab a glimpse from there.

    • Anand Bagmar
      By Anand Bagmar  ~  4 years ago
      reply Reply

      Hi Fincy,

      Thank you for the kind words.

      Regarding some of your suggestions - For any team, Agile is not the end goal. Agile is a means, a state of mind, an approach ... and in most cases, a better means of getting the "right" thing done, in "good" time.  Likewise, in my talk, the topic is not necessarily about Agile - but how can we truly be "Agile" in creating our own path in the industry, instead of being followers. The learning outcomes from my talk are also on the similar lines. What I do for sure though - is if you are able to think in futuristic ways, then "being Agile" will help achieve that.

      Hope this clarifies your questions.


  • Liked Tony Xavier

    Tony Xavier - Challenges and Best Practices: Creating Customer Focused Documentation in an Agile Framework

    45 Mins

    Agile is an increasingly popular development method primarily used by software companies. In Agile software development, work is confined to a regular, repeatable work cycle, known as Sprint. A sprint typically lasts for two to three weeks. In Agile, development teams strive to deliver a fully functioning, high quality, and potentially shippable product increment at the end of each sprint. Hence, product documentation becomes an essential part of the sprint deliverable to meet stakeholder requirement. Since, the primary focus of Agile development is to deliver products with high quality, technical communicators are expected to create customer focused documentation with high quality.

    Creating Customer focused documents involves paying great attention to needs and opinions of customers, and creating documents with a purpose. As writers we must ensure that the documents we create focus on the needs of the actual customers of the document and provides value. As writers we must identify who the potential customer(s) for our documentation are, what they require, and create minimal documentation that they actually need. By understanding the needs of our customers we will be able to deliver customer focused documentation with high quality. However, the combination of Agile’s high speed of development, short delivery cycles, and limited requirements documentation presents a unique set of challenges in creating customer-focused documentation.

    This paper highlights some of the challenges writers face and provides best practices that can be used in creating customer-focused documentation in an Agile framework.