When agile came into being, a lot of the new technologies that we know today did not even exist. Does our definition of agile and the process that we follow change with new areas of technology thinking like data science, artificial intelligence & big data engineering coming into picture? Does INVEST make sense for data stories? Do we even write stories or should we work hypotheses instead? Do we need Acceptance Criteria or Exit criteria? How do lean, agile & product principles work in context of AI problems? What happens when science meets products?


Outline/Structure of the Talk

- How are data projects different from regular delivery projects?

- Pre-requisite: mindset to experiment

- Importance of outcomes and metrics in a data project

- Practices - Division of labour, Estimations, Interaction with other roles in a team

- Team setup - Important roles

- What are the useful tools and frameworks?

- How to think about data roadmaps?

Learning Outcome

  • Understanding of need for experimentation
  • Thinking frameworks for:
    • Experiments
    • Evolving roadmaps
    • Doing incremental science based exploration to solve business problems
    • Full project lifecycle of a "Data" centric product

Target Audience

Product managers, Business Analysts, Project Managers, Data Scientists, Data engineers, Tech Leads, Engineering Managers, Delivery managers

schedule Submitted 4 years ago

  • Gopinath Langote

    Gopinath Langote - Confidently Releasing Microservices With Consumer Driven Contracts

    Gopinath Langote
    Gopinath Langote
    Software Engineer
    N26 GmbH
    schedule 4 years ago
    Sold Out!
    45 Mins

    Many teams working with microservices need confidence they don't break functionality when making changes. System integration tests, functional tests, and sometimes manual tests are older ways to obtain that confidence. These processes may take more than 1 day or even more if different teams or a different company own the services.

    To ensure the same level of confidence and speed up delivery, we can create Contracts for integrations between consumers and providers. Contracts created by consumer services need to pass with every build going in production to guarantee the integrations between systems/services work fine. Checking these contracts in a CI/CD pipeline makes feedback loops even faster.

    A Contract is a collection of agreements between a Consumer and a Provider that describes the interactions that can take place between them. Consumer Driven Contracts (CDCs) is a pattern that drives the development of the Providers from its Consumer's point of view. It is TDD for microservices.

    This talk covers an end to end demo of contract testing between two microservices to show how to release microservices with confidence, get early feedback, speed up delivery, and comparison with other testing strategies.

    Happy CDC!

  • Akshay Dhavle

    Akshay Dhavle / Chirag Doshi - Fear of Failure - What's at stake and What can you do about it?

    45 Mins

    In the era of digital transformation, enterprises want to be responsive and innovative. They adopt agile practices to help with this but there are few success stories. Moreover, most success is limited to the team level. There are deep cultural shifts required to be successful in the new world and one of the biggest elements that stops organizations from succeeding in the technology space is fear of failure. This crippling fear works at all levels from individuals to departments and business units and it is imperative for organizations to take bold steps to eradicate it.

    This talk will explain what's at stake because of the fear of failure and a few ways in which enterprises can tackle it.