From my experience as a consultant working on various projects, I observed that application performance is often not treated as a first class citizen until just before release. 

How do you anticipate the number of people using your application at any point of time ? How would you handle a surge in the the user traffic ? How would you know the limits of your system just before it breaks down ? 

In a true agile environment, where the team believes in fast feedback and continuous quality delivery, we need to treat performance tests just like any other functional tests. In this talk I will be sharing my principles  and taking you through the various aspects the team may consider for the application's performance. 

To some capacity everyone can have valuable inputs to understand performance of the system. I am intending to keep this talk less technical so that people from various capabilities can join and get an insight. 

1 favorite thumb_down thumb_up 5 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/Structure of the Talk

I will be touching upon the following and how each of that can be applied in an agile environment. 

  • Introduction
  • Why performance testing
  • What is Load and stress testing
  • The agile way of performance testing
  • Frontend and Backend performance testing
  • Performance test pyramid
  • Environments
  • Data
  • Scripts
  • Tooling
  • Monitoring
  • Takeaways

Learning Outcome

The participants would take away:

  • Significance of performance testing
  • Things to consider for performance testing



Target Audience

Developers, testers, Operations, Product owners

schedule Submitted 2 years ago

Public Feedback

comment Suggest improvements to the Speaker
  • Tathagat Varma
    By Tathagat Varma  ~  2 years ago
    reply Reply

    Do you have your own real-life experience to corroborate your presentation? Practitioners at agile conferences often find it valuable when they can relate theoretical concepts to practical implementation experiences.

    • Srinivas Murty
      By Srinivas Murty  ~  2 years ago
      reply Reply

      Hi Tathagat, yes i do have examples at least from the past 3-4 recent projects that i worked on at various clients in the past few years. 

      my blog is just an inference from these examples. I have recorded most of the challenges that we faced in my personal diary which I can share during the presentation. 

      • Tathagat Varma
        By Tathagat Varma  ~  2 years ago
        reply Reply

        Sounds good. It would be great if you are able to talk about instances where an early PSR testing was able to highlight inadequacy of an implementation or its architecture, and how that early discovery led to rearchitecturing or refactoring decisions. Also, if you can address the relative efforts and ROIs to help the audience understand the tradeoffs involved for them to make a judicious decision about planning API-based early PSR testing in their cycle.

        • Srinivas Murty
          By Srinivas Murty  ~  2 years ago
          reply Reply

          It is possible to think about instances of how early performance testing / monitoring helped in making informed decisions. 

          I understand where you are coming from about efforts and ROIs. I know these conversations raise interest in senior stakeholders. This is a question that many clients want to talk about during our initial discussions with them. But when it comes to ROIs and putting down numbers, we tend to go into muddier areas as it is very subjective. From my personal experience I would try and avoid going down that route and keep it simple. 

          • Tathagat Varma
            By Tathagat Varma  ~  2 years ago
            reply Reply

            A method - any method for that matter - that doesn't make economic sense is likely to get lower attention, especially from the decision-makers. If you have any such data that supports how early testing has led to quantifiable gains to the overall objectives of the business, it will make upper management folks in the audience to be more interested in your session.