Agile and labour turnover - Should I stay or should I go?

room: Windsor East, M — time: Wednesday 14:00-15:30
Average Rating: -

Servant leadership, pair programming, transparency and self-organising teams are evil. They make people leave! Or don’t they?

Agile values and practices often cause enough pain for someone to leave the team or even the company. On the other hand they can retain or even attract people.

What can you do if you want people to stay or go?

After this session you can deal with labour turnover, or lack thereof. You will understand the systemic aspects of labour turnover by turning stories told by participants into diagrams of effects.


Issues we will discuss are:

  • What was the employee turnover rate when you introduced an agile way of working?
  • Which values in your country, company or profession affect the turnover rate?
  • What are the costs and benefits of labour turnover?
  • Ken Schwaber mentions a 20% turnover when introducing Scrum. Does the 20% rule scale? (Meaning: if you introduce Scrum to 1000 people, does that mean 200 leave?)
  • How do you keep the right people, and lose the ‘wrong’ people?
  • Your issues

Benefits

After attending this session you will be better prepared to deal with labour turnover, or lack thereof. You will have a ‘bigger picture’ of labour turnover through stories from other participants. By making diagrams of effects from these stories, you will also have a systems view of labour turnover, which allows you to be effective in more situations.

Intended Audience

People from different companies and different cultures. HRM managers, general managers, change agents, agile coaches, developers, testers and other team members.

Background

  • Leaving a company, or firing employees, is not that easy (e.g. bad for morale, expensive )
  • You may want to keep your people, even when they resist the change,
    • attracting new people is too difficult because of a tight labour market in some countries.
    • they may have valuable knowledge and skills
  • In The Enterprise and Scrum (p6), Ken Schwaber states that when Scrum is introduced, one should expect a turnover of 20%. People who don’t like the change or cannot adapt to it, simply leave or are fired.
Process/Mechanics

you’ll see what the timetable is when you come to the session ;) We’ll do an introduction, tell some of our own stories to explain how to make a diagram, and then it is up to you to tell your stories and share your experiences!