Changing the Definition of Done: The DevOps Evolution of Agile
Traditionally on agile teams, the "Definition of Done" has centred around the completion of feature development: coding it up and maybe adding some unit tests to prove it works. What happens to our code after that is often a mystery as we rely on Operations teams to work their magic. The advent of DevOps has seriously challenged this traditional view. Teams that embrace DevOps tools and methodologies now consider a feature Done when it is in production, serving its customers - and developers, QA, and other non-Operations people now have starring roles in getting it there. Come find out what DevOps is from both a technological and a cultural perspective, how it allows companies to deliver value even faster to their customers, and how it is the logical evolution and extension of Agile.
Outline/structure of the Session
The traditional Definition of Done in Agile
What this Definition of Done is missing
What DevOps is - the 20,000ft view
- The history of DevOps
How DevOps fills the gap missed by the Traditional Definition of Done
What DevOps does for you
What DevOps is from a cultural perspective
What DevOps is from a technical perspective
Why Culture is more important to DevOps than Technology
What DevOps looks like for different types of organizations
What DevOps + Agile is like
- Understanding of how DevOps complements Agile.
- Appreciation that DevOps is a much deeper undertaking than one might initially think.
- Appreciation for the cultural and organizational aspects of DevOps.
- Advancing knowledge on aspects of DevOps that are not often considered, such as organizational / cultural fit.
Agile Practitioners, DEVelopers, OPerationS, and anybody else who wants to know how DevOps can enrich Agile.
Given the intermediate nature of this talk, attendees should have a basic knowledge of agile principles and practices to fully appreciate how DevOps improves Agile.