Conference Time
Local Time

Agile India Lite

Thu, Oct 28
Timezone: Asia/Kolkata (IST)
  • Added to My Schedule
    Peter Maddison

    Peter Maddison - 4 Maps of DevOps

    schedule  08:00 - 08:20 PM IST place Zoom people 49 Interested star_halfRate

    Although DevOps practices deliver incredible benefits to organizations looking to improve their software delivery practices, the larger positive impact of DevOps to delivering value is often harder to realize. A set of practices we’ve found to help organizations is something we call the 4 Maps of DevOps. 

    Fitting nicely in between the 3 ways and 5 ideals, the 4 maps consist of Outcome Mapping, Value Stream Mapping, Dependency Mapping and Capability Mapping. They help you create a powerful roadmap that is outcomes-focused and targeted at the most important problems.

    Through this talk, I’ll walk through the benefits these maps produce, how they relate to one another and the problems you can target with them.  I’ll go through some real-life examples of using these maps to help organizations.

    This talk is for anybody who is struggling to work out where to start or where to go next with their adoption of DevOps.

  • Added to My Schedule
    Lakshmi Ramaseshan

    Lakshmi Ramaseshan - Achieving Aligned Autonomy in Product Development with Inceptions

    schedule  08:00 - 08:20 PM IST place Zoom people 33 Interested star_halfRate

    What is the value of Collaboration in your Organization? Are your teams aligned with the overall purpose & targeted outcomes of an initiative they are working on? How might you facilitate alignment & increase their chance of success?

    This talk is targeted at Scrummasters, Product, Agile Coaches and Agile Leaders who are faced with the challenge of successfully kicking off new initiatives within an organization. Facilitating true Collaboration is often understated. Complex collaborative work requires “shared understanding”, high quality discussions, psychological safety & inclusion. As leaders in organizations, we oftentimes miss that it takes intention & design to foster good Collaboration.

    Kicking off initiatives is always a challenge in organizations I’ve worked with in the past – it is either too loosely defined or too prescriptive. Inceptions are here to the rescue!! They are an invigorating & meaningful way to bring a team, dependent team(s), product and business stakeholders together to align on the Strategy (Why), The Work (What) and the Team (How). The intentional activities, design and flow of an inception enable a shared understanding which lays a foundation for inclusive collaboration. When done well it can take teams from Good to Great and set them up for success.

  • Added to My Schedule
    Shruti Pandey

    Shruti Pandey - Applying Data Science and Innovation to Infotainment Experiences

    schedule  08:00 - 08:20 PM IST place Zoom people 14 Interested star_halfRate

    The automotive industry is becoming more softwarized. Users expect their infotainment experiences to be on par with their mobile experiences, and building such connected experiences has become a top priority for auto and software organizations.

    But what is infotainment, and what can qualify as a functioning and high-performing infotainment experience? Perhaps even more importantly, what activities and practices can teams employ to create quality, personalized infotainment experiences?


Day 1

Thu, Nov 18
  • Added to My Schedule
    Dr. Denis Bauer

    Dr. Denis Bauer - Digital Disruption in health and medical research

    schedule  09:00 - 09:45 AM IST place Zoom people 185 Interested star_halfRate

    COVID-19 has accelerated the digital transformation of research and health sciences. The use of genomic information in particular has triggered some of this change, as the unprecedented data volumes requires Big Data and Cloud computing technology. This talk outlines CSIRO developed software solutions, which use the latest in cloud architecture, machine learning and distribution channels to support a wide range of digital health applications; from disease gene detection, to personalized gene therapy, and from pathogen diagnostics to biosecurity applications. Specifically, we developed novel bioinformatics approaches to track viral evolution that has led to the first study on vaccine efficacy for the different COVID-19 virus strains. We also developed a novel machine learning framework capable of processing trillion of genomic datapoints to detect disease genes. The talk concludes by looking into the future of how clinical ontologies (FHIR) in combination with health-specific cloud deployment mechanisms disrupt health care as we know it.

  • Added to My Schedule
    Elijah Eilert

    Elijah Eilert - Innovation Accounting - Financial Modelling that Works for Ventures

    schedule  10:45 - 11:30 AM IST place Zoom people 84 Interested star_halfRate

    Financial forecasts (Business Case) for startups and corporate innovation initiatives are notoriously unreliable. But instead of throwing them away entirely, it is possible to create a model, able to quantify the most likely outcome as well as uncertainty. Innovation accounting bridges the gap between innovation teams and finance and can track progress in a meaningful way. 

  • Added to My Schedule
    Sanjiv Augustine

    Sanjiv Augustine - Moving from the License Raj to Light Touch Agile Governance

    schedule  10:45 - 11:30 AM IST place Zoom people 101 Interested star_halfRate

    Today, top performing agile teams exist in organizations worldwide. However, in many of these same organizations, those very same teams are hamstrung by legacy bureaucratic management - the remnants of a waterfall “license raj.”  Issues with delivery across multiple silios, non-value adding process red tape, and antiquated PMOs persist.  So, we continue to struggle with reaping the full benefits of agile methods, and fall short of business agility.

    True end-to-end, business agility requires a bimodal approach: continued care and feeding of agile teams done in parallel with a systematic middle-management transformation away from the license raj. The Agile Value Management Office (VMO) is rapidly gaining traction as the preferred way to accomplish this through:

    • A team of teams organizational construct and approach for light-touch governance
    • Adaptive planning and experimentation with small-batch Minimal Marketable Products (MMPs) for end-to-end flow 
    • Up-front and continuous integration of legal, audit and other business-critical functions for true risk management

    Join Sanjiv Augustine to explore how these have liberated managers, unshackled agile teams and resulted in positive customer outcomes. Through key case studies, we’ll see how these have also ensured critical management, oversight, and governance. 

  • schedule  10:45 - 11:30 AM IST place Zoom people 164 Interested star_halfRate

    In the wake of the pandemic and the challenges we have seen around us, organisations have realised how inequities can trickle down to many aspects within the sphere on workplaces, teams and practices we follow. It’s time to revisit old practices in more ways than one. 

    Aspects like lack of work-life balance, mental well being, asynchronous communication, extended virtual meetings, prolonged virtual pairing etc. impact us all. 

    To address this ThoughtWorks introduced the 'Inclusive Teams - Social Contract' an exercise for teams to re-look at their old ways, to arrive at an aspirational set of behaviours and social norms for inclusive ways of working at both the team and individual level. 


    It focuses on 4 key aspects -

    1. Building a culture of trust and inclusion - Supporting each other, feedback, empathy and cultivation.
    2. Schedules and Meetings - Best practices, setting personal boundaries and context.
    3. Communication practices - Tools, patterns and inclusive practices.
    4. Norms of engagement - Connecting as team, fun that is inclusive, welcoming & respectful.

    The inclusive team social contract helps teams understand and empathise with each other, acknowledge differences and personal context thus increasing team connect, productivity and shared accountability. It’s recommended that teams run this irrespective of whether they are working virtual/F2F/distributed/remote etc. 

  • Added to My Schedule
    Kelsey van Haaster

    Kelsey van Haaster - Passwordless: a story of risk, protection and excellent UX

    schedule  11:45 AM - 12:30 PM IST place Zoom people 68 Interested star_halfRate

    The June 2017 NIST special publication 800-63B, covering Digital Identity, turned what had previously been the gold standard for passwords on its head. For the first time, NIST recommended removing complexity rules and password cycles, supporting longer passwords, no restriction, or requirements  on special characters and preventing the use of  common passwords and those already exposed in a known breach. Why these changes? Because with the best will in the world, the human element in our security measures is always going to be the weakest link. Forcing individuals, particularly those whose primary role has nothing to do with Information Technology, to remember hundreds of unique complex passwords is hard. They don’t want to and when we make them, they get it wrong or look for an answer with as little friction as possible. NIST’s new guidelines are intended to remove some of that friction. When combined with the use of a password management system and multi factor authentication, we might hope that our corporate assets are no longer protected by the same password someone used on their favourite shopping site. 


    Unfortunately, things are never that simple. For non-technical users, even working with a password manager can present challenges. Not all systems play nicely with password managers, and they also do not stop a user from using the same credential for more than one product. 


    Passwordless authentication is one exciting way forward. This in itself, is not new technology, having been around in various forms for a while - think magic email links for example - but the approach still relies upon shared secrets. However, the release of the WebAuthN standard by the W3C and FIDO, supported by many key vendors, allows us to take advantage of public key cryptography.

    At ThoughtWorks we have embarked on a journey to introduce passwordless login to our employees, particularly those with high value accounts and who may be less technical than many. The goal of this session is to share what we have learned throughout this process. We will share our goals, challenges and their resolutions. We hope attendees will be inspired to evaluate this technology, which delivers the rarest of things, better security and a fantastic user experience.     

  • Added to My Schedule
    Matthew Hodgson

    Matthew Hodgson / Mia Horrigan - Measuring agility: Data analytics from psychology to grow your teams agility at scale

    schedule  11:45 AM - 12:30 PM IST place Zoom people 192 Interested star_halfRate

    How do you know if you’re really agile? Like predicting the weather, complex human systems need data analytics and statistical models over simple reporting, to understand what creates business agility from human behaviour. This is the world of psychology, statistics, human behaviour models. It’s how medicine predicts if you have factors that predict heart attacks or if children are likely to have developmental delay. It’s time to apply this to agile teams to growing a true agile mindset.

    This talk looks at the psychology of human behaviour and data analytics to provide a playbook for measuring and improve an agile mindset in teams to underpin true business agility. It looks at 10 years of longitudinal data, both from software and non-software agile teams, and large scale agile transformation initiatives, and the model that’s now been produced to help coaches and the enterprise become more agile.

  • Added to My Schedule
    Dr. Ashay Saxena

    Dr. Ashay Saxena / Deanna Spowart - Are agile organisations really inclusive?

    schedule  11:45 AM - 12:30 PM IST place Zoom people 57 Interested star_halfRate

    Are agile organisations really inclusive? Surely, given the fundamental principle of “individuals and interactions over processes and tools” and the fact that almost every agile approach embeds collaborative practices, the answer should be yes. And yet, the lived experience of many people contradicts this. Putting these assumptions and hypotheses to the test, the Business Agility Institute undertook an ambitious, year-long, research project and heard from 500 people globally.

    What we found is that there is a lack of understanding about diversity, equity and inclusion (DE&I). Many people shared their personal experiences about feeling excluded or knew of others who had been. In most cases, DE&I was not part of the agile transformation designs; for either employees or customers.

    In 2021, we have the opportunity to rethink our approach to DE&I in agile organisations and learn from those organizations who, as we discovered in our research, are intentionally designing their new ways of working to be inclusive. As thought leaders and change makers, we want to share ways you can make a difference to people in your team and create an organisation where everyone can belong. Impacting not only your employee experience but your customers' experience and how you serve your community.

    Deanna Spowart and Ashay Saxena, lead researchers on the project, will present the findings of their research “Are agile organisations really inclusive?” In the broader context, Deanna will share practical guidance on being an inclusive team member and Ashay will share what the agile organisations need to do embrace inclusion.


    Lunch Break - 60 mins

  • Added to My Schedule
    Yashasree Barve

    Yashasree Barve - Journey towards autonomous teams | A coach's toolkit

    schedule  03:30 - 03:50 PM IST place Zoom people 107 Interested star_halfRate

    The scrum guide says that "A scrum team is self-managing, meaning they internally decide who does what, when, and how." One of the most important responsibilities of a scrum master (or a coach or even a leader) towards a scrum team is coaching them in self-management. Self-managed teams are empowered to inspect the way they work and outcomes achieved and adapt themselves to be better. These teams are autonomous in several aspects of managing themselves. Autonomy is also an important pillar of intrinsic motivation as per Daniel Pink’s book “Drive”

    As part of coaching agile teams, we experimented with establishing various dimensions of autonomy within a team based on work done by various thought leaders. It helped the teams to understand where they stand on various aspects of autonomy, what can be taken up as an improvement backlog as well as what help do they need from the environment or ecosystem.

    This session lays down these important dimensions along with the format of the workshop for teams and a toolkit that will help the teams to understand autonomy details, identify where they are and what they can do to be more autonomous.

    The session will help agile team coaches, scrum masters or leaders to discuss team autonomy in an interactive way with their teams and identify improvement areas.

  • Added to My Schedule
    Sunil Mundra

    Sunil Mundra - Embracing Complexity-A Case Study of leveraging 'Agent' Interactions

    schedule  03:30 - 03:50 PM IST place Zoom people 67 Interested star_halfRate

    The primary challenge which leaders are facing is to evolve their enterprises to deal with increasing complexity in the external environment. Leaders are constantly having to deal with circumstances which are volatile, ambiguous and uncertain, which are the result of increasing complexity.

    In this talk, the speaker will focus on one key characteristic of complexity, viz. how interaction between 'agents' in a complex system produces value. The speaker will present a case study of how leaders in an enterprise leveraged this characteristic to create value, in their Agile Transformation journey..

  • Added to My Schedule
    Asheesh Mehdiratta

    Asheesh Mehdiratta / Sujatha Nagaraj - Lessons in addressing data challenges while using OKRs, for driving business outcomes and bringing customer centricity

    schedule  03:30 - 03:50 PM IST place Zoom people 109 Interested star_halfRate
    • Do you know your business goals?  and is IT aligned?
    • How are you addressing data challenges (source, quality etc) for measuring Key Results?
    • What experiments you can run to make data as a first-class citizen?
    • How do you use this data (Key Results) to enhance the collaboration among teams, solve interdependencies and unify competing approaches?

    With the increased demand of organizations striving for business agility & disciplined investment management, the traditional way of alignment is becoming less relevant. Hence organizations are exploring different approaches for goal setting to track the extent to which the investment is achieving the value intended and improve the business outcomes.

    In this session, we will take you through our journey and experiences by explaining the essence of OKR framework ,our lessons learnt while addressing data challenges, the experiments to get the right quality data for obtaining the Key Results and how it helped to achieve clear alignment between IT and business teams.

    Come and join our session to learn from our experiences and pitfalls.


    Break - 25 mins

  • Added to My Schedule
    Aino Corry

    Aino Corry - Team Meetings That Don't Suck - Avoid Retrospectives Antipatterns

    schedule  04:15 - 05:00 PM IST place Zoom people 164 Interested star_halfRate

    Anti-Patterns are like patterns, only more informative. With anti-patterns, you will first see what patterns recur in “bad” retrospectives and then you will see how to avoid, or remedy, the situation. Based on her experience with facilitating retrospectives, join Aino for an entertaining and informative presentation on the challenges she has seen and how to overcome them. This talk will be interesting for everyone facilitating meetings in general, and retrospectives in particular. Her latest book “Retrospective Anti-Patterns” will give you more info that she is able to convey in this talk.

  • Added to My Schedule
    Blerina Nasto

    Blerina Nasto - Software Developers in Test Automation - A Dream or Reality in Agile Software Development?

    schedule  04:15 - 05:00 PM IST place Zoom people 70 Interested star_halfRate

    Gone are the days of throwing software builds over the proverbial wall to a team of testers that sit and click pages all day. The agile way of working has shown that maybe a small revolution has started to happen in the world of software developers. The rising of software developers writing e2e functional tests that check their front-end using real browsers. Challenges of having success in this way of doing test automation are real. Let’s be sincere! Software Developers don’t like to write tests much, but the right TA framework can help. In this talk I will describe what we did to make this dream come true.

    This is a real life story of how our product team made possible to succeed in delivering quality and speed in every sprint.

  • Added to My Schedule
    Sundaresan Jagadeesan

    Sundaresan Jagadeesan - .tune - Eliminate waste in SW Development

    schedule  04:15 - 05:00 PM IST place Zoom people 69 Interested star_halfRate

    We all have heard about (Scaled) Agile transformations and it various flavors. What's next and how do we sustain the momentum and drive continuous improvements.

    After a successful Scaled agile transformation in the Organization, we are sustaining the momentum and driving the the 2nd wave of transformation, namely SW Excellence projects. One of the flag ship programs in the SW Excellence Projects is .tune - elimination of waste removal in SW development by deep observtaions

    The waste challenge:


    We all enjoy being productive and effective in software development but how do we really find and remove the things that slow us down?

    To achieve this we need to know

    How much waste we have?

    Is it going up or down?

    What actions can we take to reduce it?

    The goal 

    Stimulate a culture of zero waste. Discover, quantify and eliminate waste

    Improve productivity, predictability and quality

    The Big opportunity - is out there to reduce micro and macro wastes in development! Via Deep observations @ developer desk and enabling productivity aspects, we are able to identify and eliminate greater than 20% in development waste


Day 2

Fri, Nov 19

    Break - 60 mins


    Break - 30 mins

  • Added to My Schedule
    Alberta Soranzo

    Alberta Soranzo / Martina Hodges-Schell - The remote leader – distant but not removed

    schedule  04:00 - 04:45 PM IST place Zoom people 101 Interested star_halfRate

    If the last year has taught us anything, it’s that the way we think about, well… everything has to change, including the way we think about work and leadership.

    In this session, we will present the results of a research study conducted among global leaders, and explore how the pandemic has impacted the way we look after our teams, the differences between remote and in-person leadership, challenges and opportunities created by physical distance, and how to prevent it from also becoming emotional and intellectual distance.

    We start from a set of questions we’ve asked ourselves both in the past and more recently:

    • How do you create and maintain connection and trust when you cannot look someone in the eye or walk by their desk?
    • How do you oversee work, advice, mentor and help people grow at a distance?
    • How does a team that can’t get together, stay together?
    • What kind of additional or different support does your team (and you) need?
    • And more…
  • Added to My Schedule
    Vedavalli Kanala

    Vedavalli Kanala / Priyank Gupta - Your role is superfluous: Software delivery with skills-based, self organising teams

    schedule  04:00 - 04:45 PM IST place Zoom people 54 Interested star_halfRate

    Traditional software delivery teams are layered with roles like user experience, project management, business analysts, developers, QAs, DevOps, etc. With the translation of business problems at multiple steps, each role induces a fitment drift in the devised solution. As part of this talk, we would like to present our experience from the last 7 years building products for clients delivered by teams with ZERO roles (No PM, BA, QA, DevOps). It presents the argument and evidence of why the notion of needed depth in every skill, every single time is an overkill, and how a small team of people who dabble with code and product thinking both can deliver solutions that are faster and better with minimum fitment drift. We outline the practices and rituals required to establish, operationalise and sustain skill-based teams. We also intend to discuss delivery objectives for software teams and how teams that organise themselves around business objectives deliver better products compared to one's setup with superfluous roles for analysis, testing, and management, etc. 

  • Added to My Schedule
    Naresh Jain

    Naresh Jain - Technical Debt Prioritisation - Identifying And Fixing Highest ROI Issues

    schedule  04:00 - 04:45 PM IST place Zoom people 113 Interested star_halfRate

    Does your technical debt backlog look endless? Are you thinking about pausing feature development to resolve tech-debt? Stop. What if I told you that a good chunk of your backlog can simply wait? Tech-Debt can seem overwhelming when we look at it as a loosely organised list. This can lead to several anti-patterns in how we deal with them. Attend this session where I will be sharing strategies we have been leveraging to identify high priority tech-debt items to make sure we are able to continue feature development while improving code health.

    Problem Statement: Tech-Debt often accumulates until productivity takes a serious hit and then as a knee jerk reaction we try to clean it up all at once. At this point there is just one large list of issues with a loose sense of priority. Net net it gives an impression that we have a huge backlog. This can lead to several anti-patterns.

    • Chicken and Egg Problem - Too much Tech-Debt, so feature development is slow. Since feature development is slow, we cannot set aside time to fix issues.
    • Fixing the wrong issues - In the larger scheme of things, it may be counter-productive to fix low priority issues just because they are easy.
    • Pausing Feature Development - Approaches such as "Technical Debt Sprints" where we pause features to resolve tech-debt are not be sustainable even if they offer some short term benefits.
    • Local Optima - Patchy cleanups which lead to uneven code health across the code base.
    • And many more

    Solution: Understand the impact of each Technical Debt at Block, Category and Item level to narrow your backlog to those issues which matter. While there are several tools that help us identify tech-debt it is up to us to map our context on those issues. Attend this talk where I will be going over how to VISUALISE, TRIAGE, PRIORITISE and STRATEGISE in order to get a realistic view on your tech-debt. Also I will be sharing my experience about how we have been leveraging time boxes and capacity constraints as a tool to make sure we are only working on the most important tech-debt issues.

    Topics that will be covered:

    • Tech-debt resolutions strategies - Anti-Patterns
    • Tech Debt - Understanding Size vs Impact
    • Tech-Debt Manifestations - Matrix view of areas of code and types of problems.
    • Visualise - Triage - Prioritise - Strategise
      • Visual techniques to understand your tech-debt backlog with code analysis tools - Examples with popular tools
        • Bubble Charts - Coverage vs LOC, Maintainability vs LOC etc.
        • Git History - Multiple ways of looking at changes to a piece of code
        • Active Code Paths - Mapping usage to issues
        • Mapping Project Management Data - Bugs, Stories that touch a piece of code
      • Triaging the backlog to quickly eliminate tasks that can wait
        • Block level - Leveraging Logical Architecture
        • Category vice - Example: Front-End, Backend, API etc.
        • Item vice elimination
        • Refactor vs Rewrite
      • Prioritising tech-debt with layers of detail such as - Churn, LOC, Coverage, Bugs etc. Hotspot Identification.
      • Strategise - Approach to resolving each tech debt item based on Tech-Debt Manifestation Matrix
    • Tech-Debt resolution - Hypothesis based, Data Driven approach
      • A template to capture your hypotheses, experiments and learnings
      • Visual confirmation that the issue is resolved
      • Just-Enough resolution - The uncomfortably short time-box - Imposing constraints to avoid runaway clean-ups
      • Guard rails to avoid a repeat of the same issue
    • Incorporating tech-debt resolution into your Iterations, Weeks, Sprints, etc.
      • Identifying the right cadence on how often you fix debt - Hours per Day, Days per Week etc.
      • Tech-Debt back log Grooming
      • Cycling through categories of tech-debt
    • Measuring Progress
      • Short-term - Measuring immediate impact on the code
      • Medium-term - Productivity improvements (Readability, Issue resolution time, etc)
      • Long-term - Team Health - Knowledge Silos, New Team Member Onboarding Time
  • schedule  05:00 - 05:45 PM IST place Zoom people 26 Interested star_halfRate

    One billion people are estimated by the World Health Organisation to have a disability. W3C's Web Content Accessibility(A11y) Guidelines (WCAG) are becoming increasingly mandated by governments. They are being used by many industries to make websites more accessible for people with disabilities. The product development team is often told to make their websites accessible like it is an easy light switch you turn on or off, but, it is not easy.

    Digital transformation is now the holy grail of IT organisations. However, most companies are striving towards engineering excellence with processes like the Continuous Delivery process and often forget about the usability and Accessibility factor, which has to be given utmost importance early in the cycle. Because the applications/ products that we build should be accessible by all.

    "Accessibility is everyone's responsibility" - We all need to understand that Accessibility isn’t “someone else’s job”. In this talk, Manoj intends to share some practical examples of baking Accessibility during your agile software development cycle and advocates striving for engineering excellence with empathy. This talk will include basics like, need for Accessibility, followed by some practical, simple ways to find Accessibility flaws and, this will enrich the level of confidence to have some meaningful conversation about pushing for Accessibility mindset at their workplace and how to take it forward by baking in the accessibility at part of your Agile process from planning stages to production stages.

    This talk will share practical insights on how to bring in the Accessibility mindset within teams and highlight tools and processes in the Accessibility ecosystem to implement during product development, 

    • Where to start with Accessibility?
    • Can we add Accessibility into the Definition of Done?
    • What audit tools to use in the software dev lifecycle
    • How organizational transformation on Accessibility initiative can be done to promote the Accessibility thought process.
  • Added to My Schedule
    Jorge Luis Castro Toribio

    Jorge Luis Castro Toribio - Continuous Fun: Game Driven Development : A game design framework to drive, build and mature software engineering practices

    schedule  05:00 - 05:45 PM IST place Zoom people 93 Interested star_halfRate

    This paper shares our experience to build DevOps and engineering practices at large scale as part of digital transformation looking for improve our flow efficiency, lead time and products quality and how we made designing and implemeting gamification shifts left through. This papers shares you the framework ( step by step) that we did to make game drive development and engage developers to adopt DevOps and technical agility practices

  • schedule  05:00 - 05:45 PM IST place Zoom people 75 Interested star_halfRate

    Data technical debt refers to quality challenges associated with legacy data sources, including both mission-critical sources of record as well as “big data” sources of insight. Data technical debt impedes the ability of your organization to leverage information effectively for better decision making, increases operational costs, and impedes your ability to react to changes in your environment. Bad data is estimated to cost the United States $3 trillion annually alone, yet few organizations have a realistic strategy in place to address data technical debt.

    This presentation defines data technical debt is and why it is often a greater issue than classic code-based technical debt. We describe the types of data technical debt, why each is important, and how to measure them.  Most importantly, this presentation works through

    Disciplined Agile (DA) strategies for avoiding, removing, and accepting data technical debt. Data is the lifeblood of our organizations, we need to ensure that it is clean if we’re to remain healthy.

  • Added to My Schedule
    Al Shalloway

    Al Shalloway - Achieving Business Agility with Value Stream Management

    schedule  06:35 - 07:20 PM IST place Zoom people 113 Interested star_halfRate

    Business Agility is the ability to deliver value to customers quickly, sustainably, predictably and with high quality. Improving business agility requires identifying what is of the greatest value, having a value management office to allocate funds for these items, a way of organizing people so they can effectively collaborate, and a method of working on these items efficiently. While there are a lot of moving pieces, proper attention to the value stream enables all parts of an organization to align around improving both the way an organization’s clients work as well as how they add value to it.

    Attending to how both customers and the development organization can work more effectively is the heart of value stream management. It brings together three disciplines. First, Theory of Constraints to identify the constraints in the system. Then the theories of flow are used to reduce the delays in the workflow which create rework and waste. These two integrate with Lean-Thinking which focuses on creating an environment within which people can work together effectively.

    This session provides an overview of why value streams are so critical and how to improve them.

Day 3

Sat, Nov 20
  • Added to My Schedule
    Raja Bavani

    Raja Bavani - Enhancing Desirability: Five Considerations for Winning Digital Initiatives

    schedule  11:00 - 11:45 AM IST place Zoom people 39 Interested star_halfRate

    Experience centricity is essential to drive business outcomes and has become the top priority of many CXOs. The COVID-19 crisis has made experience-centricity and IT agility paramount to nearly every business. In the post-COVID world, businesses need superior digital enablement and acceleration to ensure continuity, customer satisfaction and competitive edge.

    Experience centricity, however, is not limited to creating new digital products and channels. It encompasses every aspect of software that can enhance an organization’s ability to solve business challenges and harness opportunities through digital solutions that are meaningful and delight end users – both inside and outside the enterprise.

    The ongoing digital revolution and related opportunities, challenges and risks pose several questions in the minds of IT executives. What makes digital products go viral? What are some of the key success factors?  How can we make digital initiatives thrive? How can organizations succeed in transforming monoliths into digital products or platforms?

    Improving usability through the right mix of user interface and interaction design, application of design thinking, and focusing on functional and non-functional requirements are the foundations. Usability is essential. Usability ensures effectiveness, efficiency and satisfaction. However, beyond usability, understanding the power of desirability and enhancing it is a prime factor. Desirability provides a meaningful, enjoyable and memorable experience.  Desirability is what makes the users bond with the product with the ongoing delightful experience it creates resulting in a worthy engagement. Whether you create and deliver new products and applications or modernize existing applications to deliver an outstanding digital experience, enhancing desirability is essential.

    This session is to present five considerations for enhancing desirability with real-world examples that reveal how any heritage organization can create experiences that help the business achieve its strategic aspirations and objectives.

  • schedule  11:00 - 11:45 AM IST place Zoom people 91 Interested star_halfRate

    Very often we work on a code-base that has been written by others, and some time ago. This code-base could be for the product code, or Test Automation code. 

    As the product life increases, evolution of the code-base is a natural process. However, there are various catalysts to speed up this evolution process:

    • More features / tests to be added, including increased complexity
    • People writing the code evolve - their learning, skillset
    • Delivery pressure means it is quite possible that correct decisions for implementation may not be taken. In other words, it is possible that short-cuts were taken in the implementation leading to spaghetti code / architecture

    People move on to different roles, new people join the team. Each has different opinions, perspectives and experiences.

    Am sure there are more reasons you can think of.

    Regardless, the challenge for a new person who starts working on such a complex code-base is enormous - as the person needs to start delivering "value".

    In this session, I will share various examples and experiences and as a result of being in such situations, the factors I looked at when enhancing the code-base to decide - should I refactor or rewrite the code-under-consideration to be able to move forward faster, while moving towards the long-term vision.

    Though I will focus on various examples of Test Automation, this session is applicable for any role that writes / maintains code of any nature.


    Break - 60 mins

  • Added to My Schedule
    Isabel Evans

    Isabel Evans - Stuck in Limbo with Magical Solutions

    schedule  05:00 - 05:45 PM IST place Zoom people 39 Interested star_halfRate

    As we face increased demands or speed, change and technical excellence, the pressure, and the need, for tool support for testing increases. Organizations want to automate aspects of testing. Is this possible? What effect does it have on the work and on the people doing the work? Success is not just about selecting and implementing tools and technical infrastructure. People ensure the success or failure of testing and of tool use; they must drive the project. 

    Isabel is midway through a research project to explore testers’ experiences with tools and automation. So far, she’s uncovered some illusions about tool usability, some attempts at magic, and many new questions.

    Interviews, workshops, and survey responses from nearly 200 testers revealed people found tools and automation to be problematic in many ways, leading to people expressing high levels of emotion, stress and distress. Over 30% of the respondents to the anonymous survey answered questions about their experiences with test tools in a way that indicated emotional responses. People talked about tools leaving them “stuck in limbo” and unable to do their work, expressed their frustration that tools are treated as “magical solutions for all of the test problems” and expressed their fears, and the demotivation they felt: “I think I should leave my job.”

    Part of the problem was the usability of the tools. This was the attribute most often discussed by testers when describing both their aspirations for tool, and their frustrations with tools. It is not just that some tools have been built without usability in mind, but that where usability had been part of the design criteria, it merely offered an illusion of usability, with a superficial veneer to the UI that didn’t address workflow, differing needs among testers, and their changing requirements. 

    In this reflection on her research and industry experiences, Isabel talks about learning new ways of working after decades in the industry, her findings so far, what she’s discovered that will help your testing now, and her plans for the rest of the research. She’ll be asking you to contribute to a survey to discover who is doing testing, and how they are doing it. This will feed into a model for designing test tools that support people, and make test tool design a people-centred activity.

  • Added to My Schedule
    Matthias Zax

    Matthias Zax - “Self-Healing Tests” The holy grail of test automation ... Or just a lot of ado about nothing?

    schedule  05:00 - 05:45 PM IST place Zoom people 66 Interested star_halfRate

    Self-Healing Tests is an approach in which machine learning helps with the maintenance of automated tests. Self-Healing, the automation of test automation, recognizes changes in the "system under test" and automatically adapts the test execution so that the tests remain functional. Commercial tools like TestIM and Tricentis Neo Engine are promising and focused on this area in good time. But there are also promising open source alternatives such as Healenium. This talk explains the pros and cons of self-healing tests and shows the implementation with the open source library Healenium using a concrete example.

  • Added to My Schedule
    Deepak Koul

    Deepak Koul - Taking biases into account : Why retrospectives promise more and deliver less

    schedule  06:00 - 06:20 PM IST place Zoom people 64 Interested star_halfRate

    Sprint retrospectives were designed to make the process of software development empirical. An approach where you can make mistakes but also reflect and learn from those mistakes.

    They possibly are the ‘A’ in the Deming’s Wheel (Plan-Do-Check-Adjust) that served as the origin of iterative development methods. Unfortunately, that is not how modern retrospectives work. They are rife with boredom, failure to admit mistakes, and lack of follow up if somehow two or three action items were identified.

    My interest in organizational behaviour and keen research links each of these problems to a cognitive bias.


    In this talk, I will list all of the biases that make retrospectives ineffective and ways in which we can mitigate them.

    For example, Recency bias is the tendency to focus on the most recent time period instead of the entire time period. Having retrospectives at the end of a sprint or maybe once a month makes people forget most of the problems they faced or the mistakes they made early in the sprint.

    But how do we fix this?

    Radical idea but how about a custom field called “Lessons learned” on every ticket you work on. Everybody keeps filling their observations per ticket during the sprint instead of waiting for the final retrospective.

    We can call them micro-retrospectives spread across the entire cycle that can be the fodder for the actual retro meeting.

    There are also other biases like sunk cost fallacy and halo effect that I am going to discuss in this session.

  • Added to My Schedule

    Tom HENRICKSEN - Humans are hard, Code is easy

    schedule  06:00 - 06:45 PM IST place Zoom people 40 Interested star_halfRate

    Are you a frustrated developer who feels like they know enough? However, the success you thought you would have is out of reach. You see others who make better strides but why? Is it a skills gap? Come learn how to set yourself apart as a developer and learn the skills of influence and collaboration.

  • Added to My Schedule
    Balvinder Kaur Khurana

    Balvinder Kaur Khurana / Sushant Joshi - Real time insights for better products, customer experience and resilient platform

    schedule  06:00 - 06:45 PM IST place Zoom people 53 Interested star_halfRate

    Businesses are building digital platforms with modern architecture principles like domain driven design,  microservice based, and event-driven. These platforms are getting ever so modular, flexible and complex.

    While they are built with architecture principles like - loose coupling, individually scaling, plug-and-play components; regulations and security considerations on data - complexity leads to many unknown and grey areas in the entire architecture. Details on how the different components of this complex architecture interact with each other are lost. Generating insights becomes multi-teams, multi-staged activity and hence multi-days activity. 

    Multiple users and stakeholders of the platform want different and timely insights to take both corrective and preventive actions.Business teams want to know how business is doing in every corner of the country near real time at a zipcode granularity. Tech teams want to correlate flow changes with system health including that of downstream stability as it happens.Knowing these details also helps in providing the feedback to the platform itself, to make it more efficient and also to the underlying business process.

    In this talk we intend to share how we made all the business and technical insights of a complicated platform available in realtime with limited incremental effort and constant validation of the ideas and slices with business teams. Since the client was a Banking client, we will also touch base handling of financial data in a secure way and still enabling insights for a large group of stakeholders.

    We kept the self-service aspect at the center of our solution - to accommodate increasing components in the source platform, evolving requirements, even to support new platforms altogether. Configurability and Scalability were key here, it was important that all the data that was collected from the source platform was discoverable and presentable. This also led to evolving the solution in lines of domain data products, where the data is generated and consumed by those who understand it the best.

  • Added to My Schedule
    Ellen Grove

    Ellen Grove - Drawing Together (even when we're apart): Visual thinking for distributed teams

    schedule  07:00 - 07:45 PM IST place Zoom people 80 Interested star_halfRate

    Moving to predominately remote ways of working has increased the challenges we face in reaching shared understandings of complex problems. And we need to be able to see the big picture together in order to really work effectively towards a common goal, especially when working as distributed teams. It’s hard enough to get people on the same page when we’re sitting together in the same room — achieving this when we are limited to communicating through online collaboration tools can be exhausting.

    But even when we are not together, we can make use of simple visualization techniques to help share what we know and to better appreciate others points of view. And we don't need fancy tools to do this – a marker, a piece of paper, and a webcam are sufficient to allow us to harness the power of visualization to improve understanding. In this interactive session, you’ll experience a simple exercise that you can use to help any group use visualization, mental models, and systems thinking to increase comprehension of complex interactions, even when working remotely. Please bring a sheet of paper and a marker — this will be hands-on!

  • Added to My Schedule
    Kristin Jackvony

    Kristin Jackvony - Helping Your Whole Team Own Software Quality

    schedule  07:00 - 07:45 PM IST place Zoom people 56 Interested star_halfRate

    In today’s Agile world, quality needs to be owned by the whole team, not just the software testers, in order to release quality software quickly.  In this presentation, I’ll discuss the key attributes of quality, the specific behaviors that are needed for those attributes, how software developers can get involved, and how the team can measure progress.

  • Added to My Schedule
    Nancy Van Schooenderwoert

    Nancy Van Schooenderwoert / Brian Shoemaker - Agile Successes in Regulated Medical Development

    schedule  07:00 - 07:45 PM IST place Zoom people 28 Interested star_halfRate

    Recent stories of Agile application in the regulated medical industry show how first principles (from Agile, from Lean, and from systems thinking) led to solutions that served the individual company exquisitely well, and were compliant with regulatory needs (whether in Europe, the U.S., or elsewhere in the world).

    ----- Longer description -----

    What is the hardest part of applying Agile methods to Medical development?

    Brian and I were asked this question in connection with our new book “Agile Methods for Safety-Critical Systems: Case Studies of Medical Product Companies”. I give two answers to that question…
    There are “twin” hardest problems - first the misconception that Agile must be taking unacceptable shortcuts to be so effective. Second, once they’ve decided that’s not the case there is a strong misconception that Agile can be ‘installed’ by tick-box actions like buying a tool or a methodology. That second misconception is what our new book addresses, and will be the topic of our talk at Agile India 2021.

    We wrote the book to help more people see positive, creative, successful implementations of Agile principles in the demanding environment of medical device development. Why successes and not failures? Attractors are stronger than repellers. People naturally want to emulate what they see working well for others, especially when those others are in similar roles to their own. 
    But emulate is not the same as “copy” especially where complexity is involved. “In complexity you don’t copy an outcome, you replicate the starting conditions.” said Dave Snowden in a recent blog post   This point needs some explanation - and that is what our new book attempts to do. People in our case studies worked from their understanding of the key principles underlying Agile, Lean and systems thinking to take a fresh look at their situation. By starting from first principles and their own deep knowledge of their products, people, and markets they achieved results any consultant would be proud to match.
    Did you know that if your software is designed and built without using a Quality Management System correctly, then the regulators can refuse to give permission to market it? That happened to one company and they ended up having an Agile company re-develop their software.
    Did you know that your SOPs (standard operating procedures) should not be overly prescriptive. If they are they impede the flexibility that your Agile teams need. There is a sweet spot that you can achieve using BDD!
    Did you know that an Agile company can move into doing medical device work without first getting certifications such as IEC62304 and ISO13485? It’s true. Simply by having a well-disciplined Agile Quality Management System, they attracted contracts to develop software for large medical device companies.
    Want to know more? Come to our session!

    1 favorite 0 comments