757-216-3656 | Monday–Friday 8:30 AM – 4:30 PM | info@itdojo.com
|

Course Duration

2 Days

Audience

Employees of federal, state and local governments; and businesses working with the government.

Prerequisites

There are no formal prerequisites for this course. A basic understanding of IT concepts and software development practices is recommended.

Course Description

This course is designed for participants who are engaged in the design, implementation, and management of DevOps deployment pipelines and toolchains that support Continuous Integration, Continuous Delivery, Continuous Testing and potentially Continuous Deployment. The course highlights underpinning processes, metrics, APIs and cultural considerations with Continuous Delivery. Key benefits of Continuous Delivery will be covered including increased velocity to assist organizations to respond to market changes rapidly, thus being able to outmaneuver competition, reduce risk and lower costs while releasing higher quality solutions. Increased productivity and employee morale by having more activities performed by pipelines instead of humans so teams can focus on vision while pipelines do the execution. This course prepares you for the Continuous Delivery Ecosystem Foundation(CDEF) certification.

Learning Objectives

  • Goals, history, terminology, and pipeline
  • The importance, practices, and transformation of a DevOps collaborative culture
  • Design practices, such as modular design and microservices
  • Continuous Integration (Cl), such as version control, builds, and remediation
  • Tenets and best practices of Continuous Testing (CT)
  • Continuous Delivery and Deployment (CD): packaging, containers, and release
  • Continuous Monitoring (CM): monitoring and analysis infrastructure, process, and apps
  • Infrastructure and tools: frameworks, tools, and infrastructure as code
  • Security Assurance: DevSecOps
  • The opportunity to hear and share real-life scenarios

Course Outline

Course Topics
  • Course goals
  • Course agenda
  • Continuous delivery (CD) definition
  • Architecting for continuous delivery
  • Continuous delivery and DevOps
  • Relationships between CD, Waterfall, Agile, ITIL, and DevOps
  • Benefits of continuous delivery
  • Importance of culture to the CD Architect
  • What a CD Architect can do about culture
  • How to maintain culture
  • Assignment: DevOps culture and practices to create flow
  • Why design is important to continuous delivery
  • CD Architect’s role in design
  • Key design principles
  • CD best practices
  • Microservices and containers
  • Continuous integration (CI) defined
  • CD Architect’s role in CI
  • Importance of CI
  • Benefits of CI
  • CI best practices
  • Assignment: Optimizing CI workflows
  • Continuous testing (CT) defined
  • Importance of CT
  • Benefits of CT
  • CD Architect’s role in CT
  • Five tenets of CT
  • CT best practices
  • Assignment: Handling environment inconsistencies
  • Continuous delivery defined
  • Continuous deployment defined
  • Benefits of continuous delivery and deployment
  • CD Architect’s role in continuous delivery and deployment
  • Continuous delivery and deployment best practices
  • Assignment: Distinguishing continuous delivery and deployment
  • Continuous monitoring defined
  • Importance of continuous monitoring
  • CD Architect’s role in continuous monitoring
  • Continuous monitoring best practices
  • Assignment: Monitoring build progress
  • Importance of infrastructure and tools
  • CD Architect’s role in infrastructure and tools
  • Building a DevOps toolchain
  • Infrastructure/tools best practices
  • Assignment: identifying common infrastructure/tool components
  • Importance of security assurance
  • DevSecOps and Rugged DevOps defined
  • CD Architect’s role in security
  • Security best practices
  • Assignment: Applying security practices
  • Identifying toolchain and workflow improvements
  • Additional Sources of Information
  • Exam requirements
  • Sample exam review

Frequently Asked Questions

What does the Continuous Delivery Ecosystem Foundation course cover?

This course covers Continuous Delivery Ecosystem Foundation training and best practices. IT Dojo delivers it as live instructor-led training with an emphasis on practical skills for government and DoD professionals.

How long is IT Dojo's Continuous Delivery Ecosystem Foundation training?

IT Dojo's Continuous Delivery Ecosystem Foundation training is 2 Days. It is available as live remote online instruction or on-site at your facility. All sessions are instructor-led with small class sizes to ensure individual attention.

Is this course available as live remote online training?

Yes. IT Dojo offers Continuous Delivery Ecosystem Foundation as live remote online training. A certified instructor leads the session in real time. Students interact via chat or microphone. Classes are kept small (typically no more than 16 students) to ensure engagement. On-site delivery at your government facility or contractor location is also available.

What prerequisites are recommended before this course?

There are no formal prerequisites for this course. A basic understanding of IT concepts and software development practices is recommended.

Does IT Dojo offer this training on-site at government or DoD facilities?

Yes. IT Dojo delivers Continuous Delivery Ecosystem Foundation on-site at government agencies, DoD commands, military installations, and contractor facilities. On-site training is ideal for teams of four or more and can be customized to your organization's specific environment and mission requirements. Contact IT Dojo to schedule.

How do I register for this course?

IT Dojo training is employer sponsored. Your organization registers and pays for seats. To schedule Continuous Delivery Ecosystem Foundation for your team, contact IT Dojo via the Request Training form or call 757-216-3656. IT Dojo will work with your contracting officer, training coordinator, or program office to set up the course.

Get More Information

We work with Government Agencies, Military, government contractors, and corporate clients. As much as we would love to, our business model does not include working with the general public.