The document discusses transformational leadership and its importance for successful organizational change, particularly for DevOps adoption which often requires cultural change. It notes that organizational change initiatives have high failure rates, but transformational leadership can positively influence the factors contributing to success. The document reports on an experiment that found DevOps leaders invited to present at a conference exhibited strong transformational leadership behaviors. Overall, it emphasizes that transformational leadership is key to guiding organizations through necessary changes like DevOps adoption.
Use of ICT for development of learning materialDr.Suresh Isave
The presentation describes briefly, how ICT tools can be used to develop various kind of learning material. It needs to elaborate points mentioned in the presentation.
Use of ICT for development of learning materialDr.Suresh Isave
The presentation describes briefly, how ICT tools can be used to develop various kind of learning material. It needs to elaborate points mentioned in the presentation.
DOES SFO 2016 - Mark Imbriaco - Lessons From the Bleeding EdgeGene Kim
DevOps news is dominated by discussions about tools, and with good reason. It's not unusual for the amount of infrastructure-related code in a system to approach or even exceed the amount of code dedicated to the actual problem the system is solving, even in small systems. As our systems scale in size and complexity, we invest an ever increasing amount of resources into building solutions to help manage our our complex technical systems. And rightly so.
What's often overlooked, however, is the human component of our systems. All too often our approaches to tools, processes, and systems management attempt to remove humans rather than empower them.
I'll make the case that humans are not a source of entropy to be safeguarded against in our systems, but rather a fundamental source of resilience and even efficiency. We'll discuss ways that we can use this point of view to our advantage when constructing our systems to move faster without sacrificing safety. We'll look at things like tools and our interactions with them, team collaboration, and even organizational structure and policies.
We've had plenty of talks about building for web scale, cloud scale, and even planetary scale. Let's spend some time talking about designing for human scale.
DOES SFO 2016 - Cornelia Davis - DevOps: Who Does What?Gene Kim
Within the IT organizational structures that have dominated the last several decades roles and responsibilities are fairly standardized. But with the dramatic changes that DevOps practices and supporting toolsets bring, many are left feeling a bit off balance - it’s no longer clear who is responsible for even things as “straight-forward” as development or operations.
In this talk I will take traditional roles that are distributed across fairly standard IT structures and sort them into a new organizational context. What is the role of the Enterprise Architect? Who does capacity planning and how? How can change management step out of the way all while still satisfying the requirements of safe deployments? How do agile teams interface with personnel responsible for maintaining legacy systems? I’ll leave the audience with a blueprint for a new organizational structure.
As organizations invest in DevOps to release more frequently, there’s a need to treat the database tier as an integral part of your automated delivery pipeline – to build, test and deploy database changes just like any other part of your application.
However, databases (particularly RDBMS) are different from source code, and pose unique challenges to Continuous Delivery - especially in the context of deployments. Often, code changes require updating or migrating the database before the application can be deployed. A deployment method that works for installing a small database or a green-field application may not be suitable for industrial-scale databases. Updating the database can be more demanding than updating the app layer: database changes are more difficult to test, and rollbacks are harder. Furthermore, for organizations who strive to minimize service interruption to end users, database updates with no-downtime are a laborious operation.
Your DB stores the most mission-critical and sensitive data of your organization (transaction data, business data, user information, etc.). As you update your database, you’d want to ensure data integrity, ACID, data retention, and have a solid rollback strategy - in case things go wrong …
This talk covers strategies for database deployments and rollbacks:
• What are some patterns and best practices for reliably deploying databases as part of your CD pipeline?
• How do you safely rollback database code?
• How do you ensure data integrity?
• What are some best practices for handling advanced scenarios and backend processes, such as scheduled tasks, ETL routines, replication architecture, linked databases across distributed infrastructure, and more.
• How to handle legacy database, alongside more modern data management solutions?
DOES SFO 2016 - Marc Priolo - Are we there yet? Gene Kim
2 years ago at DOES14, I presented “Vision Versus Execution: Implementing Continuous Delivery”. I shared how we achieved a big Continuous Delivery win – increasing software test coverage and delivery velocity and efficiency.
Since then, we have been busy scaling DevOps, Continuous Delivery and Lean principles across teams and practices throughout Urban Science. This rollout included both a cultural aspect, as well as an implementation of a centralized, shared, self-service automation solution for our teams – enabling them to “opt-in” to an automated pipeline.
In this talk I will present anecdotes and learnings gathered through our experience over the past two years and discuss the challenges and the value of scaling DevOps across the organization.
DOES SFO 2016 - Rich Jackson & Rosalind Radcliffe - The Mainframe DevOps Team...Gene Kim
This session will discuss the success story from Walmart on how they built a set of services on the mainframe to provide capabilities at a large scale for their distributed teams, as well as discuss the transformation required for mainframe teams to achieve this success.
DOES SFO 2016 - Paula Thrasher & Kevin Stanley - Building Brilliant Teams Gene Kim
After an initial DevOps transformation as a company, we had to grapple with how to scale and grow the talent and workforce to build a NextGen DevOps-minded company of 18,000+ people. We have built a number of programs to expand awareness, encourage growth mindsets, and drive workforce development. We will share the different ways we are working to "Build Brilliant Teams" to drive our DevOps transformations.
DOES SFO 2016 - Avan Mathur - Planning for Huge ScaleGene Kim
Installing one CI server or configuring a deployment pipeline for a specific application might be easy enough. However, as enterprises look to scale their DevOps adoption and optimize their software delivery practices across the organization (to support additional teams, product lines, application releases, processes and infrastructure) -- software delivery pipeline(s) need to scale to support enterprise workloads.
For some enterprises, this means having a pipeline that can withstand the velocity and throughput of thousands of product releases, supporting tens of thousands of developers and distributed teams, hundreds of thousands of infrastructure nodes, multitudes of inter-dependent application components, or millions of builds and test-cases.
This scale poses unique challenges and implications for your pipeline design. This talk covers best practices for analyzing and (re)designing your software delivery pipeline – regardless of your chosen tool-set or technologies. Obtain tips and tools for ensuring your pipelines and DevOps infrastructure have the right architecture and feature-set to support your software production as it scales, while also ensuring manageability, governance, security, and compliance.
Learn best practices for how to:
1) Plan for scale: how to project for the types of performance indicators/vectors you’d need to scale across.
2) How to design of your pipeline and supporting infrastructure and operations (such as data retention, artifact retrieval, monitoring, etc.).
3) Design your pipeline workflows and processes to allow reusability and standardization across the organization, while also enabling flexibility to support the needs of specific teams/apps.
4) Design your pipeline in a way that enables fast rollout- easy onboarding thousands of applications, across hundreds of teams
5) Incorporate security access controls, approval gates and compliance checks as part of your pipeline and have them standard across all releases
6) Ensure your architecture support HA, DR and business continuity.
DOES16 San Francisco - David Blank-Edelman - Lessons Learned from a Parallel ...Gene Kim
Lessons Learned from a Parallel Universe
David N. Blank-Edelman, Technical Evangelist, Apcera
Just within the last ten or so years, we have seen at least two separate communities evolve at the crossroads of development and operations. The first—DevOps—grew up very much in public, the second matured sequestered within the halls of “special” companies like Google and Facebook and is only now starting to gain visibility and traction in the wider world. The DevOps and Site Reliability Engineering (SRE) communities barely speak, yet both have common ancestors and much to offer each other. Let’s look at what they have in common, how they differ, and what are the key things we can learn from both.
DevOps Enterprise Summit San Francisco 2016
DOES SFO 2016 - Courtney Kissler - Inspire and Nurture the Human SpiritGene Kim
Joining another enterprise retailer and discovering similarities and differences with how DevOps is being adopted has been an extremely interesting experience. I will share what I’ve learned so far and how the Point of Service team is practicing lean techniques, optimizing delivery of value and measuring outcomes to enable continuous improvement.
DOES SFO 2016 - Greg Maxey and Laurent Rochette - DSL at ScaleGene Kim
t last year’s DOES conference, we introduced the new Domain Specific Language (DSL) for Electric Flow and painted a vision for how it could revolutionize application release automation (ARA) for very large enterprise implementations.
We are pleased to share with you our experiences and learnings from such a large scale implementation in a financial services company that we’ve been working on this past year. This is a very large implementation—hundreds of ‘platforms’, each containing hundreds of application components each targeting hundreds of ‘device types’, that is, thousands of components distributed across tens of thousands of end points in data centers across the world.
Because of regulatory and quality concerns, complex multi-environment stage testing and promotion systems with clear separation of duties must be enforced. While Electric Flow provided the core functionality to achieve these goals, there was a considerable amount of customization required to support legacy applications, tools and processes. All of the custom work done by the Electric Cloud professional services teams was done in DSL, that is, source code first. Customizations are maintained in a source control system and applied to the various staging environments through automated script execution managed by Electric Flow. While the Electric Flow UI was not used to author content, it was used to verify implementation and provide a convenient ways for the client to monitor progress of their application delivery. The result was a highly maintainable and scalable implementation that could be customized and adjusted on a moment’s notice. Indeed, the project has been managed in a lean agile manner with three week sprints.
DOES SFO 2016 - Daniel Perez - Doubling Down on ChatOps in the EnterpriseGene Kim
HPE's Research Development & Engineering team has been on a fast-tracked DevOps journey over the past couple of years.
During our DOES 2014 talk we shared our deployment of ElectricFlow as a highly available and centralized self-service solution that has enabled HPE developers to quickly onboard onto ElectricFlow for build/test/deployment pipelines in a repeatable and cost-effective way.
At DOES 2015 we expanded on our investments into a comprehensive monitoring, self-healing, and accelerated deployment strategy across all of our applications to further bridge our Dev and Ops gap with greater visibility into our environments and to accelerate our time-to-market with repeatable and fully automated deploys.
Join us this year as we continue in this journey with our biggest transformation yet: the proliferation of ChatOps within our organization. We will discuss the decisions that lead us to these investments, the key lessons we have learned, and share our various Hubot integrations and capabilities.
DOES SFO 2016 - Greg Padak - Default to OpenGene Kim
Large enterprises have hierarchical organizations to define areas of responsibility and drive better accountability. Those structures often block cross-team interactions and knowledge sharing that slow innovation and agility. We will discuss strategies that use open platforms to drive meaningful development outcomes through collaboration and productivity across the enterprise.
DOES SFO 2016 - Alexa Alley - Value Stream MappingGene Kim
Value Stream Mapping can streamline development processes and workflows. This talk will cover how Hearst has done internal Value Stream Mapping workshops to improve team collaboration and release times.
In this talk, I will discuss Value Stream Mapping and how it has helped transform internal processes for businesses within Hearst to adopt a DevOps culture. I’ll walk through the successes and learning experiences we’ve gained by holding VSM sessions at different businesses, in varying verticals at Hearst. We will review real examples of workflows, release times, benefits to the contributors and business, and how the collaboration has helped teams. While there are great successes, I will also share where we saw room for improvement and how we continually make changes to bring the most value to our teams. The most important value is how these have helped to start building a DevOps mindset in a company of over 25,000 employees.
DOES SFO 2016 - Michael Nygard - Tempo, Maneuverability, InitiativeGene Kim
Tempo. Most people are familiar with it in the musical sense. It’s the speed, cadence, rhythm that the music is played. It drives the music forward - and pulls it back. But there’s more to tempo than a musical beat. In war, like in business, tempo - the speed at which you can transition from one task to the next - is a critical component for victory.
No single person nor department owns tempo. Somebody can’t just shout, “I now control the tempo,” and take charge. If you operate at a faster tempo than your cycle time allows, then you’ll get thrashing. The rate of tempo emerges organically as companies move around that action loop of sensing, deciding and acting.
Tempo emerges from the convergence of architecture, infrastructure, organization, and mindset. All these things have to align to achieve tempo. None of them can be changed in isolation.
In this talk, we will look at different models for transforming an organization to high tempo and high performance. We'll see how that can get derailed and what to do about it.
DOES SFO 2016 - Topo Pal - DevOps at Capital OneGene Kim
In my previous years’ talks at DevOps Enterprise Summit, I spoke about starting and scaling of DevOps at Capital One; importance of Open Source, Open Technology and Innovations in DevOps.
This year, I will present Capital One’s journey of maturing in DevOps and Continuous Delivery. My presentation will cover our current areas of focus: Delivery Pipeline, Flow and Measurements. I will also share some of the problems we faced and what we did to solve them.
DOES SFO 2016 - Kaimar Karu - ITIL. You keep using that word. I don't think i...Gene Kim
Let’s get this straight. ITIL is not about implementing dozens of processes, or about establishing a CAB to review every change request, or about the never-ending story of creating a CMDB. The ITIL framework has been designed to help IT organizations to move from being a black box technology provider – often viewed as a disposable cost centre – to becoming a service provider, and a true partner for the rest of the business. We know – we own the framework.
Unless your customer can achieve their objectives with the technology you run, and can get assistance when needed, no-one cares whether your architecture is built on a monolith, uses microservices, or can brag about being serverless. Agile as a mind-set covers the whole value chain, but common practices are limited to development only. DevOps as a philosophy covers the whole value chain, but common practices are limited to the deployment-focused intersection of development and operations only. Understanding the organisation's strategy, developing the product strategy, and dealing with customer issues are expected to be taken care of by someone else, as if by magic. Because of this, DevOps faces a risk of becoming the largest local optimisation exercise ever undertaken for way too many organisations
In tens of thousands of companies around the world, ITIL has helped to develop an organizational capability that has provided them with a competitive advantage. More than three million people have been certified, and ten times as many trained over the years. Yet, we have all heard the horror stories, too. So what is it that separates a successful adoption of ITIL from an unsuccessful attempt at implementing the framework? What are the common problematic practices and anti-patterns we have seen in the wild, and what does the guidance in ITIL really say? How can you move from a broken approach to IT Service Management to one that delivers value. Can you still use ITIL in the DevOps world? Do you even need to? Or, perhaps, the questions is whether DevOps can survive (in the enterprise) without embracing the service mind-set.
Making a case for the reformation of the PMO
Based upon evolving technology and the globalization of companies there is an increasing need to manage projects, but there has been little success of Project Management Offices (PMO) to do so; thereby not providing value to its organization. PMOs are disillusioned of their importance and the business has responded with removal of those positions.
Know the difference between the failure of Change Management and the success of Organization Development. Why does 70% of Change Management initiatives fail? And what's the answer to turn this around?
Leadership , the key to unlocking high performance in safety critical indust...Wendy Anyster
Elements that contribute to the development of a strong safety culture;
The impact of various leadership styles on organisational behaviour;
Strategies to unlock organisation-wide behavioural shifts & change;
Behavioural tools & practices that work.
DOES SFO 2016 - Mark Imbriaco - Lessons From the Bleeding EdgeGene Kim
DevOps news is dominated by discussions about tools, and with good reason. It's not unusual for the amount of infrastructure-related code in a system to approach or even exceed the amount of code dedicated to the actual problem the system is solving, even in small systems. As our systems scale in size and complexity, we invest an ever increasing amount of resources into building solutions to help manage our our complex technical systems. And rightly so.
What's often overlooked, however, is the human component of our systems. All too often our approaches to tools, processes, and systems management attempt to remove humans rather than empower them.
I'll make the case that humans are not a source of entropy to be safeguarded against in our systems, but rather a fundamental source of resilience and even efficiency. We'll discuss ways that we can use this point of view to our advantage when constructing our systems to move faster without sacrificing safety. We'll look at things like tools and our interactions with them, team collaboration, and even organizational structure and policies.
We've had plenty of talks about building for web scale, cloud scale, and even planetary scale. Let's spend some time talking about designing for human scale.
DOES SFO 2016 - Cornelia Davis - DevOps: Who Does What?Gene Kim
Within the IT organizational structures that have dominated the last several decades roles and responsibilities are fairly standardized. But with the dramatic changes that DevOps practices and supporting toolsets bring, many are left feeling a bit off balance - it’s no longer clear who is responsible for even things as “straight-forward” as development or operations.
In this talk I will take traditional roles that are distributed across fairly standard IT structures and sort them into a new organizational context. What is the role of the Enterprise Architect? Who does capacity planning and how? How can change management step out of the way all while still satisfying the requirements of safe deployments? How do agile teams interface with personnel responsible for maintaining legacy systems? I’ll leave the audience with a blueprint for a new organizational structure.
As organizations invest in DevOps to release more frequently, there’s a need to treat the database tier as an integral part of your automated delivery pipeline – to build, test and deploy database changes just like any other part of your application.
However, databases (particularly RDBMS) are different from source code, and pose unique challenges to Continuous Delivery - especially in the context of deployments. Often, code changes require updating or migrating the database before the application can be deployed. A deployment method that works for installing a small database or a green-field application may not be suitable for industrial-scale databases. Updating the database can be more demanding than updating the app layer: database changes are more difficult to test, and rollbacks are harder. Furthermore, for organizations who strive to minimize service interruption to end users, database updates with no-downtime are a laborious operation.
Your DB stores the most mission-critical and sensitive data of your organization (transaction data, business data, user information, etc.). As you update your database, you’d want to ensure data integrity, ACID, data retention, and have a solid rollback strategy - in case things go wrong …
This talk covers strategies for database deployments and rollbacks:
• What are some patterns and best practices for reliably deploying databases as part of your CD pipeline?
• How do you safely rollback database code?
• How do you ensure data integrity?
• What are some best practices for handling advanced scenarios and backend processes, such as scheduled tasks, ETL routines, replication architecture, linked databases across distributed infrastructure, and more.
• How to handle legacy database, alongside more modern data management solutions?
DOES SFO 2016 - Marc Priolo - Are we there yet? Gene Kim
2 years ago at DOES14, I presented “Vision Versus Execution: Implementing Continuous Delivery”. I shared how we achieved a big Continuous Delivery win – increasing software test coverage and delivery velocity and efficiency.
Since then, we have been busy scaling DevOps, Continuous Delivery and Lean principles across teams and practices throughout Urban Science. This rollout included both a cultural aspect, as well as an implementation of a centralized, shared, self-service automation solution for our teams – enabling them to “opt-in” to an automated pipeline.
In this talk I will present anecdotes and learnings gathered through our experience over the past two years and discuss the challenges and the value of scaling DevOps across the organization.
DOES SFO 2016 - Rich Jackson & Rosalind Radcliffe - The Mainframe DevOps Team...Gene Kim
This session will discuss the success story from Walmart on how they built a set of services on the mainframe to provide capabilities at a large scale for their distributed teams, as well as discuss the transformation required for mainframe teams to achieve this success.
DOES SFO 2016 - Paula Thrasher & Kevin Stanley - Building Brilliant Teams Gene Kim
After an initial DevOps transformation as a company, we had to grapple with how to scale and grow the talent and workforce to build a NextGen DevOps-minded company of 18,000+ people. We have built a number of programs to expand awareness, encourage growth mindsets, and drive workforce development. We will share the different ways we are working to "Build Brilliant Teams" to drive our DevOps transformations.
DOES SFO 2016 - Avan Mathur - Planning for Huge ScaleGene Kim
Installing one CI server or configuring a deployment pipeline for a specific application might be easy enough. However, as enterprises look to scale their DevOps adoption and optimize their software delivery practices across the organization (to support additional teams, product lines, application releases, processes and infrastructure) -- software delivery pipeline(s) need to scale to support enterprise workloads.
For some enterprises, this means having a pipeline that can withstand the velocity and throughput of thousands of product releases, supporting tens of thousands of developers and distributed teams, hundreds of thousands of infrastructure nodes, multitudes of inter-dependent application components, or millions of builds and test-cases.
This scale poses unique challenges and implications for your pipeline design. This talk covers best practices for analyzing and (re)designing your software delivery pipeline – regardless of your chosen tool-set or technologies. Obtain tips and tools for ensuring your pipelines and DevOps infrastructure have the right architecture and feature-set to support your software production as it scales, while also ensuring manageability, governance, security, and compliance.
Learn best practices for how to:
1) Plan for scale: how to project for the types of performance indicators/vectors you’d need to scale across.
2) How to design of your pipeline and supporting infrastructure and operations (such as data retention, artifact retrieval, monitoring, etc.).
3) Design your pipeline workflows and processes to allow reusability and standardization across the organization, while also enabling flexibility to support the needs of specific teams/apps.
4) Design your pipeline in a way that enables fast rollout- easy onboarding thousands of applications, across hundreds of teams
5) Incorporate security access controls, approval gates and compliance checks as part of your pipeline and have them standard across all releases
6) Ensure your architecture support HA, DR and business continuity.
DOES16 San Francisco - David Blank-Edelman - Lessons Learned from a Parallel ...Gene Kim
Lessons Learned from a Parallel Universe
David N. Blank-Edelman, Technical Evangelist, Apcera
Just within the last ten or so years, we have seen at least two separate communities evolve at the crossroads of development and operations. The first—DevOps—grew up very much in public, the second matured sequestered within the halls of “special” companies like Google and Facebook and is only now starting to gain visibility and traction in the wider world. The DevOps and Site Reliability Engineering (SRE) communities barely speak, yet both have common ancestors and much to offer each other. Let’s look at what they have in common, how they differ, and what are the key things we can learn from both.
DevOps Enterprise Summit San Francisco 2016
DOES SFO 2016 - Courtney Kissler - Inspire and Nurture the Human SpiritGene Kim
Joining another enterprise retailer and discovering similarities and differences with how DevOps is being adopted has been an extremely interesting experience. I will share what I’ve learned so far and how the Point of Service team is practicing lean techniques, optimizing delivery of value and measuring outcomes to enable continuous improvement.
DOES SFO 2016 - Greg Maxey and Laurent Rochette - DSL at ScaleGene Kim
t last year’s DOES conference, we introduced the new Domain Specific Language (DSL) for Electric Flow and painted a vision for how it could revolutionize application release automation (ARA) for very large enterprise implementations.
We are pleased to share with you our experiences and learnings from such a large scale implementation in a financial services company that we’ve been working on this past year. This is a very large implementation—hundreds of ‘platforms’, each containing hundreds of application components each targeting hundreds of ‘device types’, that is, thousands of components distributed across tens of thousands of end points in data centers across the world.
Because of regulatory and quality concerns, complex multi-environment stage testing and promotion systems with clear separation of duties must be enforced. While Electric Flow provided the core functionality to achieve these goals, there was a considerable amount of customization required to support legacy applications, tools and processes. All of the custom work done by the Electric Cloud professional services teams was done in DSL, that is, source code first. Customizations are maintained in a source control system and applied to the various staging environments through automated script execution managed by Electric Flow. While the Electric Flow UI was not used to author content, it was used to verify implementation and provide a convenient ways for the client to monitor progress of their application delivery. The result was a highly maintainable and scalable implementation that could be customized and adjusted on a moment’s notice. Indeed, the project has been managed in a lean agile manner with three week sprints.
DOES SFO 2016 - Daniel Perez - Doubling Down on ChatOps in the EnterpriseGene Kim
HPE's Research Development & Engineering team has been on a fast-tracked DevOps journey over the past couple of years.
During our DOES 2014 talk we shared our deployment of ElectricFlow as a highly available and centralized self-service solution that has enabled HPE developers to quickly onboard onto ElectricFlow for build/test/deployment pipelines in a repeatable and cost-effective way.
At DOES 2015 we expanded on our investments into a comprehensive monitoring, self-healing, and accelerated deployment strategy across all of our applications to further bridge our Dev and Ops gap with greater visibility into our environments and to accelerate our time-to-market with repeatable and fully automated deploys.
Join us this year as we continue in this journey with our biggest transformation yet: the proliferation of ChatOps within our organization. We will discuss the decisions that lead us to these investments, the key lessons we have learned, and share our various Hubot integrations and capabilities.
DOES SFO 2016 - Greg Padak - Default to OpenGene Kim
Large enterprises have hierarchical organizations to define areas of responsibility and drive better accountability. Those structures often block cross-team interactions and knowledge sharing that slow innovation and agility. We will discuss strategies that use open platforms to drive meaningful development outcomes through collaboration and productivity across the enterprise.
DOES SFO 2016 - Alexa Alley - Value Stream MappingGene Kim
Value Stream Mapping can streamline development processes and workflows. This talk will cover how Hearst has done internal Value Stream Mapping workshops to improve team collaboration and release times.
In this talk, I will discuss Value Stream Mapping and how it has helped transform internal processes for businesses within Hearst to adopt a DevOps culture. I’ll walk through the successes and learning experiences we’ve gained by holding VSM sessions at different businesses, in varying verticals at Hearst. We will review real examples of workflows, release times, benefits to the contributors and business, and how the collaboration has helped teams. While there are great successes, I will also share where we saw room for improvement and how we continually make changes to bring the most value to our teams. The most important value is how these have helped to start building a DevOps mindset in a company of over 25,000 employees.
DOES SFO 2016 - Michael Nygard - Tempo, Maneuverability, InitiativeGene Kim
Tempo. Most people are familiar with it in the musical sense. It’s the speed, cadence, rhythm that the music is played. It drives the music forward - and pulls it back. But there’s more to tempo than a musical beat. In war, like in business, tempo - the speed at which you can transition from one task to the next - is a critical component for victory.
No single person nor department owns tempo. Somebody can’t just shout, “I now control the tempo,” and take charge. If you operate at a faster tempo than your cycle time allows, then you’ll get thrashing. The rate of tempo emerges organically as companies move around that action loop of sensing, deciding and acting.
Tempo emerges from the convergence of architecture, infrastructure, organization, and mindset. All these things have to align to achieve tempo. None of them can be changed in isolation.
In this talk, we will look at different models for transforming an organization to high tempo and high performance. We'll see how that can get derailed and what to do about it.
DOES SFO 2016 - Topo Pal - DevOps at Capital OneGene Kim
In my previous years’ talks at DevOps Enterprise Summit, I spoke about starting and scaling of DevOps at Capital One; importance of Open Source, Open Technology and Innovations in DevOps.
This year, I will present Capital One’s journey of maturing in DevOps and Continuous Delivery. My presentation will cover our current areas of focus: Delivery Pipeline, Flow and Measurements. I will also share some of the problems we faced and what we did to solve them.
DOES SFO 2016 - Kaimar Karu - ITIL. You keep using that word. I don't think i...Gene Kim
Let’s get this straight. ITIL is not about implementing dozens of processes, or about establishing a CAB to review every change request, or about the never-ending story of creating a CMDB. The ITIL framework has been designed to help IT organizations to move from being a black box technology provider – often viewed as a disposable cost centre – to becoming a service provider, and a true partner for the rest of the business. We know – we own the framework.
Unless your customer can achieve their objectives with the technology you run, and can get assistance when needed, no-one cares whether your architecture is built on a monolith, uses microservices, or can brag about being serverless. Agile as a mind-set covers the whole value chain, but common practices are limited to development only. DevOps as a philosophy covers the whole value chain, but common practices are limited to the deployment-focused intersection of development and operations only. Understanding the organisation's strategy, developing the product strategy, and dealing with customer issues are expected to be taken care of by someone else, as if by magic. Because of this, DevOps faces a risk of becoming the largest local optimisation exercise ever undertaken for way too many organisations
In tens of thousands of companies around the world, ITIL has helped to develop an organizational capability that has provided them with a competitive advantage. More than three million people have been certified, and ten times as many trained over the years. Yet, we have all heard the horror stories, too. So what is it that separates a successful adoption of ITIL from an unsuccessful attempt at implementing the framework? What are the common problematic practices and anti-patterns we have seen in the wild, and what does the guidance in ITIL really say? How can you move from a broken approach to IT Service Management to one that delivers value. Can you still use ITIL in the DevOps world? Do you even need to? Or, perhaps, the questions is whether DevOps can survive (in the enterprise) without embracing the service mind-set.
Making a case for the reformation of the PMO
Based upon evolving technology and the globalization of companies there is an increasing need to manage projects, but there has been little success of Project Management Offices (PMO) to do so; thereby not providing value to its organization. PMOs are disillusioned of their importance and the business has responded with removal of those positions.
Know the difference between the failure of Change Management and the success of Organization Development. Why does 70% of Change Management initiatives fail? And what's the answer to turn this around?
Leadership , the key to unlocking high performance in safety critical indust...Wendy Anyster
Elements that contribute to the development of a strong safety culture;
The impact of various leadership styles on organisational behaviour;
Strategies to unlock organisation-wide behavioural shifts & change;
Behavioural tools & practices that work.
Accelerating and improving the change experience (new design) v2Nick Murphy
Leading and managing change is becoming a critical 21st century capability. This presentation identifies the factors that contribute to successful change and offers achievable strategies and services to help organisations improve the change experience.
Leading Transformation Programs in Large / Global OrganizationsKaali Dass PMP, PhD.
Research shows average about 70% of the transformation programs fail.
This presentation focuses on need for transformation in organizations and propose a model to implement transformation programs successfully in large / global organizations.
How to Manage Organizational Change and Cultural Impact During a Cloud Transf...Amazon Web Services
Learning Objectives:
- Learn methodologies to prepare and mobilize resources for a cloud transformation
- Review change management frameworks to help gain buy-in for your cloud initiatives
- Discuss lessons learned by other enterprises during various stages of cloud adoption
Ignore middle managers at your peril!!!. Why middle managers hold the key to ...IQ Business - agility@IQ
Lack of Executive buy-in is known to be one the leading causes of failed Agile transformations! But what about another level of management buy-in that can either make or break your agile transformation efforts… Middle management!
Based on my experience in large corporate organisations undergoing an agile transformation, I have encountered massive support and buy-in from senior leadership and executives. Yet, still some of these transformations have failed to see the significant improvement in results that there were expecting. Middle management are often overlooked in Agile transformation initiatives, yet they are the people most effected by the change… and therefore the most likely to resist.
Presentation by sivalatha sadasivam(siva sadasivam)dm618228
Sivalatha Sadasivam is a content marketing professional at HubSpot, an inbound marketing and sales platform that helps companies attract visitors, convert leads, and close customers. Previously, Rodney worked as a marketing manager for a tech software startup. He graduated with honors from Columbia University with a dual degree in Business Administration and Creative Writing.
Running head STRATEGIC CHANGE GLOBAL CREATIVE ORGANIZATION 1S.docxtoltonkendal
Running head: STRATEGIC CHANGE: GLOBAL CREATIVE ORGANIZATION 1
STRATEGIC CHANGE: GLOBAL CREATIVE ORGANIZATION 6
Daniel Ortiz
Strategic Change: Global Creative Organization
LDR 531
Farooq Khan
University of Phoenix
March 8, 2017
Strategic Change: Global Creative Organization
The leaders in most global organizations have to deal with growing complexities in the industry and the market, uncertainties, workplace diversity, and highly volatile markets. The changes taking place in the market may affect the performance of their businesses as well as their competitiveness in the global market. As the business conditions continue to change rapidly, the leaders should be in a position to adjust accordingly and match this pace as a way of maintaining the performance of the organizations. As a global and creative organization, a firm should be able to nurture and develop such creative leaders who are capable of navigating the complexity of the market and maintain the firm's competitive advantage. As such, a leader of a creative organization should be in a position to establish the right direction, pace, and a meaningful work environment that supports the growth of individuals and the entire organization (Anderson et al, 2015). The leader should be able to facilitate the engagement of all the stakeholders and ensure that they assume responsibility in as much as they are held accountable for the performance of the firm. Also, one should lead effectively through maintenance of relationships, systems, and processes that facilitate the execution, focus, attainment, and maintenance of the desired results. This essay explores Apple Inc., as a creative organization that has been able to attain considerable success in the global market through effective and creative leadership strategies.
Apple Inc. has grown to become a global leader in the technology industry. Apple has successfully operated in the market through the application of creative and innovative strategies, which has enabled them to counter competitive pressures and attract customers from across the world. As a successful business organization, it is important to understand the value of creative leadership as well as innovation as a way to the attainment of greater competitiveness in the market. Apple Inc. is an appropriate example of the impact of effective leadership that is based on creativity and innovation can transform the future of an organization (Anderson et al, 2015).
Over the years, creativity and enabled the company to develop and improve the quality of their products continuously, thus being able to serve the rapidly evolving needs of their global customers. Through effective creative leadership, by individuals such as Steve Jobs, Apple has been able to move to higher levels of performance and maintain this competitive advantage in the market by innovating and renovating their products to suit the market dynamics. Creative leadership is able to focus on the enhancement of cha ...
The Jacksonville Sheriff\'s Office, Continuous Improvement Unit, gives an insightful look at LEAN in law enforcement and its necessity for leadership that champions the change culture.
DOES SFO 2016 - Steve Brodie - The Future of DevOps in the EnterpriseGene Kim
DevOps adoption is growing rapidly, especially in the enterprise. What started as a “keeping up with the unicorns” grassroots movement within more forward thinking companies, has matured to large, complex enterprises now often being on the forefront of DevOps innovation.
DOES SFO 2016 - Aimee Bechtle - Utilizing Distributed Dojos to Transform a Wo...Gene Kim
Aimee Bechtle of Capital One’s Card Technology Advanced Engineering team will share how they have utilized Distributed Dojos to transform to a workforce skilled in DevOpsSec, public cloud and automation. Their Distributed Dojo strategy was formed when they needed to quickly and efficiently meet the challenges of a large cloud migration but were limited by local resources. Reaching out to a prominent retail chain they learned how draw from their engineering talent to form short-term, highly focused delivery teams. These teams now work cohesively across multiple locations to solve the challenges introduced when migrating such a large-scale, complex infrastructure to the cloud. They will explain how within weeks several Dojo teams were formed and releasing automation that not only supported Card Technology’s DevOpsSec and cloud mission, but provided associates with new skills that could be proliferated throughout the company.
DOES SFO 2016 - Ray Krueger - Speed as a Prime DirectiveGene Kim
Speed as a Prime Directive
Ray Krueger, Vice President of Engineering, Hyatt Hotels Corporation
Hyatt is transforming into a technology company that delivers digital experiences in the Hospitality industry. We're applying Continuous Delivery in order to achieve our goals faster. In the process, we are simplifying and abstracting legacy environments and building a hospitality technology platform.
DOES SFO 2016 - Kevina Finn-Braun & J. Paul Reed - Beyond the Retrospective: ...Gene Kim
At DOES15, we presented the work we'd done at Salesforce to take their SRE teams to the "blameless cloud." We worked with various roles in the SRE teams so they could start asking the right questions about failure, and through the postmortem and retrospective process, begin to make lasting changes in _how_ Salesforce worked with and remediated identified failures.
But DevOps espouses less siloed thinking and more shared responsibilities, so we found postmortems within the SRE organization weren't enough. As Salesforce was moving toward a model of "service ownership," teams along
the entire software delivery value stream needed to start to understand their roadblocks to remediation and what aspects of the complex system they worked in were impeding their ability to "own their service."
We'll discuss the second phase of our work in helping these operations _and product_ teams gain a deeper understanding of service ownership, and why
just "DevOps'ing it up" wasn't quite enough on its own to help. plus we'll introduce an expanded model from last year's talk that incorporates human factors and complexity theory. These additions helped prime the teams to more effectively grapple with the challenges facing them on the road to true service ownership.
DOES SFO 2016 - Andy Cooper & Brandon Holcomb - When IT Closes the DealGene Kim
Equifax powers the financial future of individuals and organizations around the world. Using the combined strength of unique trusted data, technology and innovative analytics, Equifax has grown from a consumer credit company into a leading provider of insights and knowledge that helps its customers make informed decisions.
Delivering on that trust requires both business and technical operations excellence. Faced with the growing challenges of the modern marketplace, the Equifax IT organization embarked on a top-to-bottom cultural and technical transformation. This presentation will outline how the Equifax IT team has taken steps towards transforming itself into a nimble, efficient and internally-capable organization. Topics will include key management lessons learned, budget realignment, creating partnerships across organizational boundaries and strategic projects to focus the organization’s transformation efforts. The early results? IT is no longer viewed as a liability to the business, instead IT is now an asset – a strategic partner that is actively helping to close deals.
DOES SFO 2016 - Matthew Barr - Enterprise Git - the hard bits Gene Kim
Source code: Just put it in git, right? Enterprise scale? Github!
But what about when you have a *lot* of source code? Thousands of repositories? No problem! Github Enterprise or Bitbucket Server to the rescue!
Now: Add PCI & SOX. Confidential information. Separation of concerns. Audit. SSO. Centralized SSH key management. DR. Geographic diversity.
This is the part where you roll up your sleeves, and start doing the real work.
This talk starts where the vendors stop- discussing workflows to keep work moving, security & audit protections to ensure code integrity, and automation to connect to other enterprise systems.
DOES SFO 2016 - Sam Guckenheimer & Ed Blankenship "Moving to One Engineering ...Gene Kim
Microsoft has been on a transformation both culturally as well as technically by consolidating engineering systems to One Engineering System. Along the way, we've had many learnings that we'll share from soup to nuts: adopting Git at scale, realigning our talent competencies, reorganizing, becoming data driven, and delivering continuously through lots of automation & cloud adoption.
DOES SFO 2016 San Francisco - Julia Wester - Predictability: No Magic RequiredGene Kim
Predictability: No Magic Required
Julia Wester, Improvement Coach, LeanKit
When you merge onto a freeway and are stuck in bumper-to-bumper traffic, you know right away that its going to be a long trip. Similarly, you can predict the cycle time of your work before it is finished without time consuming, and often incorrect, estimation. Sound like magic? Fortunately for all of us, it's not.
This talk explains the basics of queueing theory; demonstrates how allocation models and pull policies affect the cycle time of work; discusses the effects of batch size and variability on queues; and teaches how to successfully monitor your workflow to get leading indicators of effectiveness. With this information, you'll be doing better forecasting, and achieving better outcomes, in no time!
DOES16 San Francisco - Opal Perry - Technology Transformation: How Team Value...Gene Kim
Technology Transformation: How Team Values Boost Customer Value
Opal Perry, Divisional CIO, Claims, Allstate Insurance
At Allstate, the largest publicly held personal lines property and casualty insurer in America, we constantly innovate for the good of our customers. It’s part of who we are and the legacy we’ve been building since 1931. Recently, we set about recasting the organization's technical and engineering discipline to make it core to the company, and moving technology up the value chain. But technology is just one piece of the transformation. Opal will discuss how an explicit focus on culture and values, together with new ways of working, empower product teams and bring valuable technology to customers with greater speed and agility.
DOES16 San Francisco - Dominica DeGrandis - Time Theft: How Hidden and Unplan...Gene Kim
Time Theft: How Hidden and Unplanned Work Commit the Perfect Crime
Dominica DeGrandis, Director, Training & Coaching, LeanKit
Invisible work competes with known work. Invisible work blindsides people, leaving teams unaware of mutually critical information, until it’s too late.
Married to this problem, is the question, how does one plan for, or allocate capacity for the invisible? It’s tough to analyze something you can’t see. Incognito work doesn’t show up in metrics. Hidden work stalls and blocks important priorities and masks dependencies. Risk accumulates from work delivered late and started late.
The solution is to put conditions in place that allow unplanned work to be seen and measured -- particularly high risk work involving far-reaching decisions. This talk shows you how to do just that.
DevOps Enterprise Summit San Francisco 2016
DOES16 San Francisco - Marc Ng - SAP’s DevOps Journey: From Building an App t...Gene Kim
SAP’s DevOps Journey: From Building an App to Building a Cloud
Marc Ng, Cloud Infrastructure Engineering & Automation, SAP
SAP has been using a DevOps & Continuous Delivery approach for building its web and mobile apps for several years, and is now building and running a global cloud at the scale needed to support the digital transformation needs of its customers. This talk recaps the story of how SAP originally adopted DevOps practices before moving on to describe how the Cloud Infrastructure Services team is building and operating its 3rd generation cloud automation system using microservices, containers and open-source software.
DevOps Enterprise Summit San Francisco 2016
DOES16 San Francisco - Charles Betz - Influencing Higher Education to Create ...Gene Kim
Influencing Higher Education to Create the Future DevOps Workforce
Charles Betz, Coordinator, Minnesota State Digital Curricula Initiative
"Where will we find the talent?"
The feedback loops are slow for higher education, and institutions are only now beginning to respond to the opportunities of DevOps. How can we accelerate this process?
This fast-paced talk will cover both macro- and micro-scale efforts. Over the summer, 11 faculty from Minnesota teaching colleges worked with industry thought leaders to draft a report, “Digital Curricula: Toward next-generation IT education.” The report (including a survey on current digital workforce) compiled hundreds of learning objectives from leading digital and DevOps practices, for instructors and commercial trainers around the world to use in course development.
This report (free and sponsored by the Advance-IT Center of Excellence in the Minnesota State University System) is being distributed this October to hundreds of computing and IT faculty across the 6th-largest education system in the U.S. and will be presented here for the first time to an industry audience.
As a worked example at the course level, the University of St. Thomas offers a survey course on IT delivery, using a “flipped model” with recorded lectures and experiential labs. An open source, 8-node, software-defined virtual cluster based on open technologies is used to illustrate continuous delivery, infrastructure automation, and Agile concepts for the course’s 12 open source lab sessions, as well as collaborative topics such as product management, work management, and operations. Come hear discussion of the motivations, teaching philosophy, technical practices, and results of this pioneering course.
DevOps Enterprise Summit San Francisco 2016
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
How many would agree that transitioning to DevOps and Lean IT leads to organizational change?
It’s something we all know, but seeing just how hard change can be in organization after organization that we’ve coached through Agile and DevOps implementations led me to a learning journey that is the reason why Gene invited me to present at this year’s summit. I became fascinated with this with this classic case of an irresistible force and an immovable object… the desperate need to change the way we build, maintain, and enhance our IT systems struggling against this inherent nature we have to resist change.
How many of you are familiar with John Kotter’s famous “70% failure rate” in change initiatives? If we believe that DevOps adoption leads to organizational change, then Kotter’s claim should serve as a warning for us that we have to know how to effectively manage organizational change if we want our DevOps implementation to be successful.
A lot of additional research has reinforced Kotter’s claim. We are also familiar with many very public failures that illustrate just how difficult change can be. (Go through list quickly).
So we know that implementing DevOps and managing the organizational change it brings is challenging… and yet we also know that in today’s environment organizations MUST be able to continuously adapt to survive.
How many of you have read the book Bold? Whether you agree with their call to action or not, what Diamandis and Kotler did a great job of in the first part of their book was to catalog all of the external factors that are literally changing the marketplace in front of our eyes on a daily basis, and the pace of change is accelerating. They talk about advances like artificial intelligence, big data, driverless cars, internet of things, EVERYTHING as a service, breakthroughs in bio science… the list goes on and on. And then last week… how many saw Elon Musk’s announcement regarding solar panel rooftops that look like regular shingles? Caught the entire energy industry by surprise. This is just one example of why organizations have no choice… the ability to change and adapt is now a core competency.
The evidence shows that companies who can’t adapt are not going to be around long. This report published last year in the New York Business Journal highlighted the fact that in just 15 years over HALF of the Fortune 500 from the year 2000 are now gone… not just off the list… GONE. That turnover rate in the Fortune 500, S&P, Dow, etc. if you graph it out is accelerating on an exponential curve.
So if we know we have to be able to rapidly adapt in our organizations, but that change initiatives frequently fail, where do we go from there? The next step in my journey was to dig into the reasons scholarly researchers found for why change initiatives were failing. This study by Decker et al actually was a study of studies… to survey all of the research at the time to see what patterns they could find. Here are the most frequently cited reasons for change failure… see if any of these look familiar. (Go through list quickly).
That brings us back to our Captain Obvious moment. Nothing here is revolutionary or new… we know this. The real answer I was seeking to find was… what do we do about it? How do we counter these factors and become one of those exceptional companies model organizational agility?
The question is, are all approaches to leadership created equal? What leadership behaviors are most effective for Lean-Agile leaders? As I began to explore that question I discovered the wealth of research around transformational leadership, and it really resonated as a set of leadership patterns that synergize well with Lean IT.
Quickly point out the four key behaviors of transformational leaders (build slide)
Change management models are good and useful, but the research indicates that HOW leaders lead can actually be more effective at creating an environment where employees embrace change.
Other articles document a variety of very positive outcomes that have been connected to transformational leadership behaviors.
Here’s the good news… these behaviors can be taught, and they can be learned! That means all of us in this room can adapt our leadership approach to incorporate the elements of transformational leadership!
Over the last two or three years I’ve discussed my research with Gene, and as we were chatting about this presentation for this conference, we had this idea to form an experiment based on this hypothesis… that the people Gene had picked to be presenters over the last three years at the DevOps Summit would demonstrate high levels of transformational leadership behavior. To test that hypothesis, we asked this group to complete the de facto standard in the research community for measuring transformational leadership – the multi-factor leadership questionnaire.
Overall our sample of 30 responses from the presenters at DOES supports our hypothesis… the green is the range you would expect for transformational leaders, and our group was right in the middle of the target.
This shows you the breakdown by the individual behaviors within transformational leadership…
The same survey also tested two other sets of leadership behaviors… transactional and passive/avoidant. We would expect transformational leaders to score lower on these questions as shown by the green indicators. Again, our sample group scored right where we would expect transformational leaders to score.
So here’s a quick review of what we’
For those who are curious and want to dig into the resources cited in this presentation, I’ve also included the bibliography for your research enjoyment!
I’m happy to answer any questions you might have about transformational leadership or about SAFe… feel free to stop by the Scaled Agile booth in the exhibit hall… I will be there throughout the conference.