Monday, December 7, 2015

Starting (Disciplined) Agile: a possible approach

Agile stalemate: "The land that Scrum forgot"

Current large adoption of Agile is mainly based on Scrum. The stalemate on realizing more process improvements it is also - in many cases - related to Scrum. The Scrum team organization practices are easy to adopt, but many teams have no hints how to go further with improvements and with Agile. The original main good option was to adopt XP or Scrum & XP. What is missing in many Scrum based Agile adoptions was describe by Robert C. Martin in “The Land that Scrum Forgot”.

The more recent approaches like DAD, comes with some complementary ideas: make the Agile habits explicit (as Agile life-cycles), offer guidance support instead of prescriptions, the teams should own & adapt their process context and others.

First steps problems. Scrum advantage

Even I can argue that DAD approach is better than Scrum-only or than Scrum & XP (in fact DAD allow to have a as possible choices Scrum-style or XP-style approaches), Scrum could have, in practice, a significant advantage on making the first steps, and making this Agile start it is fundamental. Here are some reasons:

The prescribed practices from Scrum area easy to adopt and it is less likely to be in a deadlock on starting with Agile. On the other hand, many XP practices are not so easy to adopt. DA comes with more guidance and with choices, but a team that struggle with the first Agile steps will still have difficulties: “How should I start? What are the first factors that should be subjects of my choices?”

The main advantage of Scrum practices is related more not to the direct benefits, but with removing of the negative side effects of a lot of legacy (bad) practices that are replaced. Example: if a team use the self-organizing power (enabled by Agile) to make poor process choices and disregard, for example, the practices for a collaborative work, they will have worse results that a Scrum-based team. Simplifying: I will have better results using 3 useful practices from a set of 3 than using just one from a set of 10.

No stalemate: not in the first steps or further

We finally need to have an approach offers this kind of support:

Allow an easy start and make more likely the first steps in Agile

Quickly definitely replace some legacy habits with many negative side-effects

Avoid the further stalemates that too often are encountered with Scrum-only approach

Here is a possible approach on getting these results using DAD. The starting goals are the followings:

Start working in a collaborative manner: non-solo work practices

As was mentioned before, the simple and rather vague Scrum practices for team collaboration have the great advantage of consistently replacing the old habits of non-collaborative work.

We can easily go further and get better results by adopting Agile Modeling/Disciplined Agile non-solo work practices – work with others for:

Release Envisioning – Requirements and Architecture Envisioning

Ahead look on requirements or design – Look Ahead Modeling

Just in time requirements or design – Model Storming

Pair Programming (XP practices)

Others

The essential is to offer guidance to the team and to start practicing non-solo work as soon it is possible. Agile-based process improvements and Agile retrospective works only if the team work is based on continuous and actively collaboration.

Start improvement by adopting retrospectives

The improvement based on Agile and other sources must become
continuous and permanent. If the team does not adopt retrospectives, this goals
is difficult to st accomplish.

Containers for generic process goals: life-cycle and iterations

In order to get a proper process
in context, a team should think to the best options and choices to fulfill these
goals. Anyway, we need some containers to manage these goals. Scrum use the
Sprint ~ the iteration as the main container. XP goes further and have an
implicit life-cycle.

In DAD we can find a more robust approach: we have both
iteration and more explicit agile and lean life-cycles (it is the team choice
on selecting one).

Ok, but “How should I
start”? For an “agile beginner” team here is an option for main process containers:

The iteration - is generic for not-very-advanced cases

The agile-basic life-cycle – fits with most of the cases and it is similar with XP approach

As soon it is possible - using proper guidance – the team should be aware of process goals and how these goals are distributed along the life-cycle and iteration.Of course, after (or in the same time) familiarizing with the Agile basic-life cycle, the team could explicitly adopt other types of life-cycles depending on the context.

Next step: Just do it!

Using this initial framework – process goals across life-cycle
and iterations – the team should start working collaboratively (non-solo work practices)
and use retrospectives and other instruments to decide how to improve and adapt
their process. Make sure that this approach is permanent and the process will have further optimizations.