Scrum is hard to adopt and disruptive to your organisation

before the “ professional scrum foundations ” course ever existed i was tasked with delivering a practical scrum foundation course for our customers. i came up with a 2 day “scrum foundation” course that included lots of practical exercises and leveraged the existing scrum open exam. but why would you want it and is that all you need?

it is hard to adopt scrum. you just have to read ken’s “scrum is hard and disruptive” to understand just how hard!

• but is that bad?
  
  

the reason that more organisations start looking hard at agile and scrum adoption is that we, as an industry, have lost the trust of business. the reason that we have lost the trust of business is that we (the it industry) have proven time and again that we are:

• unable to deliver on time
• unable to deliver on budget
• unable to deliver what the business need
  

is it any wonder that business does not trust us?

1. scrum is a framework for iterative, incremental development using cross-functional, self-managing teams. it is built on industry best practices, lean thinking, and empirical process control.
2. scrum is optimized for high yield product management and product development. scrum is particularly appropriate for high risk, complex, large projects and can be used when other parts of the endeavour are hardware or even waterfall development.
3. if waterfall suits current needs, continue using it.
4. an enterprise can use scrum as a tool to become the best product development and management organization in its market. scrum will highlight every deficiency and impediment that the enterprise has so the enterprise can fix them and change into such an organization.
5. whenever an enterprise modifies or only partially implements scrum, it is hiding or
   obscuring one or more dysfunctionalities that restrict its competence in product
   development and management.
6. the iterative, incremental nature of scrum puts stress on the product development organization to improve its engineering skills and on the product management organization to optimize the return on investment of every release and project. the phrase, “that can’t be done here” really means that it will be very difficult to do so. the gap between current practices and target practices is a measure of incompetence and
   competitive risk.
7. the use of scrum to become an optimized product development and management organization is a change process that must be led from the top and requires change by everyone within the enterprise. change is extremely difficult and fraught with conflict, and may take many years of sustained effort. turnover of staff and management can be expected.
8. the most serious impediments to using scrum are habits of waterfall, predictive thinking over the last twenty to thirty years; these have pawned command and control management, belief that demanding something will make it happen, and the willingness of development to cut quality to meet dates. these are inbred habits that we aren’t even aware of anymore.
9. the focus of using scrum is the change from old habits to new ways of doing business. scrum is not implemented or rolled-out as a process; it is used to foment change.
10. scrum is not a methodology that needs enhancing. that is how we got into trouble in the first place, thinking that the problem was not having a perfect methodology. effort centres on the changes in the enterprise that is needed.
11. iterative, incremental development is much harder than waterfall development; everything that was hard in waterfall engineering practices now has to be done every iteration, and this is incredibly hard. it is not impossible, but has to be worked toward over time.
12. managing a release or project to deliver only the highest value functionality and not deliver the rest optimizes value [and] is the job of product management and customers.
13. self-managing teams are extremely productive. when they work closely with the customer to derive the best solution to a need, they and the customer are even more productive.
14. a team consists of people under pressure to do their best. conflict is natural and the team needs to know how to deal with the conflict and have resources to draw on when needed.
15. the role of an enterprises management changes from telling people what to do to leading and helping everyone do their best to achieve goals. people aren’t resources and managers aren’t bosses

-scrum is hard and disruptive, ken schwaber , 2006.

an interesting point to note is #3. if what you are doing works, then keep doing it, but usually if you are reading something like this, or thinking of any sort of agile training then everything is not going well with waterfall

in order to help a development team adopt scrum there are three things that they will need:

• training
  
  

  wither this is formal training or in-house adoptive training it is crucial that everyone attain the same level of understanding of the target operating model and they can then understand what it means to them.

  this is the reason that i created the scrum foundation course. it is a level setting course that is designed to put the team on the right track from the start.

  
  figure: my first team (bi) in chicago this week

• mentoring

  once a team starts implementing scrum they need a little extra help. while teams that have no on-going scrum mentoring do succeed at scrum, more often they fail, or take a really long time to adopt. with a mentor that is able to answer questions and attend the sprint review and retrospective team are more easily able to adapt. this mentor does not need to be full time, but available to answer questions when the team has them.

  
  figure: my second team (asp.net) getting stuck into one of my activities
  
  

• dedication
  
  

  as ken has said, scrum is hard to adopt and disruptive to your organisation. it will shake things up and you need the dedication and commitment to follow through. things will get harder before they get better and it will be hard for the organisation to change on many levels.
  

  • there will be clashes between the business and it as the business asserts control over what is built and when. this is a critical process and as the development team builds trust with the business the rest of the it hierarchy will feel more and more isolated until it adapts and gets stuck into the process as well.

  • individuals will worry about their job security as things change around them until they begin to understand the niches available and which ones fit them.

  • individuals will be challenged and upset by the mixed messages they get as the understanding of the scope of change takes place within an organisation.

  • metrics will change as trust is built up between business, it and the team. certain metrics, measures and gates will start to change and often disappear as the reason that they existed (distrust) starts to be eroded.
    

  
  figure: not all early sprints will be successful

during a scrum adoption expect to fail early and often . no, its more than that. i want to fail early and often as it is far less costly than the waterfall (and and long iterative approach) where the risk is at the end and you fail late .

• would you rather fail 4 agile projects at sprint 4 or would you rather fail one waterfall in its 3rd year?
  note: one is circa 20 times more expensive than the other… can you guess which?
  

figure: agile risk is all up front

remember it is hard to do scrum, your teams are not used to this process and your business is only beginning to understand the benefits. this is usually when it management get cold feet and try to pull out. remember that it is the business that pays the bills and that they are usually on-board by now. the team may not have had a successful sprint but they will have been able to show "something" and the product owner will have been able to give feedback.

• how do you think the business will react if you suddenly take that feedback loop away from them?