Agile Glue: Creating a Culture of Dev Ops
As a company undergoes an agile transformation, the pressure from the business builds to show a product that is evolving to meet the needs of its users. Features need to be developed as fast as possible and ensure feedback is received to allow the product to grow. All too frequently do we see companies implement an agile framework without considering the development, deployment, and maintenance of the application. Businesses become concerned about moving quickly and start to implement shortcuts that impact the applications ability to be agile. Changes to security and data laws begin to affect the development of features or bug fixes significantly.
It is very common for companies to create a DevOps department or task an individual as a DevOps Specialist, this only adds another dependency to the development process and does not add to the overall agility of the application.
Successful rapid delivery has been to instill a culture of DevOps throughout the agile process. Ensuring the right requirements and deployment plans are established and enabling the team to make architectural decisions throughout the development process. Creating a team-oriented DevOps culture includes:
- Planning deployment-related tasks throughout the agile lifecycle.
- Ensuring privacy and security by design.
- Building architecture as code to enable developers to leverage essential cloud infrastructure.
- Establishing consistency of configurations across development, staging, and production environments.
- Implementing event streams for data analytic capture and application logging.
A finely tuned DevOps culture removes blockers from the development process as the team is empowered to build from a full stack perspective, and not just from the technology silo. Promoting immutable environments through configuration reduces dependency on tracking environment changes and allows cross environment consistency; this reduces scaling issues and deployment knowledge being maintained by one team or department. Application-wide event logging is a feature that requires input from all members of the group, from product owner to operations, that help monitor the stability and resiliency of the application; but is not a feature that can be implemented efficiently without a strong DevOps minded culture.
Creating a DevOps culture throughout the organization provides the support an agile team needs to deliver rapid, iterative software; this allows the team to develop software with minimal technical challenges in the future. Implementing the right culture removes the individual task of DevOps and empowers the team to deliver consistently. Enabling your team to understand the impact of a feature on releases, recognizing the consequences of not following best-practices on the ability to deploy software and the importance of production-like environments all play an integral part in delivering an application your customers want.
Outline/Structure of the Talk
- A brief history of technology and business requirements for web development.
- Convergence of Technology and Business and the impact on Delivery.
- The new Definition of DevOps.
- Impacts of DevOps on application architecture.
- Why DevOps is the cornerstone of Product Delivery.
- Creating a DevOps Evolution.
- Case Study
Participants will come away with a greater understanding of:
- The impact of DevOps on product development and deployment.
- How to implement a DevOps culture within their organization.
- Changes that can be implemented in their agile process.
- How to optimize agile development to provide greater business value.
Scrum Masters, Product Managers, Developers
Prerequisites for Attendees
Participants should come armed with a knowledge of their development and deployment process. Participants also need an understanding of skillsets required to manage the application.