Home > Articles > Software Development & Management > Agile

Master of Scrum: An Interview with Mike Cohn

Mike Cohn reveals his experiences with Scrum transitions, the challenges of estimating software project duration and scope, Agile project management, and planning in collaborative environments - all while standing on one foot. Or, at least, he tries.
Like this article? We recommend

Mike Cohn has been involved on Scrum Projects since 1995, and is a Certified Scrum Trainer and author of two books on Agile software development: Agile Estimating and Planning and User Stories Applied: For Agile Software Development. Matt Heusser talks with Mike about his earlier work on Agile planning and story-driven Development, along with his upcoming book, Succeeding with Agile.

Matt Heusser: How does your body of work fit inside of this big umbrella we call Agile?

Mike Cohn: I think of myself first and foremost as an advocate for unbranded Agile. I’m very much a Scrum guy at heart, though, but that’s because Scrum is really the minimal set of what’s needed to be Agile.

In the three books I’ve written—including my new one, Succeeding with Agile—I’ve written mostly about unbranded Agile. But in this newest book, I did find that I couldn’t be specific enough without using the Scrum language. Ultimately I made it a Scrum book, even though everything in it should be applicable to any Agile team trying to get better.

Matt: If you had to describe your recommendations for Agile estimating and planning while standing on one foot, what would you say?

Mike: Probably, “Quick, give me something to hold onto!" as I’m not very balanced. But to try to summarize it very briefly, the essential point in the book is that it’s critical to separate estimates of size from estimates of duration.

Most software developers don’t do that. But it’s a natural, real-world way of estimating. If I were to ask you how long it would take you to read a particular book, you’d first estimate how big the book is. You might think, “That’s a 600-page book with normal-size print.” Then you’d think, perhaps, of how many pages you read per hour, and you’d do some math. If you think you can read 60 pages per hour, you’d divide 600 by 60 and tell me 10 hours.

That’s what I mean by separating the estimates of size (“600 pages”) and duration (“10 hours”). When we are asked to estimate software work, we usually just guess—and that never works.

So the book goes through how to estimate in this manner, why it works, how to put together plans based on estimates created this way, and more.

Matt: You're known for championing the idea of user stories for Agile development; you even wrote a book on it. Can you tell us a little bit about the core idea, and how it is different, than, say, use cases or traditional software requirements?

Mike: User stories are short, simple statements that describe something a user wants added to the system. I recommend writing them in first person and I especially like writing them in the form of “As a <type of user>, I want <some goal> so that <some reason>.” For example, “As the vice president of marketing, I want to review the performance of past ad campaigns so that I can select which ones to run again.”

I’ve written about the differences in my User Stories Applied book so let me give you just two ways that user stories differ from use cases.

First, a use case is meant to be complete and fully descriptive. A written user story is intentionally incomplete; we augment the written part with conversations. The written story is a reminder to have those conversations.

Second, it’s very possible to write use cases at different levels and Alistair Cockburn describes wonderfully how to do this. The problem is that very few companies (at least that I’ve encountered) have the discipline to write use cases at different levels. Most settle on the user-goal level and write all their stories that way. With user stories it is much, much easier to move between large stories (which we call epics) and small ones because the format and amount of writing is no different. I find that this ability to move easily between big feature to small and back to big helps teams work incrementally, which is part of being Agile.

Matt: Another one of your books is Agile Estimating and Planning. Yet the Agile manifesto says to value responding to change over following a plan. How can you make planning 'Agile?' What does that even mean?

Mike: Agile planning involves acknowledging that all plans entail uncertainty. A plan is a point-in-time prediction about the future. So Agile planning is planning that accommodates change by recognizing it will occur.

Agile planning is done iteratively and incrementally, just like how we build products. We create an initial plan and refine it, adding more detail with each iteration.

Matt: Is it fair to say that you invented "Planning Poker?" Tell us about it.

Mike: Definitely not. Some of the teams I was working with in 1999-2000 realized that it would be better to agree on a sparse set of numbers to use when estimating. For example, we might say it’s 20 or 30 days to do something and have a good argument between those numbers. But we shouldn’t argue over 20 versus 21. They’re too close. To remember the valid numbers, those teams wrote the numbers on index cards. They used many of the rules in use today by most teams playing Planning Poker: Play until you come to consensus. You can’t play two cards and add them together. So those teams invented that way of playing.

Probably around the same time, James Grenning started doing something similar with teams he worked with. He had some slightly different rules; consensus wasn’t emphasized and you could play multiple cards. James also came up with the great name.

Matt: Tell me a story about a great Scrum success you've been involved with.

Mike: One of the biggest successes in all of Agile has to be Salesforce.com. I’m very proud to have been part of their transition (along with Pete Behrens who provided coaching). Steve Greene, Chris Fry, Parker Harris and the others who started that effort did an amazing job. They converted more than 200 engineers overnight.

What impressed me was Management’s courage to stick with it even when resistance and complaining came out of the woodwork the first few weeks. The company had gotten away from the quarterly releases they had been known for and did only one release in 2006. Salesforce.com went Agile around the end of the year and then in 2007 they did four releases. They delivered 94% more features than in the prior year and delivered 38% more per developer.

Most impressive was a measure they used called “cumulative value delivered,” which looked at the features delivered and when during the year a feature was delivered. A feature delivered in January gave more value to customers than one delivered eight months later. Using that measure, they delivered well over 500% more value to their users in the first year. That’s a success.

Matt: If you had to pick one common barrier that companies have when converting to Scrum, what do you suppose it would be? How do you recommend that companies overcome that barrier?

Mike: Stopping too soon. Too many companies adopt Scrum, see some good improvements but nothing compared to what they could really see. And when they stop improving, there is organizational gravity that pulls them right back to where they started. There’s a reason why the organization is the way it is before they adopted Scrum. Something about personalities, job descriptions, the industry, and so on shaped the company that way. Unless the organization achieves an “escape velocity” when adopting Scrum, they will get pulled right back where they started.

I’ve written about this, using the acronym ADAPT to describe the five activities that are necessary for an organization to really adopt Scrum or any agile process. ADAPT stands for Awareness, Desire, Ability, Promotion, and Transfer. It’s the last two that often do a company in.

To become Agile, we first need to become aware that a change is needed, that the status quo is no longer working. Once we’re aware, we need to develop the desire to actually change. Being aware that a change is needed and having the desire to do it are different.

Next, we need to develop the ability to work in a new, Agile way. Training, coaching, and mentoring can all provide this. Early successes need to be promoted to the rest of the organization so that other teams and projects develop their own awareness and desire.

Finally, the implications of being Agile need to be transferred to the rest of the organization. I don’t mean that the finance group needs to run sprints. But we need to make sure that other groups are not working at odds with the development group being Agile. An HR group that insists on forced ranking of employees, for example, is inconsistent with staying Agile over the long term. That’s a form of the organizational gravity I referred that can pull a company right back to where they started.

Matt: At various times you have done custom development, consulting and training, and served as a editor for Better Software magazine. What are you doing now? What kind of company could benefit from your services?

Mike: I’m finishing a new book called Succeeding with Agile: Software Development using Scrum. It’s taken me almost exactly four years to write. I think of it as a “second book on Agile.” After you’ve read one of the many good books that can get someone started, then pick up this book. It starts right in assuming that readers know what Agile and Scrum are and then goes through the things you need to do to help your organization get started and then get good at it.

At the end of each day of coaching or consulting for the past four years, I wrote down notes about what questions I was asked, what objections people threw at me, and what specific things I advised people to do. I’ve tried to put those into this book so, for example, there are specific sidebars for objections and things to try now.

Matt: What do you want to do next?

Mike: I have a goal of taking a day off sometime in 2010. Seriously, one day off. I’m the world’s worst workaholic but it’s because I love what I do. Sometime in 2010 I vow to take one day completely off. I won’t read about software development. I won’t turn on my computer or iPhone. All I plan to do is to start the day with a single tweet as that will help me hold myself to it. So follow me on Twitter and give me some crap on December 31, 2010 if I haven’t done it.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020