EVDnC: Extreme Value-driven Coaching for Agile teams

EVDnC (Extreme Value-driven Coaching) is a process designed by Marcos Garrido, Rafael Sabbagh and Rodrigo de Toledo. The goal is to promote an efficiency and Agility leap in product development, from the analysis of client’s business needs to the techniques used for software development. For an intensive week, we run full time coaching sessions with development teams and business people. It can be done with one or more teams at the same time.

EVDnC helps teams in the following scenarios:

– Newly formed Agile teams or teams who want to adopt Agile: they usually have drawbacks due to the fact that Agile values and principles are not completely understood nor internalized. EVDnC help these teams to shorten the time necessary to the achieve the first results, helping the process to flow naturally.

– Teams running Scrum / Kanban for a while: even teams running Agile for quite some time may have problems to deliver working software. It’s a perfect fit for an EVDnC session to help these teams to internalize Agile values and learn new concepts such as eXtreme Programming, facilitation techniques, product techniques etc. EVDnC helps to achieve the optimal pace.

– Experienced Agile teams: the evolution of experienced teams sometimes runs flat for a while. When this happens, it’s necessary to review and renew concepts and learn new techniques. In this particular case, EVDnC helps by allowing teams to find the motivation and energy necessaries for the team to get back on track again, shortening the path to the highest maturity level.

EVDnC is divided in 4 steps:

– Pre-Game: prior to the EVDnC week, we work with business people to identify and select a very high-valued product idea to transform into a working product in one week. The output of this session is a Product Vision;

– Preparation: in the first day of EVDnC we gather everyone in a room (business people + team members) to explain the whole idea (what EVDnC is, how it works, what is expected by the end of the week). Business people shares and discusses the Product Vision with the team to make sure everyone is on the same page. When everything is understood, the team receives a go. The outputs of the preparation are the Release Plan and the development environment up and running;

– Development: from the second day on, we run what we call “one day sprints”. Starting with a quick planning session, followed by a full day of development, ending with a review and retrospective. The team aims to deliver working software by the end of each day, so they receive useful feedback for the next “sprint”. This is the main part of EVDnC: we coach business people on how to select, split and discard user stories in an effective way. The development team learns how to be effective by learning/improving software development techniques. Team members also learn facilitation techniques to help the team improve it’s own effectiveness. Most important of all, business people and team work side by side during the whole process. The very intensive process helps everyone to focus on what really matters, as it imposes serious time constraints.

– Closure: by the end of the week we have a working, high-value MVP (minimum viable product) of the software running live. To close the week we run a Big Review with all teams and business people involved. After that, we run a retrospective where they discuss what was learned, how they felt during the process, and what they will keep doing from that moment on.

EVDnC Objectives:

– promote integration between team members;
– promote integration between business people and developers;
– help teams to internalize and practice Agile values and principles;
– learn how to adopt Scrum;
– focus on business value;
– learn how to select, split and discard backlog items;
– learn facilitation techniques to improve team’s effectiveness;
– deliver high-valued, working software after a working week.