We all know what a product is. We buy and use them all the time. But, what does it mean where you work? Why is there so much resistance to creating great products where you work? This talk focuses on how to recognize the mindset that gets in the way of effective product design and development. You may be guilty of the mindset yourself. I know I am. We’ll talk about how to recognize when you, your leadership and the processes you use have slipped into anti-product mode. And, give you ideas on what you can do to fight it.

1. Real Software Engineering, not just about coding, Not ‘CodeFlow’ like some agile methods.

2. Systems (level) Thinking: even for ‘Programs’ you need to integrate people, data, legal, hardware, cloudware and more.

3. Stakeholder Engineering: not merely ‘customer and user’: Stakeholder Stories, Stakeholder Xperience (SX not UX)

4. Simultaneous Multi-Values and Multi-Cost Requirements; as Agile Efficiency Measure, "Agility for Efficiency”.

5. Multi-Value Flow Optimization, Multi-Constraint Consideration.

6. Dynamic Design to Efficiency (Value/Cost): The Architect in the Agile Loop (IBM Cleanroom, Evo)

7. 100X Defect-Prevention from Requirements; using Spec QC + Planguage; at Intel, in practice. (Terzakis)

8. Dynamic Stepwise Priority Computation, based on Efficiency and Constraints. Using Impact Estimation Tables.

9. AI, Web 3.0, Solid, Symantic Triples, Ontology& Digitization. = Very High-Tech Agile Future: Bye Bye Yellow Stickies.

10. Scale-Free Agile methods, as proven big time, at Intel, and other places.

11. Agile Engineering on a small scale (16 Norway Developers, 4 x 4 Teams, at Confirmit, capture international market with dramatic product quality increases)

12. "Principles of Agile Engineering” : Logical Common Sense.

13. μActs: + -> Tailored Practices -> Tailored Methods: BYOM Bring Your Own Method. ‘Essence' and D.A. 

Aren’t we fascinated looking at a gymnast performing a routine? A trapeze artist swinging from one side to the other? An acrobat doing his/her amazing balancing act? But, we know little of the mechanics behind such feats of balance. All this is controlled by the ear and the brain. The semicircular canals of the ear act as a gyroscope and accelerometer to control angular acceleration and to help you decide which plane the head is moving. Unfortunately, millions suffer from various balance disorders.

NeuroEquilibrium™ is a pioneer in the field of vertigo and balance disorders aiming to provide advanced and economical medical assistance to people suffering from these conditions. We are making groundbreaking innovations in this field by developing indigenous vertigo diagnostic systems which operate on cutting-edge technology like 3D Printing, Cloud Computing, VR, AI, etc.

In this talk, we'll share our experience building NeuroEquilibrium.

How to Amplify Creativity

In most disciplines "Engineering" means the stuff that works, an application of scientific reasoning to solving practical problems. In Software, depending on your background, it either means something bureaucratic that doesn't work, or it is just another name for software development. So what are the ideas that we can use as tools to give real, practical advantage in our work in the way that other disciplines achieve? What ideas should we treat as "the tools of our trade" whatever the technology or problem before us? This presentation explores two "tools" that we can use, Testability & Speed.

Welcome Address and Agile India Conf Overview. Here you will get al the important details you need about the conference. So don't miss it.

In this talk, Lynn will share key patterns to successful cloud adoption. She and her virtual teams have worked with clients in AdTech, FinTech and BioTech for the past 11 years. In this work they've observed a number of key patterns which drive enterprises to success with a number of types of cloud projects.

Roadmapping is a flawed concept in the age of Agile. Maps, by their definition, are linear and we don't build linear products and services any more. We build continuous systems. Nevertheless, we have to be able to create and provide some plans for our teams, leaders and customers to set expectations about the ongoing improvements and future of the services we build. How do we communicate that effectively in a continuous world? How do we ensure the voice of the customer is included in these plans?

In this talk, Jeff Gothelf will discuss the concept of outcome-based product planning. Using specific examples and detailed tools, Jeff will show how taking a customer-centric look at product strategy and creating continuously improving plans ensures the teams maintain their agility, customer-focus and ultimately, the success of their product.

There might be more to being a full stack developer than you realize, because you're hampered by the ultimate legacy system: yourself. See the pragmatic approach it takes to succeed at software development despite our own limitations, biases, and accidents of history and complexity. Join Andy Hunt, one of the 17 authors of the Agile Manifesto, as he reveals secrets from The Pragmatic Programmer (the best-selling, most-recommended book on software developer) and Pragmatic Thinking & Learning.

Currently, more and more companies are coming to us with severe problems after implementing SAFe. One or two years before, they bravely implemented SAFe to become agile, and now the outcomes are poor, the costs are rising, and the lead times are not better than before. In this speech, I show the typical root causes and ways out. The keys are concepts out of the Theory of Constraint - a precious source of ideas to improve FLOW to the next level. I'll show especially a simple way to do the Lean Portfolio Management based on the constraint and the "Super" Simplified Drum-Buffer-Rope to get the dependencies and deliveries under control - all to generate FLOW 2.0

What does it mean for an agile team to be predictable? How could you tell how predictable an agile team is or whether they are becoming more or less predictable? Is improving predictability even desirable for an agile team? This talk will explore these questions and more and introduce some different ways of answering them. Attendees will go away with some new approaches and techniques that they might use as part of an agile transformation to assess how successful they are being.

This talk will be based on, and expand on this blog post: https://availagility.co.uk/2021/12/24/how-to-measure-the-predictability-of-agile/

OKRs are a goal-setting, strategy execution tool that involves setting ambitious goals that lead to measurable results. The thing is, over the years, OKRs have gotten too complicated - they need to be put on a diet - and that’s where Lean OKRs step in. They are hyper-focused on one single OKR to rule all others. Often, OKRs are not set up for success and thus tossed aside. I can name four (and a half) common reasons why your OKRs aren’t working. Among them, the importance of finding a rhythm for making OKRs part of your way of working, leading teams with trust, and getting the foundation in place so teams aren’t running before they learn how to walk.

Large-scale agile transformations do not have a good track record with reportedly up to 70% falling far short of their goals.  From a biological perspective,  many agile transformations are like taking a bulldozer to a wild, diverse eco-system.  While we may create a consistent Way of Working, the transformation bulldozer often results in a monoculture,  a weakened ecosystem that cannot adapt and innovate. Of course, to work together, especially at scale, we cannot just let our enterprise eco-system grow wild because we need consistency to collaborate and coordinate. We can resolve this dilemma by taking a page from Socio-Technical systems for a more sustainable transformation.  We introduce five principles for the "Greening" of the Agile Transformation that sustains and grows our capability to innovate while creating needed alignment and consistency.

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.

Are you using release toggles to:

• decouple deployments from releases?
• allow micro-services to be deployed independently as and when they are ready?
  • even if rest of the micro-services required for the feature are not ready
• practice trunk-based development?

If yes, then how are you ensuring that when you need to turn on a release toggle in production, you are doing it in a safe manner? 

This session will explain how you can ensure that your CI/CD pipelines can validate, manage and promote the toggle state in a fully automated manner as part of the deployment process itself. If your teams are embracing zero-touch continuous deployment model, then this session is for you.

Test Flow Charts (testflowchart.com) is a free, no code test automation platform for authoring and executing test cases. In this session we will showcase the automation of a real world open source shopping cart application using Test Flow Charts. We will demonstrate flow chart based test authoring and show how Test Flow Charts automatically sets up data, satisfies test preconditions, auto generates data, performs validations and allows data specific testing. If you are a tester or test automation person, you definitely do not want to miss this.

With 66% of the world using Scrum as their predominant Agile method, this session will open up your eyes to the many other Agile methods and frameworks in the world today. For many, Agile is a toolbox of potential methods, practices and techniques, and like any good toolbox it is often more about using the right tool for the problem that will result in meaningful results. So join us on this rapid journey to look at the universe of Agile approaches and adding some extra tools into your toolkit

You work in an enterprise organisation. You’ve got lots of delivery teams, and a central operations team that does deployments and production support. You need daily or weekly deployments. You need 99.9% reliability, and less than 1 hour to restore. You need a growth mindset, and learning culture.

The good news is you can have it all with You Build It You Run It. It’s an operating model in which on-call product teams build, deploy, operate, and support their own digital services.The bad news is... well, for some, it’s a bit controversial. It’s a 15 year old idea that flies in the face of traditional IT, and still isn’t well understood in enterprise organisations.

You’ll hear:

• How You Build It You Run It can be proven to protect more revenue than it costs
• How developers can be encouraged to try, and even enjoy, being on-call
• How to clearly establish who to hold to account for reliability
• How to build an effective, repeatable incident management process
• How developers can spend most of their time on product features, not fires
• How to balance demand and availability of specialist skills

This talk demystifies You Build It You Run It fears, drawing on experiences from multiple enterprise organisations who’ve successfully implemented on-call product teams. It explains how to simultaneously achieve frequent deployments, high availability, and a high rate of learning across many teams and digital services.

Do you want to make your releases safer, faster, and less effort? Lots of us now have microservices, kubernetes, maybe even a service mesh. So why are released still banned on fridays? Why is it so hard even know what version is running in production?

In this practical talk, Matt will talk through progressive delivery. This is an approach, and a set of tools, which give us automated, safe, observable deployments and releases.

There’ll be a lot of demos, during which we’ll see:

• Canary deployments and automated rollbacks
• The separation of Deployment and Release
• Traffic mirroring, comparison of results between versions, and other neat network tricks in Kubernetes

And lots more!

Travelopia is an experiential travel company. Our travel brands provide customers with options as varied as polar expeditions, yachts, and adventure travel. Customer experience is supported by digital platforms that enable discovery, bookings, tailoring itineraries, and completing travel paperwork. The technology delivery pipeline is always full and it is easy to get buried in the details of execution and lose sight of business outcomes. To avoid this trap, we came with mechanisms to keep the business outcomes front and center. These mechanisms are built around a central artifact - a KPI tree. In this talk Sree and Sriram will share how they made use of KPI trees to tighten the business case analysis process, demilitarize prioritization of initiatives, improve demand management, speedup onboarding of new colleagues, and enhance shared understanding and alignment.

Large-scale software development generates a lot of data when teams use tools like Jira or Azure Devops. We could analyze the data with statistical tools and techniques in order to understand how to improve delivery performance. Naresh and Sriram have been attempting this at one of their clients. In this talk, they’ll share the techniques they used and the lessons they have learnt so far.