SN-Logo NewSN-Logo NewSN-Logo NewSN-Logo New
  • Scrum Courses
  • Agile Keynotes
  • Agile Books & Tools
  • Blog
  • About
  • Contact
0

CHF0.00

✕
Scrum Breakfast March: Tips for Working Virtually
01-02-2011
Scrum and V-Modell
08-02-2011

How we do Sprint Planning 2

Published by Peter Stevens on 04-02-2011
Categories
  • how we do
  • pairing
  • sprint planning
Tags

Many people think Sprint Planning 2 (the second half of the Sprint Planning meeting) is just about creating and estimating the list of tasks for the selected product backlog. This cannot be a bigger over-simplification! Here is simple approach to conducting an effective Sprint Planning 2 Meeting.

In Sprint Planning 1, the Implementation Team and the Product Owner negotiated which “stories” would be implemented in the coming sprint. The team made sure it understood the stories, in particular the acceptance criteria (I recommend agreeing on ‘How to Demo’).

During Sprint Planning 2, the Implementation Team must figure out how to solve the problem it took on in Sprint Planning 1. This consists of two parts:

  1. A solution concept – a design, architecture or whatever, which explains how the problem is to be solved/feature is to be realized.
  2. A list of tasks – what steps must the team do to get each selected backlog item to the state ‘done’.

The goal is not an absolutely perfect design or task planning. It’s about getting a clear enough concept that the team can start work.

In my coaching, I have found it effective when the team members work in pairs in a solve-present-solve-present sequence. They brainstorm the technical concept, then present it to the team. Depending on the feedback, they may need to enhance, modify or possibly even rethink the concept. Again working in pairs, they then create task cards, showing the route to “done.” Finally, each pair presents these tasks to the entire team.

Let us assume the team has committed to 6 stories, that there are 6 team members, and that the team is doing 2 week sprints. So the Sprint Planning 2 is time-boxed to 2 hours. The team forms 3 pairs and each pair works on two stories. So the agenda for the meeting is as follows:

Agenda for Sprint Planning 2

14.00 – 14.05 Start – pair off and divide the stories among the pairs.
14.05 – 14.35 Concept – each pair brainstorms on the technical concept (producing a diagram, text or something which can be presented to the rest of the team)
14.35 – 15.05 Present – each pair presents their solutions to rest if the team. The presentation and Q&A time for each story is time-boxed to a total 5 Minutes (30 Minutes / 6 Stories )
15.05 – 15.35 Tasks – each pair creates a set of tasks to get their stories to ‘done’. Each task represents a goal for the day. The tasks are not estimated, but should be completable in one working day or less. This saves a lot of effort!
15.35 – 16.00 Present – again, each pair presents the tasks needed to get their stories to done. In the course of discussion, they may discover missing or unnecessary tasks. Each story is time-boxed to 4 Minutes (25 Minutes / 6 Stories ).

This approach ensures that at least 2 people have thought intensively about each story. It gives structure to the meeting, so the team can accomplish the meeting within the time-box. And by presenting and discussing the solution within the whole team, the rest of the team is much better positioned to help out during the execution of the sprint.

Share
1
Peter Stevens
Peter Stevens

Related posts

01-02-2019

How to be effective in an online meeting


Read more
31-12-2014

How many people do you need in your team?


Read more
12-09-2014

Pair & Share – a simple technique for Sprint Planning


Read more

12 Comments

  1. Unknown says:
    05-02-2011 at 10:44

    Hello Peter,

    I've translated your interesting post in french :
    Comment réaliser le Sprint Planning 2

    Regards, Fabrice

  2. Peter says:
    05-02-2011 at 19:27

    Merci Beaucoup, Fabrice!

  3. Anonymous says:
    01-03-2011 at 07:29

    Hi Peter. I consider the sprint planning 2 both difficult and crucial, so I appreciate your advice on this.
    I wonder though whether it is really possible to present, ask&answer questions about a solution for a story in 5 minutes, let alone to present the tasks for a story, discuss them and discover missing/unnecessary ones
    in 4 minutes.
    Lukas

  4. Peter says:
    01-03-2011 at 07:52

    Hi Lukas,

    Thanks!

    The short answer is: Of course you can! Just set and stick to the time box. When the time is up, the time is up.

    The goal of the Sprint Planning 2 is not an absolutely perfect design or task planning. It's about getting a clear enough concept about how to move forward that your team can start.

    This approach is somewhere between an individually produced concept and planning poker. By getting the relatively large and diverse team thinking about the story, you get people with differing perspectives to look at the problem and provide feedback.

    I would suggest you try it and see how it works (and post a comment here to share your experience)! Sometimes trying is more effective than discussing!

  5. Anonymous says:
    06-03-2011 at 12:22

    ok, thanks, i will.
    Lukas

  6. Dov TSAL SELA says:
    19-12-2014 at 17:27

    I like the idea of pair analysis! Thanks!

  7. Unknown says:
    04-08-2015 at 13:49

    Great post. Very helpful! I will try to apply this principle in my next Planning

  8. Anonymous says:
    04-06-2019 at 15:09

    Still relevant mid 2019. I share this post very commonly still.
    One thing I've added/changed:

    When the teams present to each other I really trigger them to look for flaws and try to "break the solution" that was presented. This has 2 benefits:
    1. I've found that developers always have critical feedback and want to share that
    2. It makes it more fun

    Offcourse you need to create the right environment for this (trust), but it can bring Planning part 2 to a next level!

  9. Peter says:
    04-06-2019 at 15:30

    Thanks, anonymous! That's a nice tip!

  10. The Agile Paradigm says:
    02-03-2020 at 13:31

    Hi – I tried this but my team creates desktop applications where almost all the Stories have similar tasks (wireframing, coding, testing, code review, UAT). When I tried the above approach, the team felt the exercise was a bit forced. Perhaps we werent approaching it correctly. thanks for any advice

  11. Peter says:
    02-03-2020 at 14:36

    Dear @The Agile Paradigm

    This is really good question.

    Rather than go to the internet to look for the answer, I would have a conversation with the team to find a better answer, one that the team believes in. Here are a couple of questions you could ask:

    * What is happening now? What is the pain or frustration we are feeling?
    * What benefit do we want from task planning?
    * What are five other ways we could get this benefit?
    * Which approach would we like to try in the next sprint?

    It's entirely possible that you'll find that your stories are small enough and simple enough that you don't need task planning. Maybe your stories are too small or overspecified. Maybe you'll discover you are better off with some kind of task planning.

    My advice would be to treat each approach as an experiment, give it a try, and evaluate how well it worked after a sprint or two. That is what the retrospective is there for!

    Good luck, and I'd love to hear how you solve this.

    Best
    Peter

  12. Anonymous says:
    02-03-2020 at 15:54

    Thank you. That makes sense

Learn more about Agile

  • Certified Scrum Product Owner | Face-2-Face | English | 230413-CP2
    in Zürich
    April 13, 2023 -
    April 14, 2023
    Register Now
  •  

  • Certified Scrum Master | Face-2-Face | English | May 22-23, 2023
    in Zürich
    May 22, 2023 -
    May 23, 2023
    Register Now
  •  

  • Certified Scrum Product Owner | Face-2-Face | English | Jun 15-16, 2023
    in Zürich
    June 15, 2023 -
    June 16, 2023
    Register Now
  •  

  • Certified Scrum Master | Face-2-Face | English | Jul 06-07, 2023
    in Zürich
    July 06, 2023 -
    July 07, 2023
    Register Now
  •  

High Performing Teams

  • Get Stuff Done
  • Get Right Stuff Done
  • Create Alignment
  • Leadership

Free Resources

  • Personal Agility Institute
  • Impressum
  • Terms and Conditions
  • Privacy Policy

Upcoming courses

  • Certified Scrum Product Owner | Face-2-Face | English | 230413-CP2 in Zürich
    April 13, 2023 -
    April 14, 2023
    Register Now
  • Certified Scrum Master | Face-2-Face | English | May 22-23, 2023 in Zürich
    May 22, 2023 -
    May 23, 2023
    Register Now
© 2020 Saat Network GmbH. All Rights Reserved.
    0

    CHF0.00

      ✕

      Login

      Lost your password?

      We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept All”, you consent to the use of ALL the cookies. However, you may visit "Cookie Settings" to provide a controlled consent.
      Read more about our Privacy Policy
      Cookie SettingsAccept All
      Manage consent

      Privacy Overview

      This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
      Necessary
      Always Enabled
      Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
      CookieDurationDescription
      cookielawinfo-checkbox-advertisement1 yearSet by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
      cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
      cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
      cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
      cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
      cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
      viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
      Functional
      Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
      CookieDurationDescription
      mailchimp_landing_site1 monthThe cookie is set by MailChimp to record which page the user first visited.
      Performance
      Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
      Analytics
      Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
      CookieDurationDescription
      CONSENT2 yearsYouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.
      _ga2 yearsThe _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
      _gat_gtag_UA_42152348_11 minuteSet by Google to distinguish users.
      _gcl_au3 monthsProvided by Google Tag Manager to experiment advertisement efficiency of websites using their services.
      _gid1 dayInstalled by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
      Advertisement
      Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
      CookieDurationDescription
      NID6 monthsNID cookie, set by Google, is used for advertising purposes; to limit the number of times the user sees an ad, to mute unwanted ads, and to measure the effectiveness of ads.
      test_cookie15 minutesThe test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.
      VISITOR_INFO1_LIVE5 months 27 daysA cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
      YSCsessionYSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.
      yt-remote-connected-devicesneverYouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
      yt-remote-device-idneverYouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
      Others
      Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
      CookieDurationDescription
      COMPASS1 hourNo description
      cookies.jssessionNo description available.
      S1 hourNo description available.
      SAVE & ACCEPT
      Powered by CookieYes Logo