Skip to main content

Creating a Sense of Urgency

  • Chapter
  • First Online:
The Scrum Culture

Part of the book series: Management for Professionals ((MANAGPROF))

  • 6956 Accesses

Abstract

If a company operates successfully in the market, it builds up a pool of processes, structures, and regulations over the years. These are usually very useful and helpful to the organization at the time of their introduction (cf. e.g. Kotter 2012, p. 149). However, often the utility diminishes with time because the world—especially in today’s globalized and fast-paced environment—changes, but the processes remain rigid. If you ask your employees about the perceived benefits of the existing processes, structures, and rules, you will probably find that they are being experienced as a burden rather than an aid. You can prove this—especially for non-production processes—easily with value stream analyses. On the other hand, however, these structures provide footing and safety. Every employee knows exactly where her place is in the overall structure, her power and influence. If you want to implement far-reaching changes, you directly attack people’s safety needs. Maslow clearly demonstrated in his “hierarchy of needs” that “safety” is almost as important for every individual as “physiological needs” and thus a foundational need far from the higher levels of “esteem” and “self-actualization”. This literally means you are shaking your employees at their very foundation. Accordingly, you will encounter resistance, which can stop your change process, even before you have really started. Therefore, you must transport a sense of urgency that is recognized by everybody. It must illustrate that your change endeavor is not only justified but also necessary for survival. Brief: Make the crisis transparent, on which your desire for change is based on (cf. Kotter 2012, pp. 46). You would not undertake a major change effort, if you did not have good reasons. Share them. With smaller changes, it may be that it is not about survival—they are nevertheless usually about long-term profitability and thus competitiveness. There is a reason that you want to change something. Make this reason visible to everyone.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 54.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 69.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 109.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    In a value stream mapping, you first write down all process steps and add the process inputs and outputs. Then you split them into value creating, supporting, and wasteful process steps and measure their throughput times. The goal is to minimize the supporting processes and to eliminate the wasteful ones.

  2. 2.

    “Impediment” is a Scrum term. It means “problem, that inhibits project progress.”

  3. 3.

    Planning Poker is a method to estimate work. Usually it is used for relative estimates (e.g. Story Points), but it is possible to use the method for absolute numbers (e.g. hours) as well. This method has the advantage that no one dominating person can influence the estimates and cause a bias. In addition, the method nicely facilitates discussion. You can learn more about this method in the appendix. Planning Poker® is a registered trademark of Mountain Goat Software, LLC.

  4. 4.

    If your team is not yet well rehearsed working together, usually team-internal issues are so important that your team will not uncover organizational ones. In addition, a lack of familiarity with the organization or the project can make it difficult to uncover deeper problems.

  5. 5.

    This does not mean that you should create an artificial crisis, but that you simply agree to let an existing crisis come to the surface and into people’s consciousness.

  6. 6.

    “Velocity” refers to the speed at which a Scrum team produces customer value. The time worked is not measured. Instead, the relative size of the customer relevant work that is completed is what counts. Unfinished features, bug fixes and support functions usually do not count towards velocity.

Reference

  • Kotter, J. (2012). Leading change (New ed.). Boston: Harvard Business Review.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2018 Springer International Publishing AG, part of Springer Nature

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Maximini, D. (2018). Creating a Sense of Urgency. In: The Scrum Culture. Management for Professionals. Springer, Cham. https://doi.org/10.1007/978-3-319-73842-0_6

Download citation

Publish with us

Policies and ethics