Home > Articles

This chapter is from the book

Shortcut 8: Plan the Sprint, Sprint the Plan

As one of the “elements of a chemistry-building strategy for healthy organizations,” DeMarco and Lister (1999) recommend providing “lots of satisfying closure.” I totally agree with their advice and suggest another complementary element: the provision of lots of clean, fresh starts. Luckily for us, the sprint time-box offers both closure and fresh starts, and in this shortcut we explore the Scrum activity that offers us the regular fresh start: sprint planning.

By collectively resetting the goals for the upcoming sprint every few weeks, the team can start afresh rather than remain stuck on a seemingly endless treadmill of ongoing work. Further, without this regular and expected planning session, significant disruption is caused when team members are rounded up on an ad hoc basis to plan and design.

Product Backlog Refinement

Before the team is gathered in the planning room, I recommend a few preliminary steps to ensure that the product backlog is refined appropriately. First, ensure that the product owner (with relevant assistance) not only has determined the next priority requirements for the upcoming sprint but also has fleshed them out in just enough detail to allow the developers to get started. Doing so might mean including more detailed acceptance criteria as well as any wireframes or mock-ups if applicable (see Shortcut 11). Additionally, it helps if the product owner has taken some time to collaborate in advance with any specialist testers to develop a set of initial test cases (based on the acceptance criteria) to fully describe the inner workings of the required functionality.

Goals Are Good

I would say that most of us enjoy working toward goals, so it is helpful to determine a centralized sprint goal that is omnipresent throughout the sprint. This focal goal typically maps to the main theme of the sprint. For example, the sprint goal might be Enhance the Messaging Engine; this doesn’t mean that other bits and pieces can’t also be worked on during the sprint, but it does indicate that the majority of the work will target the messaging engine. A sprint goal also helps with decision making by ensuring that everyone remains focused rather than deviating and heading off on tangents.

How Long Should a Sprint Be?

Back in the day, it was recommended that the sprint duration should be 30 days—no more, no less. These days, things have become somewhat more flexible, and it is now pretty much universally accepted that the sprint length can vary from team to team. If you speak to any Scrum team, you will find that the vast majority of sprints run from 1 to 4 weeks. I have tried them all out, and in my opinion, 1 week is too short, 4 weeks is too long, leaving me sitting on the fence between 2 and 3 weeks. For a new project, I make the decision based on two factors:

  • Team preference: Some people prefer the longer duration to help gain more momentum, whereas others prefer the simpler planning that a shorter sprint offers.
  • Volatility of requirements: If the product owner is likely to change requirements more often than not due to the product domain or market conditions, then I definitely recommend the shorter duration (see Figure 3.2).
    Figure 3.1

    Figure 3.2. Factors to take into account when considering sprint length.

    Now, an important point: When the preferred sprint length is confirmed (it may take some experimenting in the early days), it should be locked in and rarely changed. There are specific reasons to avoid sporadically adjusting the sprint length, including the following:

  • For team focus, a regular rhythm helps the team better understand how to pace itself.
  • The velocity metric (see Shortcut 13) relies on a consistent sprint duration; otherwise, it becomes less meaningful and more difficult to calculate.
  • If you change the duration of sprints, your sprint review, retrospective, and planning sessions will not fall on the same day of the week. Such irregularities can prove to be a logistical headache, especially if you have to share meeting rooms with others in the organization.

Capacity Planning

Before diving into the sprint planning process, the team needs to first determine its sprint capacity. First, remember that not everyone will have full capacity for every sprint. Some team members may need to work across multiple projects—certainly not an ideal situation, but it can happen (see Shortcut 6). If this is the case, make sure that these developers aren’t overallocated. Also, don’t forget to take into account any public holidays, training, or scheduled leave.

Second, don’t fall into the trap of believing that those who are dedicated full time to the sprint will be able to spend their entire working day on sprint-related tasks.

For example, in a team that I recently worked with (using 2-week sprints), a full-time developer was typically allocated a capacity of 9 days × 6 hours per day = 54 hours per sprint to work on tasks.

First, we used 9 days because the equivalent of 1 full day was dedicated to the sprint planning, review, and retrospective sessions. Six hours a day was allocated because in a typical 8-hour day we found that an individual would usually get only about 6 hours of solid sprint-focused work. The rest of the time was often taken up by various other activities unrelated to the current sprint, such as refining the product backlog (in anticipation for the upcoming sprint) and more general tasks required to be a good citizen of the organization (such as responding to email and assisting others not in the Scrum team). Please note that the proposed capacity per day will vary depending on the team and environment. As such, 6 hours a day should not be considered a universal standard, and I recommend using historical sprint interference statistics (see Shortcut 19) to help you determine your team’s estimated sprint capacity.

Let’s now take a look at the flow of the actual sprint planning session, which I like to split into two distinct parts:

Part 1: The What

This segment is all about the product owner presenting the next-highest-priority product backlog items (PBIs) to the development team as well as fielding any specific questions. This task is conducted for each of the PBIs that are being targeted for completion in the upcoming sprint. I recommend using the team’s velocity (see Shortcut 13) as a rough guide to determine how many PBIs the product owner should be prepared to run through during this session.

Part 2: The How

Moving on, it is then time for the development team to break the PBIs into more granular technical tasks and to estimate each task to the nearest hour. Although estimating in hours may still be inaccurate at times, it helps the team make more informed design trade-off decisions and assists in establishing more confidence in what will likely be delivered by the end of the sprint. As Cohn (2007) explains further:

  • The goal is not the hours but the hours are often a good tool to use to ensure we have discussed things (mostly the technical and product design of those things) at a level sufficient to enter the sprint with a good feeling that we’ll be able to finish all the work of the sprint.

I don’t expect product owners to hang around for this second part (unless they particularly want to). That being said, I stipulate that although product owners don’t necessarily need to be in the room, they certainly need to be on call in case any further clarification is required. Nothing stalls a sprint planning session more than an unavailable product owner!

Even though I like to use velocity-based planning as a guide for Part 1, I like to also use what is commonly known as commitment-based planning to determine the number of specific tasks to include in the sprint backlog. Here are the steps that the development team typically runs through during commitment-based planning:

  1. Start with the highest-priority PBI.
  2. Deconstruct the PBI into tasks with estimates in hours.
  3. Identify any specific task dependencies.
  4. Continue this cycle until the team’s collective capacity is full.
  5. If the output from the velocity-based approach (from Part 1) doesn’t match the output from the commitment-based approach, simply call back the product owner (if she has left the room) to add additional PBIs (if there is still capacity) or explain to her why there will be fewer PBIs targeted than initially expected (if the capacity is filled earlier than initially expected).

Task Definition

I typically set a few parameters for the generation of tasks:

  • Each task needs to be a small, testable slice of the overall PBI (see Shortcut 10) and needs to factor in all activities required to meet the task’s definition of “done” (see Shortcut 11).
  • Each task should take no longer than about 8 hours (the shorter, the better, though).
  • Although more than one developer can work on a single PBI, there should be only one developer (or developer pair) working on a task (see Figure 3.3).
    Figure 3.3

    Figure 3.3. Although a single PBI can be worked on by multiple developers, each task should be worked on by only one developer.

  • Don’t forget to include tasks for the sprint review preparation (see Shortcut 22), such as preparing demo data if required.

You now have the sprint backlog compiled, including the tasks and corresponding estimates for them. The original estimates for the tasks can be aggregated to form the sprint’s initial remaining time, and this time can then be recalculated each day and tracked on the sprint burndown chart (see Shortcut 19). Before going home each day, everyone on the development team should adjust the remaining time for any tasks they had been working on that day to ensure that up-to-date data is being fed into the sprint burndown chart.

The Right Number of Requirements

In a perfect world, after sprint planning is all said and done, you will have a nice neat whole number of PBIs that the team anticipates it will be able to complete in the forthcoming sprint. What you will find occasionally is that there will be a small amount of expected capacity left over that isn’t quite enough to fit a whole new PBI into. That’s okay—simply acknowledge as a team that the intention is to commence the next-highest-priority requirement without setting the expectation that it will be completed by the end of the sprint. I prefer this approach to trying to identify a small enough PBI (lower down on the product backlog) that could fit in nicely because I feel that it is more important to focus on working on the highest business value items.

The 7 Ps

As the British army adage goes, “Proper planning and preparation prevents piss-poor performance,” so a thorough and well-conducted sprint planning session is important to help generate a forecast that is as accurate as possible.

The sprint won’t always go according to plan, and no doubt adjustments will need to be made at times. However, if this session is well run, everyone will have a much better idea of what the collective objectives are, and this information will make the coordination and alignment of expectations a great deal easier.

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.

Overview


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.

Surveys

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.

Newsletters

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.

Security


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

Children


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

Marketing


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.

Choice/Opt-out


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.

Links


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