Shripad will be presenting the following session
Shripad Agashe - DevOps & Cost of Trust: Looking at devops from an economist's perspectiveShripad AgasheDirector Of EngineeringDeserve Labs
schedule 10 months agoSold Out!
Often the word DevOps connotes cloud infrastructure and a set of tools and hence existence of the DevOps teams in many organizations. This categorisation and organization is the projection of understanding existing tools and practices to an emerging category and an attempt to co opt or assimilate new tools and ideas. This categorisation fails to take into account the basis of DevOps movement.
In this talk, I will be covering the motivations and incentives for DevOps movement and why it is successful when it is applied with a first principles approach.
If you look at any activity, there are subtle motivations and tradeoffs which direct our actions. The idea of transaction cost for a given transaction is such a subtle backdrop for many of our seeming irrational actions. From farmers going to a loan shark instead of banks to the rise of nfts and tokenization. Ronald Coase back in 1937 asked a fundamental question: If the markets are so efficient, why do companies exist? The essay is an excellent read on how organic organizations emerge nudged by intrinsic forces like transaction cost. What Coase found out was the trust between two individuals is the most costliest of the resources.
The lack of trust increases the transaction costs of business transactions and a structure where trust can be established more easily, brings down the transaction cost and hence subsequently the cost of goods and services.
So how does this apply to DevOps thinking? In my talk I will show how we can leverage this thinking to reduce batch sizes and thus increase flow and effectiveness of the teams.
1. What got you started/interested in modern software development methods?
I was working with large enterprise clients. In one of the projects, we focused on value stream based approach. It lead to lot of streamlining of activities and ensured consistent flow of business feature deliveries. That opened a new world for me. Then I found out more about "The Unicorn Project", "ToC", "Flow" and it completely changed my way of thinking.
2. What do you think is the biggest challenge faced by the software product engineering community today?
We use techniques and technologies for the sake of using techniques and technologies. That sometimes leads to complicated solutions which are hard to maintain in production. I think product engineering folks should also focus equally on "product" part and not just engineering part and collaborate more closely with product managers.