location_city Online schedule Sep 23rd 04:00 - 04:45 PM IST place Zoom people 61 Interested

This talk will describe how we can enable the businesses to manage software engineering efforts at scale in a financially sound way, all the while dealing with multiple projects/products or value streams, multiple events or deadlines, multiple stakeholders and multiple teams.

It will show how to resolve the conundrum of dependency management at scale by collapsing the combinatorial explosion of dependency networks into a simple linear queue.

It will describe how to instrument the organization in order to raise leading signals of oncoming trouble in order to trigger intense, frequent and engaging collaboration between all players (business and engineering), leading to an environment that unleashes the organization's collective intelligence via co-creation and social learning.

The talk will highlight techniques employed to foster intense collaboration between engineering and business, at scale.

It has been employed, among others, in a case in the automotive industry involving an organization with 8.000 people, half of which in 120 engineering teams distributed globally across the world, dealing with on average 400 projects in process at any time, and 70,000 change requests per month. The focused approached allowed the organization to improve it's operational throughput by 40% in a matter of months after inception.

The approach is data driven, and takes into account: Flow metrics, Buffer Burn Rate, Virtual Queue Sizes, Operational Throughput, Financial Throughput, Financial Throughput Rate.

The techniques used are a re-elaboration of the Theory of Constraints, taking elements of Drum-Buffer-Rope scheduling and Critical-Chain Project Management, and combining them with queuing theory and Little's Law.

The metrics and signals produced are also used to trigger collective psychological flow states leading to sustainable and optimal human experience at work.

 
 

Outline/Structure of the Talk

The talk will present the following topics

  • Backgrounder: who is Steve Tendon (3 min)
  • Introduction to the Theory of Constraints (3 min)
  • Economic view of Backlogs (5 min)
  • Balance, separation of concern, and collaboration between business and engineering (5 min)
  • Finding the Constraint in the Work Process (2 min)
  • Little's Law and system stability (2 min)
  • Execution Management via CCPM-Style Buffers (3 min)
  • Finding the Constraint in the Work Flow (7 min)
  • Finding the Constraint in the Work Execution (5 min)
  • Achieving Scalelessness (1 min)
  • Integration with classical Project Management (1 min)
  • Dependency Management (2 min)
  • Psychological Flow States (2 min)
  • Fostering agile interaction and collaboration (2 min)
  • How to get started with the approach: agile bootstrapping expediencies (2 min)
  • Conclusions (2 min)

Learning Outcome

The participants will learn how to manage a scaled software engineering environment with multiple projects/products or value streams, multiple events or deadlines, multiple stakeholders and multiple teams.  

They will gain new tools to manage the backlogs in a financially sound way.

They will be able to confront and master the most complex dependencies, with development or delivery precursors; architectural elements and architectural dependencies; exploratory works; failure demand work.

They will know how to quickly bootstrap the fundamentals of this approach with simple actions at the team level. 

Target Audience

Executives, VP, Directors, Mid-senior management in software engineering organizations; Software engineering managers; PMOs and Project Managers; Product Owners and Scrum Masters; Software Engineers and DevOps Engineers; Agile Coaches/Consultants

Prerequisites for Attendees

This is very advanced talk. The more you know about Lean, Agile, Scrum, Kanban, SAFe and other contemporary methods, frameworks the better. The talk refers a lot to the Theory of Constraints. TOC concepts will be introduced very briefly, but if you already know about them, the better. In particular, previous knowledge of Critical-Chain Project ManagementDrum-Buffer-Rope SchedulingFever ChartsThroughput Accounting will be very helpful. If you have read the Phoenix Project book, you will have a good basis from which to start.

Video


schedule Submitted 5 months ago

  • Simon Copsey
    keyboard_arrow_down

    Simon Copsey - Systems Thinking for Happy Staff and Elated Customers

    45 Mins
    Talk
    Intermediate

    Every organisation has problems to overcome. At first glance they seem daunting: software bugs, financial issues, staff troubles, operational woes.

    However: what if all these problems weren’t disconnected, but actually stemmed from the same underlying cause? What if - by tackling that underlying cause - we could make all those obstacles disappear in one go? And, what if it was surprisingly simple to find that underlying cause?

    This talk draws on the Theory of Constraints and aims to provide you with the tools you need to understand and uproot the cause of complex, cross-functional problems that cause widespread pain and all too often go unaddressed.

  • 45 Mins
    Case Study
    Executive

    "Universal law is for lackeys. Context is for kings." The best practices are the ones that make sense for you. Embracing DevOps culture is not a binary decision. This thinking often leads to inaction. Should we use distributed tracing? Should there be 100% unit test coverage? Should we use Infrastructure-As-Code? We should when the right time comes.

    In this session, we will explore what DevOps practices make sense for companies at different stages operating in different industries, DevOps maturity models, and the role of platform engineering. We will also see how a maturity model was deployed at Blinkit to help teams areas of focus for DevOps maturity.

  • Jorge Luis Castro Toribio
    keyboard_arrow_down

    Jorge Luis Castro Toribio - devops for agile coaching collaborative model

    Jorge Luis Castro Toribio
    Jorge Luis Castro Toribio
    agile coach
    NTT DATA
    schedule 5 months ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    devops for agile coaching collaborative  model

    zurück zum Wesentlichen - back to basics

    In this paper we are sharing our experiences from the trenches about how we as a agilits ( agile coaches, scrum masters, ATFs. and so forth) can support, accelerate and collaborate with DevOps culture and practices adoption through a collaborative-work inverted Y model 

  • Nadezhda Belousova
    keyboard_arrow_down

    Nadezhda Belousova - [Agile] Coaching Agreement as Creative Partnership

    45 Mins
    Talk
    Intermediate

    As an Agile coach, have you ever struggled with managing expectations of your role in the organization? Has magic in any shape or form been implicitly included in your responsibilities or deliverables? Was it expected of you to be “agile” and re-adjust the definition of your coaching activities with each and every shift of operational context? And what’s more, have you ever felt like carrying the weight of the whole Agile transformation on your shoulders?
    Although there may be many heavy-lifting moments and unpredictable turns on the journey of organizational growth and development, there is a way to help you stay firmly grounded in your coaching intent. You can navigate a wide range of situations with more clarity and grace, while nurturing everyone’s commitment to bring change. You can grow trustful relationships and cultivate ownership of development by individual contributors, teams and leaders.
    Join this talk to learn how to establish healthy boundaries, structure coaching priorities and enable self-organization from day one. Whether you’re an external or internal Agile coach, you will get many practical tips on how to effectively (re-)frame your Agile coaching engagements as creative partnerships through the lens of professional coaching agreements.

  • Scott Ambler
    keyboard_arrow_down

    Scott Ambler - The Agile Database Techniques Stack: New Ways of Working (WoW) for Database Development

    45 Mins
    Talk
    Intermediate

    Data, the way that we process it and store it, is one of many important aspects of software-based solutions. Data is the lifeblood of our organizations, supporting real-time business processes and decision making. It is crucial to the success of software development, and to our organization as a whole, that we apply agile and lean strategies to data-oriented activities. Yet for many organizations their data sources prove to be less than trustworthy and their data-oriented development efforts little more than productivity sinkholes. We can, and must, do better.

     

    This presentation begins with a collection of agile principles for data professionals and of data principles for agile developers - the first step in collaborating more effectively is to understand and appreciate the priorities and strengths of the people that we work with. Our focus is on a collection of practices - the "agile database techniques stack" - that enable you to easily and safely evolve databases. These techniques are vertical slicing, clean architecture and design, agile data modelling, database refactoring, database regression testing, continuous database integration, and configuration management. We call them a technique stack because they build upon each other.

  • Priya Malhotra
    keyboard_arrow_down

    Priya Malhotra / Usha Ramaswamy - Hello, I’m Culture…Did you forget me in your transformation journey???

    20 Mins
    Talk
    Intermediate

    Any transformation journey usually has a roadmap that focuses on process, tools, technology and people. Studies have shown that some key reasons why transformations fail are due to cultural aspects. However, culture is often ignored and we expect magic to happen quickly. Hence, a transformation needs to weave in culture shift as a critical part of the roadmap.

    We delve into…

    • What constitutes culture?
    • Why should a transformation look into culture shift?
    • A ‘culture gauge’ as a tool to calibrate the cultural aspects
    • The E3R model as a recipe to plan the culture shift journey
    • The elements of ‘thin slice’ and ‘1% improvement’ as key ingredients

    … we weave in our stories of failure, some good practices and envision how we would use the culture gauge and E3R model.

  • Chris Boys
    keyboard_arrow_down

    Chris Boys - Agile Metrics eat Empathy for breakfast...or do they?

    Chris Boys
    Chris Boys
    CEO
    Umano.tech
    schedule 5 months ago
    Sold Out!
    45 Mins
    Tutorial
    Intermediate

    In modern agile ways of working, team performance is measured by the outcomes of delighting your customer with working software. Data-driven, data-led, data-inspired decisions are increasingly shaping a cultural revolution of fact fuelled delivery. It’s the facts that provide the freedom for hard conversations, decisions and action, right?

    Well, sort of. The facts are only half of the picture. We also need context, narrative and the subjective for deeper understanding and truly being able to unleash your team’s mojo. In short metrics need empathy.

    Metrics and empathy can sometimes be like oil and water. but they can and do make magic when brought together in the right ways.

    In this presentation, participants will get an overview of:

    • the key agile success metrics for team insights into HOW (i.e. behaviours and practices) you design, build, review and engage together

    • tips and techniques that add team context, narrative and voice (i.e. deeper empathy and understanding) to agile success metrics for a complete picture of team performance

  • Thabet Mabrouk
    keyboard_arrow_down

    Thabet Mabrouk - Making agile teams reliable and trustworthy

    45 Mins
    Talk
    Advanced

    A lot of businesses and Customers loose trust on teasm, simply because they don't keep their promises regarding delivering value to them.

    Teams tell the business, we will deliver this next week. The business tell the customer the same. Then the team fails to deliver this for whatever reason. Bussiness and customers starts to have bad tasts.

     

    if this is repeated more than one time, then they will never rely on this team to give them trustworthy estimations or to deliver on time.

    In my talk, I would like to highlight the solution to this problem "Making agile teams reliable and trustworthy"

     

help