Sustainable Pace: Does Culture Play Any Role At All ?

by Avienaash Shiralige

 

Sustainable pace

Striving to bring agility into the organisation to adapt to changing business conditions is leading people to lose sleep and stretch more than before in some organisations. Agile thought leaders definitely envisioned this and hence recognised sustainability as one of the agile principles.

 Agile processes promote sustainable development.  The sponsors, developers, and users should be able  to maintain a constant pace indefinitely. 

 

To run a long distance you need to find a sustainable pace. But often, companies just don’t get this due to various reasons like:

  1. Pressure from business and management to get most work from least people
  2. Team not having an option to make their own decisions – command and control culture
  3. Teams inability to say NO for non-realistic goals. Service industry firms –  they just can’t say NO to unreasonable client demands
  4. Utilisation of people – Planning for 100% utilisation. This makes people work for more than required hours and hence getting burnout
  5. Unable to remove distractions to the team. Lot of unplanned, non-essential meetings taking people’s time. Questioning motives and saying NO is essential here.
  6. Allocating people on multiple projects with allocation distributed 20%,50%,30% etc. This does not work in reality. There is a switching time between two tasks and people take around 15 mins to achieve FLOW (high productive zone)

Sustainable pace is:

  1. How to achieve this FLOW within the organisation and within your projects. Optimising workflow from concept to cash.
  2. Keeping right balance between speed, robustness of solution without losing quality of product and quality of life of the people. Interestingly, you can achieve high speed only if you have high quality, if not it will slow you down.

Sustainable pace is not a marathon, but a series of short sprints, where you pause, re-energise yourself, reflect and start new. So definitely you need a slack within the sprint to achieve this. Finishing demos and retros quite early on the last day of the sprint and team having some rest time before starting new sprint is one way of getting some slack time.

Google 80/20  or Atlassian Fedex days are some great examples of introducing slack time to drive innovation.

To attain this sustainable pace, you need to remove lot of waste, non-value added activities which a self-organised team finds and eliminates it.

Does culture play any role to attain this self-organising character and hence sustainable pace?

Nation culture has an impact on the organisation culture too.  Geert Hofstede’s years of research in this field reveals some interesting insights into this question.

He has defined multiple parameters for us to understand the culture of different countries. One of the parameters of research was PDI (Power Distance Index). It reflects the extent to which less powerful members of a culture accept that power is unequally distributed and they don’t resent the authority easily. This index varies across cultures with Denmark showing highest resentment while China the lowest. This stark variation across countries could be a very interesting and revealing study by itself.

Culture graph - India:China

A PDI score of 70+ for India clearly indicates that people are far less likely to resist the decisions – whatsoever – done by authority. Not a progressive sign, eh?  People are susceptible to command and control managers and may NOT resist their decisions openly. Western clients working with the Indian teams often complain –  ”I hear only Yes from my team in India. They don’t challenge me? “. Good news is it is changing, some entrepreneurs recognise this and working hard to change this culture.

Building an organisation which questions, challenges ideas, shares thoughts openly which eventually helps to build self-organising teams, with absolutely no hierarchical mindset is immensely tough – more so – as it’s a constant struggle against our own culture/mind-set.

Keeping this culture while we scale is a battle and hence it is extremely important who we bring on-board at every level and more so at middle to senior management. He/she should be a person who is open to work as servant leaders and a very important factor often ignored in organisations.

Have you dealt with such cultural challenges? I will be eager to hear your experiences in achieving sustainable pace.

About Avienaash Shiralige


Avienaash Shiralige is an Agile Coach, Trainer, Business Optimisation and Agile Transformation Consultant @ AgileBuddha. He has been on senior leadership positions in various companies and comes with very rich 17+ years of experience in product and service companies. He has consulted companies in India, US, Europe and Australia on Agile/Scrum/Lean/Kanban and successfully set-up various distributed agile teams across timezones. He can be reached at avienaash@gmail.com.

{ 9 comments… read them below or add one }

Abhishek Aggarwal August 12, 2013 at 1:17 pm

Well said Avienaash. This is how I compare product vs service vs startups companies. It’s just about changing the mindset of organization. People want to use Agile but they do not know what Agile is…

Reply

Avienaash Shiralige August 12, 2013 at 1:23 pm

True. Unless we address cultural issues of the organisation you can not achieve agility. Applying it superficially, is solving a wrong problem.

Reply

Abhishek Aggarwal August 12, 2013 at 1:40 pm

Still What do u think? Are organizations serious? I am sure organizations are not serious yet.
If I compare Indian IT vs US IT then there is a substantial difference. India after all is a cost centre and cultural differences of course has lot of implications not to follow true essence of Agile. I would rather prefer to change 3′s – organization, team and most important individual mindset to bring agility in one’s thinking and doing. Afterall we indian have been british followers :) Location does not matter!!

Reply

Avienaash Shiralige August 12, 2013 at 1:57 pm

It starts with individuals and then spreads across group and org. I’m seeing a change, but in very less firms. We as individuals and as Agile Transformation coach must seed this thinking. I’m fortunately associated with few companies where I DO see this change coming. Top management need to recognise this.

Indians have great attitude and approach that we must focus on and leverage it. I will write about it sometime soon. But we have to move away “following” mindset and question and challenge things – more personal leadership.

Reply

Ben Linders August 12, 2013 at 4:50 pm

Great blog Avienaash! I recognize the things you mention about teams that don’t get sufficient opportunities to develop themselves, and deliver software in a sustainable pace.

Some of the success factors that I consider important in scrum adoption are:
- The way that Scrum / Agile is introduced to teams, and the freedom that teams have to adopt it to their needs and to become self organizing
- The opportunities that a team takes to reflect upon how they use Scrum, and how they adapt their way of working (e.g. by doing retrospectives)
(http://www.benlinders.com/2013/success-factors-for-using-scrum-and-getting-benefits/)

They both have to do giving teams room to find their way with Scrum, and creating a culture that can release the benefits that agile and scrum have to offer.
Ben Linders recently posted..Getting to the Root Causes of Problems in a Retrospective

Reply

Avienaash Shiralige August 12, 2013 at 5:48 pm

Thanks Ben. I Agree with your points. Freedom to fail and learn is what is missing in many organisations. Senior management hurried approach to agile/scrum and not allowing teams to mature and adapt.

Reply

Avienaash Shiralige August 15, 2013 at 5:52 pm
Pradip Ghosh August 18, 2013 at 8:56 am

Good article

Reply

Anjana November 22, 2013 at 1:44 am

Good article. I agree cultural issue will remain there. Sickness of developers and their family members/society etc all create obstacle which does not let companies/team maintain sustainable pace. Yet another fact!

Reply

Leave a Comment

Previous post:

Next post: