Skip to main content

Introducing Scrum into Large Teams

  • Chapter
  • First Online:
The Scrum Culture

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

Abstract

Time and time again, there are situations in which a very large project team or even an entire company is looking to transition to Scrum. Quite often, these teams are not only large, but also scattered around the globe. A Scrum introduction in such an environment is extremely demanding for the change agent and all those involved in change management. You need to know the specifics of such an endeavor and coordinate across all the departments and staff, whether they are involved or just impacted. Mistakes made in this respect will immediately multiply themselves.

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.

    A truly agile enterprise will not conduct performance reviews on an annual basis. Feedback is expected in short cycles, preferably daily.

  2. 2.

    Depending on the specific task and situation at hand your team may already decay from seven people. Try it out and involve your developers in the decision making process.

  3. 3.

    Depending on the chosen scaling model, this coordination meeting works differently. “Scrum of Scrums” is a very general term, originating from the early days of Scrum.

  4. 4.

    “Overhead” refers to expenses for administrative or other tasks that have nothing to do with the actual product development. Every company should strive to minimize these costs as such.

  5. 5.

    A proxy Product Owner is an information relay of the Product Owner. He does not have decision-making powers and only forwards information coming from the top. Some information is lost or distorted. This is not a desirable state and should be avoided.

  6. 6.

    Again, I am relying on old terms here in order not to favor any specific scaling approach. Depending on your choice, you will find other terms like “community of practice” or “guild”.

  7. 7.

    The Scrum guide defines the rules of Scrum. In these 17 pages (July 2016) are the cornerstones (Schwaber and Sutherland 2016) defined.

Reference

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). Introducing Scrum into Large Teams. In: The Scrum Culture. Management for Professionals. Springer, Cham. https://doi.org/10.1007/978-3-319-73842-0_14

Download citation

Publish with us

Policies and ethics