DRAFT

Agile Coach Camp

Sun, Mar 15
09:30

    Agile Coach Camp - 510 mins

Pre-Conf Workshop

Mon, Mar 16
09:30

    Registration - 30 mins

10:00
  • schedule  10:00 AM - 06:00 PM place Magnolia

    n this one-day Workshop, Dave Snowden, the creator of the Cynefin framework and famous in the agile community as an inspiring and sometimes controversial speaker, will address agility from the point of view of complexity. Participants will be exposed to a realistic approach that puts context before dogma and shows a future for Agile that goes beyond fighting over methods and towards a sophisticated application of agility in organizations.

    This class will offer an introduction to the Cynefin framework by its creator: the Cynefin framework is a transformational idea that uses a situation-specific approach to making sense of the world in order to act in it, and ensures effective work, decision making, and management even in complex and uncertain environments. For Agile practitioners, this framework supports effectively tailoring methods and practices to different situations. Cynefin-informed methods and practices help Agile organizations harness change and turn complex situations into a competitive advantage for customers and the business.

  • Added to My Schedule
    keyboard_arrow_down
    Jutta Eckstein

    Jutta Eckstein / John Buck - Beyond KPIs and OKRs: Creating an environment for high-performing, innovative teams that leads to true effectiveness

    schedule  10:00 AM - 06:00 PM place Plumeria

    Leverage your team’s agile performance potential by using BOSSA nova, a synthesis of Beyond Budgeting, Open Space, Socioracy, and Agile. Too often innovative people in medium to large organizations have the feeling of being in a box - with startling new ideas - and no one really listens. In essence, these innovators are trying to “measure performance upwards.” “Governance from below” intrinsically measures strategies and customer impact, and applying the concept can significantly improve the overall performance. Moreover, with only “governance from above,” it is easier to measure the output of production than the truly important outcome: what is really making a difference for our customers and therefore for our company. The BOSSA nova approach encourages us to rethink the whole topic of measurement, including an examination of KPIs or OKRs and how to experiment safely.

    Acting together, the components of BOSSA nova create a mindset that empowers everyone to follow their passion and interest and nourish the company’s effectiveness. Knowing how to apply BOSSA nova principles for making decisions jointly with full buy-in can enable you to “lead upwards” without jeopardizing the strengths of “leading downwards.” Moreover, you can achieve higher performance for the company through trust than control. Probing and demonstrating new ideas on a small scale such that the proof cascades beyond the demonstration will enable you to get started on your journey to spreading the agile mind-set company-wide.

    This workshop asks participants to start where they are, explains what it means to probe, and helps them develop strategies and experiments they can use in their own situation to create an environment for high performance and goes beyond what OKRs and KPIs can offer.

  • Added to My Schedule
    keyboard_arrow_down

    Pre-Conf Workshop

    schedule  10:00 AM - 06:00 PM place Jacaranda

Agile Mindset

Tue, Mar 17
08:30

    Registration - 30 mins

09:00
  • Added to My Schedule
    keyboard_arrow_down
    Dave Snowden

    Dave Snowden - Is Mindset yet another agile buzzword?

    schedule  09:00 - 09:45 AM place Mysore Hall

    While it is true to say that people’s attitudes and beliefs are key to implementing an agile project, or Agile in itself, much of the use of the term ‘mindset’ implies a mental model that can be defined and engineered. In this presentation, we will look at how we can measure attitudes within an organization and use multiple small actions to trigger the rapid evolution of organizational culture, so that it can sustain agile developments. Mindset and the alignment-based ideas of some on the Agile movement too often imply creating homogeneous beliefs and values that will lead to full alignment. In practice, this damages resilience and can be dangerous. This presentation will introduce the idea of coherence instead of alignment - the celebration of cognitive and behavioral differences that can align if needed to support the delivery of sustainable solutions.

10:00

    Welcome Address & Agile Mindset Day Overview - 30 mins

10:30

    Coffee/Tea Break - 30 mins

11:00
12:00
  • Added to My Schedule
    keyboard_arrow_down
    Shane Hastie

    Shane Hastie - The Ethics of Agile Coaching

    schedule  12:00 - 12:45 PM place Mysore Hall 1

    Agile Coaching is currently hit and miss – there are no guidelines and standards around what good coaching is and active harm is being done by some unethical coaches. Having a voluntary Code of Conduct will not prevent this from happening but it could raise visibility around what behaviors should be expected of a professional, ethical agile coach.

    In this interactive session Shane presents some ideas around what a Code of Conduct for Agile Coaching could be and draws from the participants areas they feel should be included in such a code.

  • Added to My Schedule
    keyboard_arrow_down
    Oana Juncu

    Oana Juncu - Ego, Power, Fear ... and Leadership

    schedule  12:00 - 12:45 PM place Mysore Hall 2

    Wether you are an Agile Coach, an Agile transformation facilitator or a Scrum Master, did it happen to you to feel frustrated because the change you wanted to see was nat the change that was taking place? Didi you ever think that the values and principles you promoted had not the desired echo? Did you ever felt the pressure to succeed a transformation, while people had other operational priorities? If you are a manager, did you feel excited by a more collaborative way of working, then felt lost because your hierarchy hase the same "old ways" type of expectations form you?

    If you ever felt this way, this session invites you to explore another path toward leadership, a path that I believe helpful either for coaches, facilitators, and managers, the path of the servant leader, who I'd rather call "leader at service".

    The challenge of a "leader at service" posture is the letting go of our own fears, our ego and eventually, our own involvement in power games, therefore we will discover together, from a systemic point of view, how our own fears may reinforce our ego and may push us in group power dynamics. The "Human Element" model created by William Schulz will be used to explore the root causes of fears and how we can address them, and Robert Greenleaf's Servant Leadership principles will be also used as a support

  • Added to My Schedule
    keyboard_arrow_down
    Anna Obukhova

    Anna Obukhova - Biology of Agile Leader

    schedule  12:00 - 12:45 PM place Mysore Hall 3

    Agile Leadership has its unique flavour of natural leadership, when power is not given with a title but taken by a person based on his/her inner abilities. We use Servant Leadership or Powerless Leader to emphasise this difference. If we look deeper into the biology and neuroscience of leadership we might find really unexpected things – that Agile leaders are the ones that are recognised by nature and we unconsciously can select these people from the crowd. How to become this type of person?

    To be an effective Agile leader we need to understand:

    • What makes a leader: Leader-Leader Agile Model

    • The difference between a leader and dominant behaviour, why leaders look younger and more active (on hormonal level)

    • Hormones and neuroscience of a natural leader (with some cases and practice)

    • Leadership differences and similarities of Scrum Master and Product Owner

    • Simple (4 words) yet powerful mindset change to become a natural leader that people will follow

12:45

    Lunch - 60 mins

01:45
  • Added to My Schedule
    keyboard_arrow_down
    Ralf Westphal

    Ralf Westphal - How to Overcome the Addiction to so Called "Technical Debt"

    schedule  01:45 - 02:30 PM place Mysore Hall 1

    Why is the fight against technical debt such an uphill battle? Why is it so hard to nip technical debt in the bud or at least keep it much better under control? If after so many years of the metaphor circulating around in developer circles little has changed, there seems to be an underlying unresolved issue.

    This talk is dedicated to uncovering an inconvenient truth: There is no such thing as technical debt in the first place. Hence fighting it is like fighting against non-existing windmills.

    But what about the deficient code situation the term is referring to. Isn't that all too real and painful? Yes, it sure is. But it should not be called a debt, because it does not accumulate like a financial debt which the term technical debt is alluding to. Rather it's a mess, a mess like that created by any addict.

    Managers and developers thus don't need to learn to manage just another form of debt. Instead, they need to sober up. They need to get clean. They need to recognise what's happening in everyday software development under deadline pressure as what it is: the behavior of addicts.

    In my talk, I will contrast the signature aspects of debt and addiction. It will become clear and will be supported by the audience's own experience why debt is the wrong metaphor and addiction is a much more fitting notion. And then I'll talk about interventions. How to climb out of the bottomless hole of addiction and get on the track of longterm high productivity.

  • Added to My Schedule
    keyboard_arrow_down
    David Horowitz

    David Horowitz - Stop complaining and start learning! Retrospectives that drive real change

    schedule  01:45 - 02:30 PM place Mysore Hall 2

    Good retrospectives (you know, the ones that actually lead to real change?) rest on three pillars:

    * people,
    * process, and
    * follow-through


    What makes retrospectives so difficult is that if any of these three pillars starts to crack, it's very difficult for the retrospective to be a success.

    Ultimately, getting the right people in the room, utilizing a good process to facilitate the conversation, and following-through on the learning outcomes depend on having an organizational culture that encourages learning, transparency, feedback loops, and continuous improvement.

    If this sounds like your company already, then great! This talk is not for you.

    For everyone else, join me to explore how effective retrospectives can break a downward cycle of disillusionment and malcontent and transform you and your team into engines of learning and growth.

  • Added to My Schedule
    keyboard_arrow_down
    Anjali D leon

    Anjali D leon - Careers in the Age of Accelerations: A Well Crafted Roadmap or A Drunkard’s Walk?

    schedule  01:45 - 02:30 PM place Mysore Hall 3

    The rules of the game have changed! Studies indicate that by the year 2030, half of jobs will be ones that do no exist today and half the jobs of today will no longer exist. The volatility, uncertainty, and ambiguity ushered in by this age of accelerations extends not just to our environment, politics, and communities, but our organizations as well. In response, organizations are undergoing a massive transformation in technology, structure, culture, and values - fundamentally changing not only what we work on, but how we work, and who we work with.

    Where does this leave our careers? If answering the question ‘Where do you see yourself five years from now?’ leaves you stuck, uncertain, confused and/or anxious, you are not alone.

    Join me for “Careers in the Agile of Accelerations”. During this workshop, we will look back at your career and look ahead at organizational and cultural trends, and understand the skills and capabilities for new and emerging roles. Build the awareness and confidence to take control and navigate a career aligned to the future of work and guided by your Ikigai (reason for being).

  • schedule  01:45 - 02:30 PM place Magnolia

    What does agile have to do with psychotherapy? It turns out quite a lot. If you think about it, ultimately agile is about working closely with people and working closely with people requires our understanding of each other. That's where psychotherapy comes in. Psychotherapy is the science and art of working well with each other, of understanding ourselves and the other person at a deeper level. I hold a masters in clinical psychotherapy (MSW) from New York University and have worked with 5000+ clients to provide coaching/advisory. As a startup founder, I also have hands on experience of applying agile methodologies at my startup. I combine all of that knowledge and experience in this interactive session to cover concepts such as empathy, self limiting beliefs and cognitive biases and how it impacts us and our teams.

    Join me for a fun session that is designed by drawing from the latest brain science research to help you learn effectively through interactivity and activities.

    By the end of the session, you'll have a clear picture of the importance of concepts like empathy, self-limiting beliefs, systems thinking and cognitive biases and their significance in individual and team performance.

    And you won't just learn concepts, you'll take back concrete ideas to implement in your teams starting the next day!

02:45
  • Added to My Schedule
    keyboard_arrow_down
    Yasunobu Kawaguchi

    Yasunobu Kawaguchi - Fun! Done! Learn! - a positive retrospective born in Japan, is this work in your culture?

    schedule  02:45 - 03:05 PM place Mysore Hall 1

    In this talk, the speaker will present a brand new retrospective format quickly becoming popular in Japan. This method is heavily influenced by Japanese culture, but it may work great in other cultural contexts. We are looking for your feedback.

    Someone said Agile is not work in Asian Culture ( https://www.infoq.com/news/2016/06/agile-asia/ ).
    One of the difficulties is from retrospectives.

    We found a positive retrospective format better fit for our culture: Fun! Done! Learn!
    After we published the method in a blog in Japanese, many teams in Japan started using the method. We've not taught or facilitated directly; people just accepted and started using it.
    We'd like to share the method as well as how the teams accepted the technique in Japan.
    We are eager to hear from you whether this works for your team or not and why.

  • Added to My Schedule
    keyboard_arrow_down
    Vishal Prasad

    Vishal Prasad - Why I stopped Coaching Agility and so should you!

    schedule  02:45 - 03:05 PM place Mysore Hall 2

    The story goes ...

    During the Agile Coach Camp at Agile India 2019, we had an interesting discussion driven by Woody Zuill around the concept of Organisational Inertia. This has been a topic of research since the early 80s with the newest research in 2000s as well. The research basically revolves around two aspects:

    1. An organisation's incapability to keep up with major shifts
    2. The resistance towards change

    These don't necessarily stop change from happening but considerably slows down the shift. With organisations struggling to survive in a VUCA world, Organisational Inertia becomes one of the critical factors for consideration. Enter, an Agile Coach! Our industries have heavily invested in them in the recent past and continue to do so in order to help them survive in this VUCA world. Shane Hastie addresses this as the Golden Age of Agile Coaching in which coaches can help the poor souls navigate themselves during a period of turmoil. I respect that.

    But my evil mind links the concepts of Organisational Inertia and the Golden Age of Agile Coaching differently; so during the Agile Coach Camp, I asked folks to run a Thought Experiment which I also mentioned in my talk during Agile India 2019.

    The hypothesis is: "We can deploy Agile Coaches in organisations and hopefully the organisations will overcome their inertia in 10 years to provide a better work experience to their employees. Contrarily, if Agile Coaches cease to exist, organisations may crumble under their inertia in 5 years and the ones left will be great places to work" ... from a Behavioural Economics standpoint, the second option seems better.

    Being a SLICE fundamentalist, I decided to run this hypothesis and began my experiment on 3rd June 2019, the day after I finished my last batch of ICAgile's Agile Coaching training. At the time of submitting this proposal, it hasn't been very long since I started the experiment, and it hasn't been easy to deliberately take a step back from coaching interventions. The observations have been interesting (if not amazing) so far and this is my experience report that I wish to share during Agile India 2020.

    My plan is to run a set of experiments until 31st December 2019 and then decide my way ahead. I mention below the observations so far that I wish to share in my talk but there may be other experiments that I'll share if provided a platform at Agile India 2020.

03:05

    Coffee/Tea Break - 25 mins

03:30
  • Added to My Schedule
    keyboard_arrow_down
    Todd Little

    Todd Little - Feedback Loops are the Key to the Learning Mindset

    schedule  03:30 - 04:15 PM place Mysore Hall 1

    At the core of the agile mindset is learning. Continuous learning is only possible through active feedback loops. Linear approaches do not support learning and are doomed to fail in a world of uncertainty. The key is maintaining healthy feedback loops which incorporate new knowledge which enables learning leading to success. An iterative approach with broken feedback loops is similarly doomed.

    From Todd’s background as a Chemical and Petroleum engineer the idea of feedback and control loops was natural and to a large extent how he got involved in the agile community. Todd will explain the basics of feedback loops and how they can enable agility and learning, or when broken they can destroy agility and enable other behaviors such as organizational politics.

  • Added to My Schedule
    keyboard_arrow_down
    Abhigya Pokharel

    Abhigya Pokharel - Personal Agility - A framework beyond frameworks

    schedule  03:30 - 04:15 PM place Mysore Hall 2

    In today's busy world, you have more things to do, than time to get them done. Deciding upon the priorities is a big question. 'What is important to you, and what is urgent?'

    To be able to reflect upon what is important and discard the things that are of least value to you is an important aspect of being happy and efficient, be it at work or in your personal life. The talk, ‘Personal Agility- A Framework Beyond Frameworks’ will provide you an insight to ensure that you do the right thing at the time. It will help you to focus and rethink on the values to be adapted in everyday life.

    The talk will guide you through the ways to cultivate personal agility from my own experience, where I discovered my own personal agility when I got lost in a jungle in South Australia, few years back. What would you have done then, when you knew that you could not have failed in such an appalling situation?

    I would be mapping these experiences and stories into an Agile Model, with a tint of Tuckman's stages of group development.

  • Added to My Schedule
    keyboard_arrow_down
    Danny Kovatch

    Danny Kovatch - The new era of the Scrum master

    schedule  03:30 - 04:15 PM place Mysore Hall 3

    When the concept of a Scrum master was introduced to the world, it was way too far to digest. Having a coach to a team was a new time that hardly anyone could understand how to implement in a technical world. Even going back one step for being a trainer who train the team was a mission that not all the companies and the team could understand its benefits, so another one step backward was needed to be done to a facilitator. Along the time , more and more teams became more Agile mature hence the role of a Scrum master could have been gained into the right direction to again become the coach of the team.

    If you are frustrated as a Scrum master how to motivate your team, have rare idea how to motivate your team , have no idea what are motivational buttons or are not fabulist with the term intrinsic motivation, the Scrum meetings are considered to be a big waste and you have no clue how to reach the vision (doing nothing while the team is fully self managed), this session was created for you.

  • Added to My Schedule
    keyboard_arrow_down
    Angie Doyle

    Angie Doyle / Talia Lancaster - 3... 2... 1... We have Sprint-Off

    schedule  03:30 - 05:00 PM place Magnolia

    Getting new teams to work together is hard. Really. Hard.

    Is it because there is so much hype around new Agile teams? Or is it because there is such a focus on “doing things right” (or “doing” Agile right), that we forget about the people actually doing the work? Regardless of the reason, before we can change the way people work... we need to focus on the things that are important for teamwork to work!

    We believe that the key to high-performance teams is creating an intentional culture that respects and embraces diversity - whether it be race, gender, class, culture, age, beliefs, language, skills or background. So join us as we explore the Team Canvas – sort of like a Business Model Canvas for teamwork - covering nine essential teamwork elements:

    • Purpose - Why we are doing what we are doing?
    • People & Roles - What are our names, roles, and responsibilities?
    • Common goals - What do we as a group want to achieve together?
    • Personal goals - What do I as an individual want to achieve?
    • Team values - What do we really stand for and believe in?
    • Needs and expectations - What do each of us need to be successful in a diverse team?
    • Rules & Activities - How do we communicate and keep everyone up to date?
    • Strengths & Assets - What skills do we have in the team?
    • Weaknesses & Risks - What are the weaknesses we have, as an individual and as a team?

    During this session, we walk through our agenda for team lift-offs, facilitation posters and preparation work required, materials needed, and facilitation tips and tricks. All packaged in a handy pocket guide, that you can use to explore tried and tested techniques for each essential element. You also have an opportunity to practice some of these techniques during the session.

    Get ready to lift-off your team in T-minus 3... 2... 1...

04:30
  • Added to My Schedule
    keyboard_arrow_down
    Peter Maddison

    Peter Maddison - Applied Coaching Practices

    schedule  04:30 - 05:15 PM place Mysore Hall 1

    This talk is about my journey to become an ICF certified coach and how I apply those skills both to my role as a strategy consultant and business leader.

    Coaching is a powerful discipline that differs from mentoring, teaching and consulting. Applied correctly it can help you have better, more powerful conversations and allow you to overcome difficult challenges.

    I'll talk through the skills what I learned and where they align and differ from Agile coaching practices.I'll talk to the most powerful tools I learned that I now apply to all my work such as logical levels. Throughout this, I'll do a couple of simple exercises for the audience to take with them and use.

    These skills are valuable to people at every level of the organization and equally, can be applied to all aspects of your life.

Design Innovation Day

Wed, Mar 18
08:30

    Registration - 30 mins

09:00

    Keynote by Jeff Patton - 45 mins

10:00

    Welcome Address & Design Innovation Day Overview - 30 mins

10:30

    Coffee/Tea Break - 30 mins

11:00
12:00
  • Added to My Schedule
    keyboard_arrow_down
    Jacob Singh

    Jacob Singh - Agile Data Governance: Balancing Freedom-to-measure-anything with Consistency and Reliability

    schedule  12:00 - 12:45 PM place Mysore Hall 1

    How do you allow teams the freedom to pollute the data lake, and protect the security, privacy, sanity and usability of data?

    Giving teams the power to choose what they measure means giving them the power to drive org-wide changes.

    Gatekeeping through Data engineering is too slow and centralized.

    Totally DIY, you can't control costs, privacy or integrity.

    This talk will cover both the organizational and technical structures we use at Grofers to enable agile data governance and analytics in a team of over 300 in tech and analytics.

  • schedule  12:00 - 12:45 PM place Mysore Hall 2

    Traditional accounting methods measure and manage innovation efforts but this can in fact be one of its biggest disablers. Internal funding systems and the way performance and progress get measured, demand us to make up facts that can not possibly be predicted far into the future. In return, it all too often makes us build the wrong thing. How can Return on Investment (ROI) calculations, for example even be close to true when the product and even the market doesn't yet exist?

    The problem with innovation of course is that we have little to no historical data these approaches heavily rely on. Further, current systems don’t account and adjust for all the new learnings a team gathers. They simply don’t enable honest conversations between those that build products and those that make investment decisions. It leads many people to make up fiction and hide risky assumptions in order to get funding. Many times the best storytellers and politicians get funded, not necessarily those with the best ideas. As a result, organisations fall into the trap of not making corrections early enough before, all too often, the budget is used up before reaching success or ends up with a zombie product on life support.

    Innovation Accounting fundamentally ties learning and money together. It bridges the gap between product and finance. It allows for an honest and effective approach to creating, delivering and capturing value.

12:45

    Lunch - 60 mins

01:45
  • Added to My Schedule
    keyboard_arrow_down
    Anjali D leon

    Anjali D leon - Build the Right Thing with a Formalized Discovery Process

    schedule  01:45 - 02:30 PM place Mysore Hall 1

    Do you have a nagging feeling that you may not be investing in building the right thing?

    Do your products have features that are rarely or never used? Does it takes your organization the full investment of building and launching a product to validate an idea? Is your organization challenged with striking the right balance between the demands of a scalable, high-quality product and innovating on the most compelling problems and opportunities for your customers?

    At Pearson Online & Blended Learning, we met these challenges head-on by creating and implementing a framework that includes early collaboration within a multi-disciplinary team and a light-weight process. Based on Design Thinking principles and practices, the framework effectively balances discovery and delivery efforts. It ensures that, across the portfolio, our investments are focused on the right things, and the efforts of our delivery teams are aligned to solving the most important problems for our customers and addressing the most valuable opportunities for our business.

    In this interactive session, learn about this discovery framework, our implementation approach, and our triumphs and challenges. Each participant will have the opportunity to reflect on how a similar approach may help them address challenges within their own organizations.

  • Added to My Schedule
    keyboard_arrow_down
    Ricardo Abella

    Ricardo Abella - Don’t mix up our stuff!! Empathy Interviews --> Clean Language

    schedule  01:45 - 02:30 PM place Mysore Hall 2

    Design Thinking is one of the best tools available to create products and services with the potential to satisfy people’s needs. Since it is a human-centered process, empathy interviews are the most common technique for collecting data.

    If you want to obtain amazing results, pay full attention and focus on the quality of the information you collect! The more accurate and authentic it is, the more solid and mind-blowing insights you will obtain to guide your ideation phase.

    But be careful! 1) Specialized books and articles have plenty of examples of questionnaires and structured interviews full of leading questions. 2) As interviewers, we tend to contaminate our research with our own metaphors, interpretations, suggestions, mind-reading, references and/or unwarranted assumptions. 3) Interviewees unconsciously look for hidden cues on the questions about how to answer them –conformity, social influence, group pressure.

    Interviewer: “We know change is hard and transitions are always tough. What kind of impact has the new system had? How has this impacted your daily life?” Interviewee: “I thought the new system was awesome, but now that you mention it, it definitely has had a very large impact...”

    Do you want to obtain reliable information? Or more useful and accurate results? Or minimizing the chances of influencing and compromising data authenticity with your bias? CLEAN LANGUAGE is a great tool for this. It’s not a language and it’s not about language; it’s not even about speaking clearly, using fancy jargon or swearing.

    If you want to understand people, how they think and feel, their emotions, passions, frustrations, challenges and dreams, do not miss this workshop. You will have an opportunity to learn, practice and also have fun.

  • Added to My Schedule
    keyboard_arrow_down
    Renesh Moodley

    Renesh Moodley - Hacking the workforce of the future

    schedule  01:45 - 03:15 PM place Mysore Hall 3

    What characteristics does the ideal agile team member possess? How would the needs of the future workforce be addressed if those needs aren’t understood and solved for? My experience of integrating new talent into functioning agile teams has lead me to one, surprising, realisation: Most of the approaches and practices that were used to build organisational teams aren’t working anymore. The tried and tested approaches to team formation and leadership are showing little progress into understanding the mindset of the future workforce. We need radical thinking and action in order to reinvent the way we enable people to communicate, collaborate, and ultimately win as a team. It is up to leaders to mould the culture of organisations to ensure that the future workforce is primed and focused to deliver their best work.

    This session focuses on some of the challenges that present themselves when integrating the future workforce into an agile organisation or team. Ultimately, every organisation that is concerned with future proofing their existence must be focused on building teams of motivated individuals that can build the products and services of the future without the constraints we recognise today.

  • Added to My Schedule
    keyboard_arrow_down
    Jutta Eckstein

    Jutta Eckstein / John Buck - Don’t Fail Fast - Learn fast: Failing fast is an option. But innovating fast is a must

    schedule  01:45 - 03:15 PM place Magnolia

    Often in agile working environments, people aim for failing fast. Yet failure is not the goal - learning is. Failure can lead to learning and so can other approaches. It can lead beyond continuous improvement to transformative learning: seeing your situation from a whole new framework in a way that lets you learn by leaps of insight.

    In this workshop we present specific ways to probe, using hypothesis, and experiments will help you and your team to learn fast. This approach provides a way to get into the mindset of learning and thus always developing.

    Usually a failure is to do nothing… or to do anything (blindly). The key even for big issues is to make small bets (hypothesis) and learn through experiments what's the impact. So, gain insights by (in)validating the bet. In summary it's about thinking big but acting small (and safely). Note, that every great idea, every innovation is at first a guess or rather a hypothesis and only experiments allow us to find out if our idea is really as great as we thought at first.

02:45
  • schedule  02:45 - 03:30 PM place Mysore Hall 1

    Any organization’s ability to focus on what matters most to their customers is directly related to their ability to get valuable feedback from them. While more and more organizations embrace agile practices during the development of their services, they often lack in how they collect feedback and therefor don’t get the benefits they are after. After all, what is the upside to investing in being able to pivot, if there is no information available to guide the direction of that pivot?

    The fact that many roadmaps leave little room for flexibility significantly contributes to this and building powerful roadmaps is a really hard task. How does one get feedback about a house without building it completely? How does one give feedback about a car without being able to drive it around the city for a couple of hours?

    This session will provide you with practical techniques on how to build a powerful roadmap for your product or service, one that allows any organization to get valuable feedback from their customers. The session is based on ideas from the draft book Powerful Roadmaps.

03:30

    Coffee/Tea Break - 30 mins

04:00
  • schedule  04:00 - 05:30 PM place Mysore Hall 3

    This Workshop will help you understand why emotional culture matters to building a more high performing and connected team in a more human and empathetic way.

    One of the lesser known and least discussed parts of organisational culture is the emotional culture of an organisation. Research shows the way people feel at work (or the way they don’t feel) has a significant impact on the way they behave, motivation, commitment, creativity, satisfaction, decision making and collaboration.

    In this highly interactive workshop, we will provide you with a way to bring your teams together to talk about the emotional culture of your organisation. We will learn how we explore both those emotions that your employees want to feel to be successful and those that they don't want to feel. From here, you, as a leader but also as a team, can decide what behaviours you want to support and cultivate and what you need to avoid and manage to create the culture you want.

    So far we have run tens of emotional culture workshops, and the results have been stunning. We provide you with a facilitation framework, which can be used with leaders, teams and individuals to talk about emotions and culture in the workplace. It gives people the freedom to participate, be vulnerable and share what they feel and how they want to feel, allowing your people and leaders to take actions and genuinely start to shape the culture.

    Unfortunately, most companies pay little attention to how their people are or should be feeling at work. Many organisations don't support the expression and discussion of emotions at work. Showing emotion at work can be seen as "unprofessional". But emotion drives human behaviour. So come and learn about why emotion matters to your teams and how you can have conversations about emotions and their impact on your teams in a new, fun and engaging way.

  • Added to My Schedule
    keyboard_arrow_down
    Ralf Westphal

    Ralf Westphal - Slicing - Requirements Analysis with the Developer in Mind

    schedule  04:00 - 05:30 PM place Magnolia

    Starting software development from use cases and user stories sounds great. You get a more structured view of requirements and you get a less pseudo-accurate deliverable to transform into code.

    Unfortunately neither requirements description was invented with developers in mind. Because neither comes with a mapping to code and its structures. Sure, it's just requirements, not designs. But still... How to move on towards code from a use case or a user story? The developer is pretty much left alone with that. Also requirements easily get dissolved in code like sugar in a cup of tea: the code's capabilities are increased, but there is hardly a link to the specific requirements. That leads to waste of all sorts and negative effects: meetings, overengineering, bugs, conflicts, false promises, overconfidence...

    What makes developers happy, on the other hand, are scenarios like they get presented in coding dojos: clear, focused, close to code.

    In my talk I'll present a lightweight, framework rooted in Agile thinking for processing requirements from broad/comprehensive to narrow/detailed in a way so that the subsequent creation of designs and code is well supported. You'll learn simple criteria for "good" requirements - and what to do when they are not "good" (yet). And you'll get acquainted with a "language" you can use with users/POs to drill down into requirements while getting hints for design and implementation. This is satisfying for both sides: developers feel valued with their background leading the process and produce tangible starting points for further development, users/POs feel understood and guided through a process of incremental refinement of their ideas.

    Requirements engineering is a vast subject. But in the end it all boils down to: Does a developer understand where to start implementation or where to change code? And maybe even, how is incremental software development possible?

    Use cases and user stories might be a good starting point, but their shortcomings in programmer guidance should be compensated. Users/POs and developers need to meet on eye-level.

DevEx and DevOps Day

Thu, Mar 19
08:30

    Registration - 30 mins

09:00

    Keynote by Michael Nygard - 45 mins

10:00

    Welcome Address & DevEx/DevOps Day Overview - 30 mins

10:30

    Coffee/Tea Break - 30 mins

11:00
  • Added to My Schedule
    keyboard_arrow_down
    Adam Tornhill

    Adam Tornhill - A Crystal Ball to Prioritize Technical Debt

    schedule  11:00 - 11:45 AM place Mysore Hall 1

    The technical debt metaphor has taken the software world with storm. No wonder, since software projects have their fair share of challenges. Most organizations find it hard to prioritize and repay their technical debt. The main reason is due to the scale of modern systems with million lines of code and multiple development teams; No one has a holistic overview. So what if we could mine the collective intelligence of all contributing programmers and start to make decisions based on data from how the organization actually works with the code? This session introduces one such approach with the potential to change how we view software systems.

    In this session, you'll get an introduction to techniques that help us uncover both problematic code as well as the social dimension of the teams that build your software. The techniques are based on software evolution and findings from various fields within psychology. This combination lets you prioritize the parts of your system that benefit the most from improvements, detect organizational issues and make practical decisions guided by data. Each point is illustrated with a case study from a real-world codebase.

  • Added to My Schedule
    keyboard_arrow_down
    Prima Virani

    Prima Virani - Security Practices for Developers

    schedule  11:00 - 11:45 AM place Mysore Hall 2

    Effective organizational security is a shared responsibility and yet, a big number of organizations suffer from testing security issues at the last minute or not at all. In this talk, we discuss secure best coding practices for developers to improve an organization’s security posture.

  • Added to My Schedule
    keyboard_arrow_down
    Renesh Moodley

    Renesh Moodley - Devops = Culture + Ownership + Empowerment

    schedule  11:00 AM - 12:30 PM place Mysore Hall 3

    The three spheres of a DevOps adoption being Culture, Processes and Tools are fundamental to any organisation. The focus on tools often supersedes any work being done at the process levels and almost always, the culture aspect is 'ignored'. Through my years of helping teams adopt agile and eventually pursue DevOps, I've identified certain patterns that address the varying levels of change that are needed by a team pursuing Agile Ways of Work.

    In this talk, I'll highlight the most important patterns that are needed along with suggestions to help embed these patterns. We'll utilise Value Stream Mapping, A4 Problem Solving and Team Skill Coaching as patterns for helping a team adopt DevOps thinking. I will be using the DevOps radar (from SAFe) as a guidepost for patterns to get an organisation moving towards the promised land.

    Whilst there isn't an 'endpoint' for a DevOps adoption, these patterns reflect milestones on a DevOps transformation roadmap and serve as a possible ‘quick start’.

    NOTE: This is not. A SAFe pitch or SAFe sales workshop. The DevOps radar can be used, regardless of the presence of SAFe.

  • Added to My Schedule
    keyboard_arrow_down
    Dana Pylayeva

    Dana Pylayeva - DevOps Culture Simulation (with Lego and Chocolate Game)

    schedule  11:00 AM - 12:30 PM place Magnolia

    Organizations today can no longer afford to deliver new features to their respective markets once a year or even once a quarter. In an attempt to catch up with the competition, they jump start their DevOps journey with the "How", while losing the sight of "Why" and "What".

    Join this tutorial to gain a solid understanding of fundamental principles of the DevOps culture and avoid typical DevOps anti-patterns.

    In this gamified simulation you will become a part of a "large enterprise" and experience how DevOps will help to eliminate silos. You will experience the benefits of cross-training and start adopting systems thinking. You will participate in the debriefing with Liberating Structures and gain valuable insights that can be immediately applied in your organisation.

    The workshop is designed to be equally accessible to technical and non-technical audience alike. It bring together years of practical experience in IT, experiential learning models, elements of game design, Lego, Chocolate, and facilitation with Liberating Structures.

    Engaging, simple and powerful, this workshop is not to be missed.

12:00
  • Added to My Schedule
    keyboard_arrow_down
    Gunnar Grosch

    Gunnar Grosch - Building event-driven serverless applications

    schedule  12:00 - 12:45 PM place Mysore Hall 1

    Serverless applications are usually made up of functions interacting with fully-managed services, so you can develop applications without having to think about servers. This enables us to build applications that scale quickly and reliably based on incoming requests, often in the form of events that go well beyond API requests and scheduled cron job type rules. In the event-driven model, the components communicate with events and that helps you adopt some of the best practices for distributed systems by default. In this talk, we’ll explore what events are, the different types of events available to your serverless applications, where they come from and how to utilize them to build applications that can provide more value to your customers. All of this with a lot of architectural pattern examples.

  • Added to My Schedule
    keyboard_arrow_down
    Peter Maddison

    Peter Maddison - Securing your pipes with a TACO

    schedule  12:00 - 12:45 PM place Mysore Hall 2

    TACO is an acronym I use with clients to help them map controls from their software delivery pipelines to the organizational controls.

    TACO stands for Traceability, Access, Compliance, and Operations.

    The approach consists of a base list of 25 automatable controls that are documented and the control activity, artifacts and SOR identified. After mapping how these controls are handed we map them to the organizational controls and identify any gaps.

    This model allows for the creation of opinionated pipelines and helps create a common understanding across teams as to what is required in order to be secure.

    Taking a TACO approach can be considered a part of implementing a DevSecOps program and I’ve used this approach at multiple banks. I’ve given the base talk at three conferences and multiple times to internal teams. It helps build organizational confidence in the automation of software delivery.

    During the talk, I’ll run through the different categories of controls, how they are implemented, what the purpose of them is, how to create robust feedback loops for controls such as SAST and how to handle long-running processes such as DAST.

    Content is fairly high level but I can dig into specifics of each given area as questions arise.

12:45

    Lunch - 60 mins

01:45
02:45
  • Added to My Schedule
    keyboard_arrow_down
    Karthik Gaekwad

    Karthik Gaekwad - 10 years of DevOps- Where are we today?

    schedule  02:45 - 03:05 PM place Mysore Hall 1

    Happy birthday, Devops- you are officially ten years old this year!!! Let’s blow out the candles on our cake, and reflect on our devops journey!

    This session will cover the evolution of devops over the past ten years, and talk about the initial idea, the growth of devops, to the state of the world today! You will leave with an understanding of the different successes that it has provided for organizations, the challenges that devops faces today, and where devops might be in another ten years.

  • Added to My Schedule
    keyboard_arrow_down
    Katy Sherman

    Katy Sherman - Agile in Legacy Apps - Mission Impossible?

    schedule  02:45 - 03:05 PM place Mysore Hall 2

    How many times did you hear: legacy systems are not a good fit for Agile transformation? Have you ever said it yourself? I want to tell you a story of a digital transformation in Premier to prove you wrong. Agile is not only a great fit for the legacy applications, it an absolute business necessity, because how else can you provide incremental value for hundreds or thousands of users through a flexible adjustable roadmap?

    My story is not going to be about an immediate success. We've had our fair share of problems, challenges, and small failures. "Legacy" means "old". It means - outdated technology stack, messy dependencies, code that nobody understands, manual testing, manual builds, manual deployments, redundant features. Also, customer issues, bugs, performance issues, scalabiity concerns. Wait, did I mention dependencies?

    Come to the session if any of this sounds familiar, if you're afraid of starting the Agile transformation, or if your company already went through a number of initiatives but the old habits die hard. I will share the valuable lessons we've learned from our experience, the strategies to apply to make the changes stick, as well as the anti-patterns to watch for.

  • Added to My Schedule
    keyboard_arrow_down
    Shripad Agashe

    Shripad Agashe - The myth of perfect abstractions

    schedule  02:45 - 03:05 PM place Mysore Hall 3

    Deriving abstractions for a given problem description is always challenging. No matter what your experience level is, a new scenario will always be challenging to model. At the core of the problem is something known as "Inverse Problem" i.e. it is often easy to observe abstractions in hindsight than in foresight.

    The modeling that we do,deals with IT systems and people operating those systems. What transpires from it is that the observed behaviour of a system is always a reflection of interference of multiple responsibilities of that system. To give an example, a lock is a lock because of the key. Should we lose the key, the lock is just another dead weight. So when we verbalize lock, certain properties come to our mind and weight is not one of them. But the properties that we perceive as properties of a lock are indeed interactions between a lock and a key.

    It is very easy to extrapolate the lock example for unknown scenarios. In such cases we struggle because we have no clear idea about the underlying components and their interactions. So our best attempts are guess work. And if it works for scenarios at hand, we should stop generalizing. By extension of this argument, we can see that we should not strive for universal abstraction but try and model based on certain heuristics and create a workable domain and leave our abstractions incomplete. At the same time, we should have the humility to accept that our abstractions may be wrong but we should be ready to change them if such a need arises.

    To conclude, in the session, I want to highlight difficulties faced in creating abstractions and how to cope with such difficulties. This is useful from developers to system architects and even CTOs to some extent.

03:05

    Coffee/Tea Break - 25 mins

03:30
  • Added to My Schedule
    keyboard_arrow_down
    Vilas Veeraraghavan

    Vilas Veeraraghavan - Walmart's Continuous Deployment Journey using Concord - Delving into the successes, failures and learnings

    schedule  03:30 - 04:15 PM place Mysore Hall 1

    This talk will focus on Walmart’s home-grown open sourced solution for all workflow orchestration needs - "Concord". We will discuss the extremely rewarding continuous deployment journey that we undertook at Walmart that led us down the path of creating Concord. We will dissect some key successful case studies that Concord helped us solve at Walmart scale. In addition, we will talk about the various challenges we faced and continue to face during our journey and how the fast-changing industry landscape (with respect to continuous delivery of software) influences our growth inside Walmart.

    You will be able to understand:

    • How we deal with challenges at Walmart scale
    • Why we chose to open source our solution
    • How we enable a complete CD cycle using Concord
    • How Concord empowers deployments in a hybrid cloud model
  • Added to My Schedule
    keyboard_arrow_down
    Anand Bagmar

    Anand Bagmar - Visual Validation - The Missing Tip of the Automation Pyramid

    schedule  03:30 - 04:15 PM place Mysore Hall 2

    The Test Automation Pyramid is not a new concept.

    Test Automation Pyramid

    The top of the pyramid is our UI / end-2-end functional tests - which simulate end-user behavior and interactions with the product-under test.

    While Automation helps validate functionality of your product, aspects of UX validations can only be seen and captured by the human eye and is hence mostly a manual activity. This is an area where AI & ML can truly help.

    With everyone wanting to be Agile, make quick releases, the look & feel / UX validation, which is a slow, and error-prone activity, quickly becomes a huge bottleneck. In addition, with any UX related issues propping up cause huge brand-value and revenue loss, may lead to social-trolling and worse - dilute your user-base.

    In this session, using numerous examples, we will explore:

    • Why Automated Visual Validation is essential to be part of your Test Strategy
    • Potential solutions / options for Automated Visual Testing, with pros & cons of each
    • How an AI-powered tool, Applitools Eyes, can solve this problem.
  • Added to My Schedule
    keyboard_arrow_down
    Ralf Westphal

    Ralf Westphal - TDD 2.0 - Situation-Aware Programming

    schedule  03:30 - 05:00 PM place Mysore Hall 3

    Are you "doing it" the TDD way? Really? Are you getting the results from TDD as you expected? Yes? Great, check out one of the other exciting sessions at this conference.

    No? Then: How come? Isn't TDD supposed to be easy? Just do the red-green-refactor dance and all code's gonna be functional plus clean.

    Sorry, but I beg to differ. It's not that simple. And there are many reasons for that as I'll show you in this talk.

    My main objection is, that TDD as it's commonly explained and demoed, is ignoring the plain and simple reality of problems being of very, very different difficulty. Or have you ever seen a TDD demo beyond the usual code kata exercises like "Fizz Buzz" or "Game of Life"?

    Hence in this talk I want to present a bigger picture. I'll classify programming situations according to the Cynefin framework and put TDD in perspective. It will become clear where TDD might be a good fit and why - but also, where TDD is overtaxed.

    And since TDD is only a fit for a small subset of problems, of course alternative approaches to test-first programming will be presented.

  • Added to My Schedule
    keyboard_arrow_down
    Todd Little

    Todd Little - Exploring Little’s Law

    schedule  03:30 - 05:00 PM place Magnolia

    Little’s Law is an elegant explanation of the relationship between throughput, WIP, and cycle time. In a stable environment it gives us a good understanding of the performance of the system. In this workshop we explore Little’s Law through theory and the experience of simulations. You will come away with a better understanding of Little’s Law and the core assumptions necessary for it to be applicable and useful in forecasting. Through the simulation we will experience why estimation of individual items is often not necessary in an environment where Little’s Law applies.

04:30
  • schedule  04:30 - 05:15 PM place Mysore Hall 1

    Elevator Pitch

    Extreme programming can transform even the most bureaucratic organizations. Matt Kleiman has spent 2 years enabling the US Military to build lean products. Matt thrives on these agile teams despite having ADHD. In fact, his neurodiversity is an asset in these collaborative, high-stakes environments.

    Summary

    For years Matt Kleiman’s Attention Deficit Disorder (ADD) and other learning disabilities deterred his success on traditional software development teams. Working alone, on globally distributed teams, and on amorphous tasks, Matt found himself struggling to meet the expectations of a software engineer. In an endless showdown against distractions, Matt almost gave up on his career.

    This is the story of how Pivotal Labs’ Extreme Programming practices not only have the ability to transform bloated, slow-moving enterprise software development teams but also have the power to promote inclusive and neurodiverse groups of software engineers. Matt’s journey to find a workplace that nourishes his strengths has taught him the value of bringing neuroatypical individuals together to form teams that benefit from broad and divergent thinking.

  • Added to My Schedule
    keyboard_arrow_down
    Nikhil Barthwal

    Nikhil Barthwal - Managing Modern Serverless Workloads Using Knative & Cloud Run

    schedule  04:30 - 05:15 PM place Mysore Hall 2

    This introduces Knative & Cloud Run and shows how they can be used to run modern serverless workloads. Knative is a reference API &
    implementation and Cloud Run is a product built on the Knative specification.

    Knative is a Kubernetes-based platform to build, deploy, and manage modern serverless workloads. It provides a set of middleware
    components that are essential to build modern, source-centric, and container-based applications. Knative components are built on
    Kubernetes and codify the best practices shared by successful real-world Kubernetes-based frameworks.

    Cloud Run is a managed compute platform that is built upon Knative that automatically scales your stateless containers. Cloud Run
    is serverless: it abstracts away all infrastructure management. It is compatible with Knative, letting you choose to easily run
    your containers either fully managed with Cloud Run, or in your Google Kubernetes Engine cluster with Cloud Run on GKE.

05:30
  • Added to My Schedule
    keyboard_arrow_down
    Shama Ugale

    Shama Ugale - Testing Conversational AI - Stragegy to Automation

    schedule  05:30 - 06:15 PM place Mysore Hall 1

    Last year was dominated by the smart devices and voice based home assistants. These use the conversational interfaces unlike other application to interact with. They are built using advanced algorithms, ranging from pattern and expression matching engines to natural language processing and AI/Machine learning techniques. These systems are constantly learning by themselves improving the interactions with the user bringing up the challenge in the testing world of non-deterministic output. To such interfaces, natural language is the input and we humans really love having alternatives and love our synonyms and our expressions using emojis gifs and pictures. Testing in this context moves to clouds of probabilities.

    In this session I will cover the strategy for testing such interfaces, testing the NLP models and sharing experience on how to automate these tests and add it to the CI/CD build pipelines.


    Key learning:
    * How What and why of a conversational interface?
    * How can I build my testing approach for such an interface?
    * What from my current tool set can I use for this new context?
    * How do I automated and add it for my CI/CD pipeline for instant feedback?
    * How do I measure the quality?

  • Added to My Schedule
    keyboard_arrow_down
    Saurabh Nanda

    Saurabh Nanda - Property-Based Testing - Examples of Properties from Business Applications

    schedule  05:30 - 06:15 PM place Mysore Hall 2

    I got excited about property-based testing after hearing John Hughes talk at Functional Conf 2016. I tried it that year with QuickCheck, but failed miserably (it almost derailed the entire project delivery). I cribbed about it in my talk at Functional Conf 2017. In 2018, Srihari's talk got me excited again. This time, I tried with Hedgehog, and got it to work!

    This talk is about this journey and its learnings. We'll talk about how Hedgehog was used to test [1]:

    • A Postgres backed task/job queue
    • A small Wai/Servant based webapp

    And no, we will not talk about the most common (and completely useless) example of reversing a list!

    [1] Both of these are part of an open-sourced task/job queue library.

Chaos Engineering Day

Fri, Mar 20
08:30

    Registration - 30 mins

09:00

    Keynote - 45 mins

10:00

    Welcome Address & Chaos Engineering Day Overview - 30 mins

10:30

    Coffee/Tea Break - 30 mins

11:00
  • Added to My Schedule
    keyboard_arrow_down
    Vilas Veeraraghavan

    Vilas Veeraraghavan - Measuring the cost and tracking the effectiveness of a high-impact Chaos Engineering program

    schedule  11:00 - 11:45 AM place Mysore Hall 1

    The practice of Chaos Engineering has established the importance of running resiliency experiments in cloud-native application ecosystems. As the field of Chaos/Resilience Engineering has matured and attained widespread adoption, a need has emerged for engineering organizations to quantify the costs of running such a program. Additionally, sustained investment in any long-running program will require metrics (KPIs) to show effectiveness to Executive Leadership.

    In this talk, we will discuss the setup, running and maintenance stages of a high performing Chaos/Resilience engineering program irrespective of the size of the organization. We will analyze the key metrics that should be tracked along with the optimum cadence of chaos exercises. Also, with the rapid advancement of CI/CD tools and cloud deployment technologies, we look at enhancing the impact of chaos engineering by deep integration into the continuous deployment pipeline.

  • Added to My Schedule
    keyboard_arrow_down
    Aaron Rinehart

    Aaron Rinehart - Security & Chaos Engineering: A Novel Approach to Crafting Secure and Resilient Distributed Systems

    schedule  11:00 - 11:45 AM place Mysore Hall 2

    Modern systems pose a number of thorny challenges and securing the transformation from legacy monolithic systems to distributed systems demands a change in mindset and engineering toolkit. The security engineering toolkit is unfortunately out-of-style and outdated with today's approach to building, security and operating distributed systems. The speed, scale, and complex operations within microservice architectures make them tremendously difficult for humans to mentally model their behavior. If the latter is even remotely true how is it possible to adequately secure services that are not even fully comprehended by the engineering teams that built them. Security Chaos Engineering helps teams realign the actual state of operational security as well as build confidence that their security actually works the way the think it does. Chaos Engineering allows for security teams to proactively experiment on recurring incident patterns to derive new information about underlying factors that were previously unknown by reversing the postmortem and preparation phases. This is done by developing live fire exercises that can be measured, managed, and automated. It develops teams by building a learning culture around system failure to challenge engineering teams to proactively, safely discover system weakness before they disrupt business outcomes. In this session we will introduce a new concept known as Security Chaos Engineering and how it can be applied to create highly secure, performant, and resilient distributed systems.

  • Added to My Schedule
    keyboard_arrow_down
    Gunnar Grosch

    Gunnar Grosch - Performing Chaos in a Serverless World

    schedule  11:00 - 11:45 AM place Mysore Hall 3

    The principles of chaos engineering have been battle-tested for years using traditional infrastructure and containerized microservices, but how do they work with serverless functions and managed services? In this session we'll cover the motivations behind chaos engineering, how we perform chaos experiments, what some of the common weaknesses we can test for in our serverless applications are and run some actual experiments in a serverless environment. Join as we move from talking about principles to performing real chaos engineering experiments for serverless!

12:00
  • Added to My Schedule
    keyboard_arrow_down
    Adam Tornhill

    Adam Tornhill - Meet The Social Side of Your Architecture

    schedule  12:00 - 12:45 PM place Mysore Hall 1

    Software projects often mistake organizational problems for technical issues and treat the symptoms instead of the root cause. The main reason is that the organization that builds the system is invisible in our code. From code alone, we cannot tell if a module is a productivity bottleneck for five different teams, or whether our microservice boundaries support the way our codebase evolves or not. This session closes that gap by taking a behavioral view of code combined with insights from social psychology to measure aspects of software development that we haven't been able to capture before. You learn how this information lets you detect modules with excess coordination needs, measure how well your architecture supports your organization, as well as why Conway's law is an oversimplification. To make it specific, each point is illustrated with a case study from a real-world codebase.

  • Added to My Schedule
    keyboard_arrow_down
    Lyndsay Prewer

    Lyndsay Prewer - Embracing collaborative chaos - running Chaos Days on large platforms

    schedule  12:00 - 12:45 PM place Mysore Hall 2

    Today’s systems are inherently complex, with some component parts often operating in or close to suboptimal or failure modes. Left unchecked, as complexity increases, the compounding of failure modes will inevitably lead to catastrophic system failure. Chaos Days help us address this risk by spending time deliberately inducing failures, then analysing the response.This session summarises our experience of running Chaos Days on a large scale platform. We’ll explore the what, why, how and when of running a Chaos Day.

    As engineers we spend a lot of our time thinking about how best to shield our clients and customers from the risks inherent in the systems we build. We ask ourselves “what’s the worst that could happen?” – and work hard to mitigate the risk. A common risk in most systems, particularly distributed ones, is the unexpected failure of a component part. As a system’s complexity and its number of subsystems grows, so does the likelihood of a subsystem failure. Subsystem failures can compound in such a manner that catastrophic system failure becomes a certainty. The only uncertainty is when the system will fail.

    Chaos Engineering addresses the risks inherent in distributed systems that stem from unexpected component failure. It does so by running experiments that explore the impact of sub-system failures by deliberately inducing different types of failure in different components. Outcomes are then analysed and learnings applied to improve the system’s resilience. These learnings deepen our understanding of the system and its failure modes, which aids the identification of new failure scenarios. This feedback loop informs subsequent rounds of experimentation, and thus the cycle repeats. In addition, planned failures provide a safe environment for teams to improve their incident response and how they conduct subsequent postmortems.

    Chaos experiments can take many forms, ranging from continuous, automated failure injection (made famous by the Netflix Chaos Monkey), to one off Chaos Days (similar to Amazon’s Game Day), where disruption is manually instigated. Chaos engineering is similar to the ethos of “building quality in”: it’s a mindset, not a toolset: you don’t need to be running EKS on AWS to benefit from being curious about failure modes and how to improve a system’s resilience towards them. It just requires a focus on “building resilience in”.

    This session shares our experience of running Chaos Days over the last year, with one of our clients – a major Government department that hosts around 60 distributed, digital delivery teams. These teams design, deliver and support hundreds of microservices that serve online content to the department’s varied customers.

    The microservices all run on a single platform, itself run by seven Platform Teams that take responsibility for distinct areas (infrastructure, security and so on). Inspired by the Netflix Chaos Monkey and Amazon’s Game Day, the Platform Teams have planned and executed several Chaos Days – to see just how well they and the Platform coped when everything that could go wrong, does go wrong.

  • Added to My Schedule
    keyboard_arrow_down
    Prima Virani

    Prima Virani - Building Resilient Security Log Pipelines with Chaos

    schedule  12:00 - 12:45 PM place Mysore Hall 3

    Chaos Engineering is an up and coming method used by SREs for autonomously introducing random failures into a system and measuring whether the service degrades or fails. This talk discusses how security teams can use Chaos Engineering principles to develop, test, and maintain resilient log pipelines.

12:45

    Lunch - 60 mins

01:45

Post-Conf Workshop Day 1

Sat, Mar 21
09:30

    Registration - 30 mins

10:00
  • Added to My Schedule
    keyboard_arrow_down

    Passionate Product Owner by Jeff Patton

    schedule  10:00 AM - 06:00 PM place Magnolia people 1 Interested
  • Added to My Schedule
    keyboard_arrow_down
    Dana Pylayeva

    Dana Pylayeva - DevOps Simulation Certified Trainer

    schedule  10:00 AM - 06:00 PM place Plumeria

    Unique opportunity to get trained by the author of one of the most effective DevOps Culture simulation, prepare for DevOps Simulation Certified Trainer exam (DSCT) from CertiProf© and gain competitive advantage in DevOps training marketplace.

    First time in India! The latest 2019 version of this popular simulation (ran at 45 conferences in 15 countries).

    This train-the-trainer workshop will prepare you for many successful facilitations of DevOps Culture simulation and give you access to the licensed training material (PowerPoint slides, handouts, flipcharts design etc). You will learn to run effective debriefing with your groups and help them connect learning from the simulation with solutions to the real-life challenges in their organization.

    The simulation is designed for a broad audience, enabling participants to gain the insights into the “Why” and the “What” of the DevOps before jumping into the “How”. Through this powerful role-based simulation, participants experience the benefits of cross-training, learn to eliminate silos, "shift left" on security, adopt systems thinking and practice optimizing the flow of value from business to development and to IT operations.

    Become one of the DSCT holders - DevOps change agents who are able to create the DevOps Culture simulation experience, providing participants with additional insights into taking the next steps to embracing DevOps mindset and leading organizational change. Guide your workshop participants through the experiential discovery of the following practices: optimizing flow, amplifying feedback loop and growing safety culture. Deliver real-life examples from medium to large size organizations, latest findings from the State of DevOps report and key ideas from “The Phoenix Project” by Gene Kim.

    This unique simulation uses cognitive neuroscience principles, game design theory and elements of “Training from the Back of the Room” framework.

    Learn from the game creator, prepare for DSCT exam from CertiProf© (included in your registration) and help make DevOps culture experience accessible to all – business stakeholders, C-level executives, IT management, techies and non-techies alike.

  • schedule  10:00 AM - 06:00 PM place Jacaranda

    Many codebases contain code that is overly complicated, hard to understand, and hence expensive to change and evolve. Prioritizing the technical debt to pay down is a hard problem since there's always a trade-off between improving existing code versus adding new features. In this masterclass, you learn how easily accessible development data let us uncover the technical debt with the highest business impact. The techniques cover both technical and organizational decisions around your codebase, and we cover both traditional architectures as well as microservice architectures where you learn to measure non-code properties like team coupling, system mastery, and detect implicit dependencies between services.

    • Identify the code that's most expensive to maintain amongst millions of lines of code.
    • Put costs on technical debt and assess its delivery impact.
    • Detect architectural decay and learn to control it.
    • Perform architectural analyses of layers and microservices to uncover team coupling and implicit dependencies.
    • Learn refactoring patterns to address technical- and architectural debt.
    • Measure how organizational patterns influence code quality and the link to software architecture.
    • Uncover the social side of your codebase and use data to mitigate off-boarding risks.

    Participants are encouraged to take this opportunity and analyze their own codebases. As part of the workshop, you also get access to CodeScene – a tool that automates the analyses – which we use for the practical exercises. We also look at open-source alternatives, and see how we can use Git itself for data mining; the workshop is not about tools, but rather about the techniques and their applications. This is a new perspective on software development that will change how you view code.

Post-Conf Workshop Day 2

Sun, Mar 22
10:00