location_city Bengaluru schedule Mar 19th 03:45 - 04:30 PM place Grand Ball Room 1 people 58 Interested

Quality in Eurofins Genomics is a central focus point - analysis we do or products we produce have critical applications, be it production of drugs, identifying rare diseases or gene editing. IT is a driving force behind the scenes which challenges us to ensure the highest quality standards without compromising on speed.

When we start a new project, we do it with enthusiasm and feeling of doing something meaningful or even cool. Following scrum we quickly establish our velocity and deliver soon first release into production. Overall quality is quite good; results from testing acceptable, deadlines are coming so nothing can stop us. Let’s prioritize last bugs, fix critical, move rest into backlog – now we can be proud of having delivered value to users!

We continue delivering at ever increasing speed as team matures! Unfortunately the idyllic scenery gets soon destroyed by first, more and more effort needs to be spent addressing issues from both QA and production. We spend time arguing with QA and users on what is bug or if this defect is P2 or P3 or can even be seen as P4, from time to time we take a sprint to “stabilize”, but all too often nothing changes. User stories are getting spilled to next sprints, we postpone releases to have more time for testing, club them with next releases and finally find ourselves in downward spiral..

As quality cannot be compromised we quickly decide that Agile is fine, but as we work in regulated environment we need to be pragmatic and adjust Agile to our needs. What comes out is unfortunately not much different to Waterfall or V-Model, we still keep sprints and do reviews, but realize that only form is left. I am directly responsible for IT in Eurofins Genomics so will share experience from the field on how did we overcome this and reanimated Agile.

 
 

Outline/Structure of the Case Study

In first part I will give you a short introduction on who I am and what we do. Then we will look at the quality requirements in Biotech and related industries and what was the situation with quality at Eurofins Genomics. We will continue with challenging status quo and looking at how the holy grail of zero defects was achieved and what was the impact on team velocity.

Learning Outcome

In this session you will learn how Eurofins Genomics IT approached a challenge of zero defects, what is the real cost of quality and learn how to repeat it yourself.

Target Audience

IT executives, project managers, developers and anybody interested in achieving the quality

Prerequisites for Attendees

Open mind to challenge the way how we see acceptable quality.

schedule Submitted 1 year ago

Public Feedback


    • Liked Rashina Hoda
      keyboard_arrow_down

      Rashina Hoda - Becoming Agile vs Doing Agile (Research Talk)

      45 Mins
      Talk
      Beginner

      After 20 years since the manifesto, the latest state of agile reports more than 80% of organizations as "still maturing" in their agile practice. As agile methods expand beyond small teams and software itself, we are still struggling to answer these questions:

      • Why is it that some teams are more 'agile' than others even though they all claim to be practicing agile methods?
      • What all dimensions need to change as teams, managers, and entire organizations attempt to become agile?
      • How do these dimensions interact with each other?
      • Overall, what does it take to become agile and how does that differ from doing agile?

      This talk is based on my original theory of becoming agile developed from 10+ years of industrial research of agile practice in New Zealand and India, which received the distinguished paper award at the IEEE/ACM international conference on software engineering (ICSE), in 2017.

      In this session, I will explain the key dimensions that need to transition during agile transformations, using industrial examples, and highlight what you can do to progress beyond simply doing agile, to harness the most from your agile transformations.

      This keynote will add a unique research perspective to the conference program, sharing agile research in an industry-friendly format and delivery style.

    • Liked Jutta Eckstein
      keyboard_arrow_down

      Jutta Eckstein / John Buck - Using Beyond Budgeting and Sociocracy for agile-friendly performance appraisals

      90 Mins
      Workshop
      Intermediate

      There are many suggestions dealing with Agile-friendly performance appraisals, which promise to rely on trust, honesty, respect, safety, and servant leadership. The Agile Manifesto does not address performance appraisal although it does generally mention regular and frequent feedback, which can also be applied to performance evaluation. Two related methods, Beyond Budgeting and Sociocracy, offer interesting approaches to agile performance review. In this session we want to present these two different performance appraisal approaches, how they're are supported by the values of BOSSA nova (short for Beyond Budgeting, Open Space, Sociocracy & Agile) and want to invite the participants of this workshop to discuss the synthesis of the two approaches.

      This session looks at several real-world examples from actual companies including Accenture, Equinor, and Google.

      The first principle of Beyond Budgeting asks to “engage and inspire people around bold and noble causes; not around short-term financial targets,” the eleventh principle advocates: “Evaluate performance holistically and with peer feedback for learning and development; not based on measurement only and not for rewards only.” Thus, the main strategy of Beyond Budgeting is to separate (financial) bonuses from performance evaluation and to use relative and not fixed targets as a foundation for the evaluation.

      Sociocracy suggests holding 360 degree in-person meetings. The person being reviewed should request it when needed, not just on a rigid annual basis, and perhaps not just once in the year. In the 360 degree meeting, the organization itself can be critiqued in the review - “the way we organize is causing performance problems.” Similar to Beyond Budgeting there is a focus on the vision and mission of the specific department as well as the overall company as a source of inspiration and motivation. The output of the performance review meeting should be a development plan that the immediate group of supervision, peers, and subordinates consent to.

      Based on BOSSA nova, we invite participants to dive into what Beyond Budgeting and Sociocracy combined offer for performance appraisals. Participants will take away insights that they can use in their organizations.

    • Liked Alex Sloley
      keyboard_arrow_down

      Alex Sloley - The End is Nigh! Signs of Transformation Apocalypse

      Alex Sloley
      Alex Sloley
      Alex Sloley
      schedule 1 year ago
      Sold Out!
      45 Mins
      Talk
      Advanced

      How can an Agile Coach figure out when an Agile “Transformation” is going wrong? Are there signs that they might see, heed, and take action upon? Of course, there are!

      Hindsight is 20/20, but in the moment, these warning signs can be hard to see. Let’s explore some of the more common, and frightening, warning signs that your Agile “Transformation” might be exhibiting. We will discuss transformation provider types, frameworks, keywords, and other anti-patterns that might be signs that THE END IS NIGH.

      This session will review common themes and help familiarize you with the warning signs. Armed with this new knowledge, you will be able to plan as appropriate, to help navigate your organization through potential impending doom.

    • Liked Maaret Pyhajarvi
      keyboard_arrow_down

      Maaret Pyhajarvi - Working without a Product Owner

      45 Mins
      Case Study
      Intermediate

      For a decade of software product agile, we had worked in a structure where business responsibility of what to build was allocated to a product owner and the responsibility of how to build it was allocated to a development team. Product owner would maintain a backlog, act as voice of the customers. Until one day we realized that the choice of what to build or fix is hard, and critical to everyone’s success. If we wanted to do it poorly, we delegated it to a single product owner.

      We started a no product owner experiment. For three months, we experienced the development team delivering multitudes of value to what we had grown to expect, and innovate customer-oriented solutions in direct collaboration with customers. Team satisfaction and happiness bloomed. The experiment turned into a continuous way of working.

      Customer-focused team directly in touch with their customers performs better without a proxy. Join me to learn how the decision power shared for everyone in the team transformed the ability to deliver, and how collaboration is organized with product experts and business representatives.



    • Liked Gabor Devenyi
      keyboard_arrow_down

      Gabor Devenyi / Alex Sloley - The magic number is 10

      45 Mins
      Talk
      Beginner

      Why are Agile teams supposed to be small? How big are they supposed to be? Most agilists tend to agree that a team of ten people works well.

      But what is it about the number 10 that makes it the “magic” number?

      Since the start of human evolution, people formed groups to be more effective. Whether it was the hunt for a mammoth or going to war, working in teams ensured a greater chance of success.

      There have been various researches from Dunbar’s paper through the Scrum Guide to military formations about the ideal number of people in a team.

      We’ll discuss the historical, scientific and cultural reasons why 10 seems to be the magic number of forming effective teams.

      Does the number of team members really matter? Is 10 really the magic number. You will get an answer that will help you to create effective teams with the right amount of people.

    • Liked Fennande van der Meulen
      keyboard_arrow_down

      Fennande van der Meulen / Maartje Wolff - Designing happy teams: use Design Thinking to enhance happiness at work, raise productivity and creativity

      90 Mins
      Workshop
      Beginner

      We all know that innovative organizations are more successful. But how does Happiness at Work fit in the equation? Definitely, there is a link between happy, creative, innovative and successful organizations. In this interactive workshop, you will experience how Design Thinking and Happiness at Work go together and how that leads to success in so many organizations. We will provide practical tips on how to develop new habits to empower your creativity, empathy and thus happiness at work.

      On the basis of the theory of happiness and design thinking participants will experience step by step how they can work on more creativity and innovative thinking in their organization. The workshop will be very interactive with small exercises and mind setters.