Abstract: You have a golden gem of an activity. There's a brand new project and your project sponsor says "I want to do some DevOps on our new Agile project!" Sigh. You respond with "Well, how about this? Let's BE Agile and adopt a DevOps approach to structuring our teams, designing our architecture, and leveraging automation to rapidly deliver value to our customers." There. At least we've set the mood.
Regardless, greenfield projects provide a unique opportunity for us as DevOps professionals. You don't have the established baggage of a legacy project. The project is probably open to modern tools and architectures. The project is trying to set up team structure that will have the right skill sets.
The problem is: where you do you actually start with greenfield projects? When we introduce DevOps to an existing project (brownfield) we have a unique set of challenges and we can prioritize where to start based on our biggest problems. What do you do when you have a blank page? "Do everything!" Well, what actually makes up "everything" and where do we start?
Putting a solid DevOps solution in place involves some key things. You can follow the religion of the "Three Ways of DevOps" (fast delivery, fast feedback, constant learning) made popular by Gene Kim, but you still have to start somewhere. In this talk, I'll provide a pragmatic formula to setting up well-integrated teams, establishing a DevOps platform, organically growing an initial DevOps pipeline with continuous integration and continuous delivery, establishing some (useful) standards, and guiding the system architecture to support rapid build, deployment, and testing.
This talk is targeted directly at DevOps practitioners and project managers who are trying to establish the right priorities, practices, and organizational structure for new projects. It is also directly applicable to the same people trying to improve their existing projects.
Learning Outcomes: - Recognize and understand the importance of team structure when practicing DevOps on small and large Agile projects
- Prioritize the importance of developer standards, automated build and deployment, and automated testing for your project
- Determine the requirements for your DevOps and operating platforms early in your project
- Evaluate and select a baseline set of tools for building, deploying, and testing your software system
- Establish an initial continuous integration and continuous delivery pipeline for your project
- Recognize the critical importance of automated testing throughout your pipeline
- Realize it's possible to deploy your working software into production-like environments within days or weeks of starting your project, not months or (heaven forbid) years.
Attachments:
