Agile Trends Switzerland 2016
Agile Trends Switzerland 2016
What are the main hurdles to introduce agile approaches in Swiss companies. The last five years learn us that
- Introducing agile company-wide is a cultural change process. Such a change takes time and sometimes hurts,
- Without commitment of senior management, the initiative will fail,
- You must teach, coach, support your collaborators through the transition. You need to believe in them and provide an environment where they can safely learn and experiment,
- At the end what matters is collaborator purpose, customer satisfaction, business value.
SwissQ has published a "SwissQ Software Development Switzerland 2016". The study can be downloaded as PDF from their website. See a previous blog for the results of Agile Trends Switzerland 2013 and another blog for the results of Agile Trends Switzerland 2012.
Below some of the findings of the study.
Major Hurdles When Introducing Agile Approaches
The number left is the value for 2016, the number in parenthesis is the value found in the study for year 2013. Bold items are new in the 2016 study and have no 2013 values.
- 63% (72%): Culture change
- 61% (21%): Management support
- 42% (28%): The team
- 30% (-%): Integration of the business
- 28% (25%): Fokus on business value
- 19% (-%): Discipline
- 17% (28%): Know-how collaborators
The trend is a clear move toward agile approaches. Companies seem less reluctant to introduce agile approaches, but often compromise using for example bimodal IT. A typical Swiss example is the government Hermes method mixing Scrum with Waterfall.
Major opponents such as senior managers or internal and external customers more and more acknowledge the success of agile approaches.
The majority of teams use Scrum or Kanban. The associated events and tools are used. The deeper values such as test driven development, acceptance test driven development, clean code or refactoring are often missing. The key is
To be agile, Not to do agile.
We wrote in previous blogs that introducing Scrum in the development department or in the whole company is a change process. The coaches should be trained in change management and have experiences with resistance to changes. Our experience shows senior management are often not ready to move along the cultural change path.
You shall start introducing agile approaches
- Senior management fully committed to the approach and approves the cultural change. Read the book "Reinventing Organizations" from Frederic Laloux to understand the implied changes.
- Products are value driven and quality oriented
- Teams are focused to master their work and tools - Craftsmanship, eXtreme Programming -
For huge development departments consider using the LeSS approach.
Teams work best if you can answer a sounding yes to these five questions (see google:rework).
- Psychological safety
- Can we take risks on this team without feeling insecure or embarrassed?
- Can we count on each other to do high quality work on time?
- Structure & clarity
- Are goals, roles, and execution plans on our team clear?
- Meaning of work
- Are we working on something that is personally important for each of us?
- Impact of work
- Do we fundamentally believe that the work we’re doing matters?
If you have doubts please refrain using of agile methods. Introducing agile approaches in product development is similar to introduce lean principles in a production environment. Either you do it fully or the benefits are marginal.