The word "DevOps-in-a-Box" has been deemed a misnomer , among the DevOps practitioner, thanks to the parody video from ScriptRock (my personal favourite ) and some active advocates of the same in our field. DevOps-in-a-box makes no practical sense just like Agile-in-a-box wont. You cant buy an appliance or a "box" which will make you / your enterprise  Agile or DevOps. Maybe CI/CD Tools-in-a-Box might make some sense considering some of the end to end tool chains and orchestration services that are offered as an appliance or as-a-service model.

During the various discussion on training & coaching for DevOps implementations, we realized that implementers & practioners need an simple environment to experiment and learn the concepts of DevOps not limiting to only the tools & tool-chains. We realized that this maybe a practical use case for DevOps-in-a-box i.e DevOps in a Box - a Training Environment. When we looked around for similar views and approaches we found the Calavera project by Charles T. Betz. The Calavera project creates a "skeletal" continuous delivery pipeline that can be experimented on a workstation using Vagrant and VM VirtualBox. Though it is primarily CD-tools-in-a-box ,it is an interesting way to experiment with your own pipeline. 

For our training needs , we wanted to explore methods of creating an environment where the aspects of tools , process and people enablement methods can be experimented. As a result of which , we set out to create the DevOps Experimental Learning Platform (DELP). Using the extensive experience Wipro has in the field Agile , CI-CD & DevOps we created various Devops-in-a-box models that can be stood up in a experimental environment to understand how the implementation was architected , what were the process models and the key people enablement factors that were used for the success. The Practitioner can compare their experimental implementation with the actual and understand the reason for the difference.

As part of this demonstration , i will walk you through key elements of the Platform , DevOps Implementation codification methods and a view of a live "Devops-in-a-box" use case. 

 

 
 

Outline/Structure of the Demonstration

Section I - 15 Mins

1. DevOps-in-a-Box - a Training Environment Introduction

2. DevOps Experimental Learning Platform.

Section II - 25 Mins

3. Demo of one Use Case 

Section III - 5 mins

4. Q & A

 

Learning Outcome

- Understand the need for a training environment for DevOps Tools & processes

- Key elements of creating a usable , Codified DevOps Implementation for Training

- General components of a Learning Platform

- Experience on Use case on the platform

Target Audience

DevOps Coaches , Scrum Masters , Trainers , Consultants , Developers , Engineering teams.

schedule Submitted 5 years ago

Public Feedback


    • 20 Mins
      Experience Report
      Advanced

      What is it about?

      This is a story about building appreciation and feedforward culture in the organization.

      I am going to talk about a bottom-up experiment based on Jurgen Appelo's Merit Money, conduced in the biggest e-commerce company in Poland - Allegro Group. It is a story about learning throughout an Agile experiment to get the most out of it. Primarily the experiment was intended to challenge the existing bonus system based on forced ranking. It turned into appreciation and feedback system with some sweets involved. 

      This feedback system has grown to more that 230 people involved from 3 different physical locations and still grows virally. We made a structure in which there is a coordinator in each location. If at least part of scrum team plays the game, SM is the first line contact. He distributes credits and exchanges them for sweets. Also cooperates with coordinator who is responsible for making sure system works well in his location.
      Iterations are now 2 weeks. We introduced a requirement that credit has to be filled in with short description what you thank for, in order to be exchanged. This was to promote written thank you’s and avoid situations where people hand over credits just to get sweets.
      Also every quarter we change credits appearance so that the previous credits cannot be exchanged for sweets. This is to set a time box and “flush the system”.

      Is it for me?

      Do you feel your team could be more engaged in their work? Trying to get rid of silos in your organization? Then this is for you.

      Get inspired by this simple game, in which there are several instant feedback loops, fun, gambling and sweet prizes.

      Oh, I forgot... and you'll find an answer on why we call it Fudge Candies.

    • Ran Nyman
      keyboard_arrow_down

      Ran Nyman / Naveen Kumar Singh - Large-Scale Scrum Introduction

      480 Mins
      Tutorial
      Intermediate

      Large-Scale Scrum (LeSS) is a framework for scaling agile development to multiple teams. LeSS builds on top of the Scrum principles such as empiricism, cross-functional self-managing teams and provides a framework for applying that at scale. It provides simple basic rules and guidelines on how to adopt Scrum in large product development.

      In this tutorial, we focus on LeSS framework and see how you can scale Agile development to big organizations. We will start by looking at basic assumptions behind scaling and what different approaches there. Then we learn how LeSS deals with scaling in big groups and finally how LeSS can be adopted for existing organizations and what changes it bring in.

    • Madhu Madhanan
      keyboard_arrow_down

      Madhu Madhanan / Kartik - Adopting Agility in Infrastructure Projects

      20 Mins
      Talk
      Intermediate

      The words Agile and Infrastructure were often used in the context of elastic, scalable and virtual infrastructure providing agility in computing , storage and network space. More recently , based on the success of Agile in Software development , many companies are looking at improving the agility in infrastructure projects by adopting some of the "Agile" principles in their implementations. The expectation is to be able to create a guiding framework for making infrastructure projects like End user services , data center Services & migrations, etc more agile ( the one with a small 'a') by applying the learning from established models of Agile software development. 

      As part of this talk / session , I will share our experience & insights  on "Adopting Agility in Infrastructure projects" . I would be covering briefly on the following aspects

      1. The Need for increased agility in infrastructure project - is there one ?

      2. Critical Characteristics of Infrastructure Projects that makes them different 

      3. Emergent Design to Emergent Services .

      4. Reference Models Water-Scrum-Fall , ScrumBan , Kanban , CRP etc

      5. What works for us !! 

      6. Key Challenges & Learnings

      The value proposition of enhancing the agility in infrastructure projects is different from the ones viewed from a software developments lens. The need for improving the agility in non software development space is slowly catching attention of business owners. Agility in infrastructure projects is our first step towards an extended agile (small 'a') implementation model for non software development space.

    help