Data @ the core of Enterprise Agile

location_city Bengaluru schedule Mar 17th 04:45 - 05:30 PM place Grand Ballroom 1

Agile adopts an empirical approach to software development. One of the key aspects of a successful Agile Implementation is how quickly we can react to change. For this, we need to ensure that data flows seamlessly from customer to the Agile team. This data should form a critical part of our decision making.

  • Is the customer successful in using our product or service?
  • Which features are customer most interested in?
  • Where are the friction points in usage?
  • Where are the failures happening in our product?
  • How is the customer engaging with our product over time?

and many more similar questions.

In this talk, I discuss best practices in data collection, analysis and visualization and how data can make your Agile process and thereby your business more effective.


Outline/Structure of the Talk

  • Introduction to the data sources in Agile Software Development
  • Data Collection methodologies
  • Best practices in analyzing data
  • Visualization of data
  • Decision making from data
  • Data to Insights

Learning Outcome

  • Understand data collection methodologies
  • Effectively analyze & visualize data
  • Make better decisions using data
  • Apply machine learning to derive deeper insights from data

Target Audience

Developers, Leads, Managers

schedule Submitted 4 years ago

Public Feedback

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

    Mathew - can you pl respond back to the quesries by Venkat and Evan so that the program team can take a call on your proposal?

    • Mathew Aniyan
      By Mathew Aniyan  ~  4 years ago
      reply Reply



      I had earlier updated the proposal based on comments from Evan. Today, i have responded to Venkat's comments. Please let me know if there is any additional information needed.

  • Venkatraman L
    By Venkatraman L  ~  4 years ago
    reply Reply

    Dear Mathew,

    Thanks for the proposal. 

    At the first read of the proposal including the PPT, though I understand you want to focus on the "feedback through data and usage patterns", can you help with more info 

    1. What will be the basis of this presentation. Would you be taking an example from your current work, product etc, to show how the data provided the insights finally ? 
    2. Will it be focused only on UI based products where customers can use and feel or is this more generic ? How about developing platforms (would it be through API calls etc) ? Would you be sharing those details too, to the audience ?
    3. I am presuming this can also be at team levels and not necessarily at enterprise levels. I mean, this can be used for any product development even at small and mid size teams. Please do clarify if so. 

    Would be nice if you can share more info about #1 above and possibe to update the deck accordingly, that would be great. 




    • Mathew Aniyan
      By Mathew Aniyan  ~  4 years ago
      reply Reply

      Venkat, Thanks for your feedback. Apologies for the delay in responding.


      1. I will be sharing examples from my current work. As part of the demos, i will showcase a relevant example from my current team.

      2. The model i am proposing will apply for any type of application. In my team, significant sections of this model have been built as a platform. I will share high level architecture as part of the talk.

      3. Absolutely. At a high level, this is a set of best practices which any team or product can adopt. The visualizations will differ based on the granularity at which we are analysing the data.

  • Evan Leybourn
    By Evan Leybourn  ~  4 years ago
    reply Reply

    Thanks for submitting the proposal. 

    Can you please update your proposal with the following...

    • Slides - Preferably an outline of this talk, but any similar presentation will do.
    • Videos Links - To some of your past presentations on this topic or any other. The video could be from other conferences, user group meetups or internal to your company. In case you don't have any; I suggest you shoot a short video presenting to the audience.
    • Blogs/Articles: Links to blogs or articles on this topic.

    The above will help you complete the proposals and also help the review panel. We can take it forward from there.



  • Liked Mathew Aniyan

    Mathew Aniyan - Beyond the wall of issues – Focus to drive velocity

    Mathew Aniyan
    Mathew Aniyan
    Sr. Program Manager
    schedule 4 years ago
    Sold Out!
    45 Mins
    As we iterate faster in Agile cycles, we tend to choose locally optimal solutions. E.g:- We use an algorithm which has poor performance so that we can deliver the feature to customer early.  These choices lead to a build-up of technical debt in software; reduces our velocity in future iterations and we deliver less business value to customers. Counter-intuitively, we become less agile.  So how can we prevent technical debt from growing? First you stop it getting worse – stop the leak, and then manage it down – clear up the flood. Making this concrete, debt gets manifested as code analysis issues, missing tests, flaky and overlapping tests, tangled dependencies and so on. The problem is that as tools get switched on to manifest that debt, the developer is faced with a wall of issues – the flood, that is just too overwhelming to deal with. So to take control of the debt, those existing issues need to be hidden so developers get visibility into the new ones that they introduce, and fix them. Then they can stop the leak. To clear up the flood, there are a number of strategies that can be employed, from clearing up as you go, e.g. when you change a method or file clear the debt out of that, to a more planful approach choosing to clean up specific components or particular kinds of debt, using e.g. the SQALE pyramid as a guide.
    In this talk, I will walk you through best practices in setting up a system to measure and understand your technical debt.  After that, I will show you a real-life example of the “Wall of Issues” and show how to focus and manage it down.
  • Liked Ritu

    Ritu - Thinking Beyond :: Marry Agile and DevOps for Phenomenal results

    Sr. Program Manager
    schedule 4 years ago
    Sold Out!
    20 Mins

    DevOps is not a person or a task or a defined role. It is a transition of mindset and culture which ensures more collaboration to build better quality software quickly and reliably. Agile and DevOps can no longer exit is Silos. They need to have a strong partnership for overall success as we move towards cloud.


    Its more of 3 key points

    1. Collaboration of People

    2. Convergence of Process

    3. Creation & Exploitation of To o l s

    We have been working in DevOps model for last 2 years. Would share the transitioning challenges and gaps. Also the first hand experience on

    - How the culture and thought process got transitioned.

    - Quality and metrics details

    - How tools supported this collaboration

    Our next vision to improve it further.