IDEAS home Printed from https://ideas.repec.org/h/spr/fuobcp/978-3-030-82978-0_6.html

Managing the Agile Salesforce in Scrum

In: Scrum for Sales

Author

Listed:
  • Michael J. Scherm

Abstract

The world of sales has become too complex to be understood and managed by a single person. Sales managers need salespeople to think, decide, and act independently. Scrum fosters participation, autonomy, and decentralized decision-making. Scrum also has checks and balances for self-organizing, autonomous teams. This chapter lays out what they are and how they function specifically in sales organizations. But even self-organized teams need leadership. The chapter details out how sales leaders can lead their sales Scrum teams to productivity and success. It suggests how targets can be set and the performance of sales Scrum teams can be managed. The suggested sales planning method is different but can be highly effective in Scrum for sales. We learn how sales planning “the Scrum way” can lead to more accurate and reliable results and how sales teams can use agile fixed-price contracts and pricing to create a win-win situation for both customers and vendors. Sales-specific requirements must be kept in mind if the transition to Scrum is to be successful. Checklists, exercises, and tools are provided that help sales organizations to manage the change. Given that “agility” has been one of the most abused words in the business world in recent years and the fact that Scrum is perceived as something specific to software development, it is not surprising that many people are skeptical about agile frameworks in general and Scrum in the context of sales. In corporate boardrooms, executive offices, shop floor cubicles, hotel bars and at dinner parties, the same statements can be heard again and again: “Sales is not software development. Scrum will not work in sales.” “Self-organized Scrum teams will do what they want but not what they are supposed to do.” “Salespeople are not software developers. They are not intrinsically motivated.” “How will self-organized teams perform when they set their goals by themselves?” “Sharing opportunities, quotas and goals—that will never work.” “Individual salespeople will slack off and hide behind others in the team.” “There is no planning in Scrum.” “I will not be able to forecast revenue anymore because iterative planning means teams will change their sales forecast after each iteration—if they plan at all.” Most concerns about the use of Scrum in sales organizations have to do with management issues: Managers are concerned that “a bunch of self-organized agile hippies” will run the sales team, doing what they want and not being held accountable for anything they do. Salespeople, on the other hand, are often rather enthusiastic about the idea of working in an “agile” sales organization. Some of them are thrilled by the prospect of breaking up encrusted structures and actively participating in company decisions. Others see the opportunity to lean back and let others do their work because—due to the same misperceptions that many managers have—they think there is less management and control in self-organized teams. Realistically speaking, there is quite a lot of management in Scrum. A short look at sales managers’ key responsibilities will help to understand what they do in general and what they must do differently in Scrum. According to Brock (2016), key requirements for sales management can be summarized as follows: Organize how salespeople work. Set up the sales organization. Set up sales territories. Set up sales processes. Enable salespeople. Set up sales systems and tools. Translate market intelligence into sales strategy. Provide content and collaterals. Manage the politics within the company. Manage salespeople’s performance. Set sales strategy and goals. Motivate and incentivize salespeople. Conduct reviews. Tackle performance problems. Develop salespeople. Run formal development programs. Coach salespeople to success. Hire salespeople. Select them. Train them. Even sales management in Scrum must cover these areas. Management in Scrum is different from traditional management, though, because it aims at different things. The sections that follow explain how sales management must change, and how sales managers can fulfill the above requirements in a Scrum setting.

Suggested Citation

Handle: RePEc:spr:fuobcp:978-3-030-82978-0_6
DOI: 10.1007/978-3-030-82978-0_6
as

Download full text from publisher

To our knowledge, this item is not available for download. To find whether it is available, there are three options:
1. Check below whether another version of this item is available online.
2. Check on the provider's web page whether it is in fact available.
3. Perform a
for a similarly titled item that would be available.

More about this item

Statistics

Access and download statistics

Corrections

All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:spr:fuobcp:978-3-030-82978-0_6. See general information about how to correct material in RePEc.

If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.

We have no bibliographic references for this item. You can help adding them by using this form .

If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.

For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: Sonal Shukla or Springer Nature Abstracting and Indexing (email available below). General contact details of provider: http://www.springer.com .

Please note that corrections may take a couple of weeks to filter through the various RePEc services.

IDEAS is a RePEc service. RePEc uses bibliographic data supplied by the respective publishers.