General

User Voice

The Scrum Guide is a community website, created and maintained by Jeff Sutherland and Ken Schwaber. Via this User Voice forum, you may propose changes to the website, the Scrum Guide itself, or engage in discussion about suggestions others have made. This User Voice is read and supported by the Scrum Guide creators.

Periodic reviews of these suggestions inform the product backlog for the Scrum Guide, but final decisions on changes and functionality are Ken and Jeff's.

User Voice is read-only while new Scrum Guide is under development

User Voice is in read-only mode while Jeff and Ken create the next release, based on your suggestions in the User Voice, input from the overall Scrum community, and to meet advanced applications of Scrum that are either being made or have been requested.


  1. Why Sprint Goal inspection at least monthly?

    When we read (in the section Sprint) that “Sprints enable predictability by ensuring inspection and adaptation of progress toward a Sprint Goal at least every calendar month.” it simply says to us that the progress toward a Sprint Goal is inspected/adapted at least monthly. However, we know that on a daily basis the same is done in the Daily Scrum event: “The Development Team uses the Daily Scrum to inspect progress toward the Sprint Goal”. As a result, these two may look mutually contradicting. Suggest correct the first one.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    hold  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add "When is Scrum appropriate" section

    There is a Scrum Reference Card (http://scrumreferencecard.com/ScrumReferenceCard.pdf) that includes a "When is Scrum Appropriate" section (very last page) that I believe is very important for people to read. I am wondering why this "Scrum Guide" website does not have any guidance with respect to the types of projects that are/are not suited to Scrum. Our organization is basically mandating that all projects follow scrum, and sending everyone on Scrum training, but there is no mention of the idea the Scrum is not necessarily the proper "framework" for projects that have "well understood requirements" and are using "proven technologies".…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    hold  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Short version of Scrum Guide. 5 pages, not 17. It can be printed on every wall, even memorized.

    Current version of Scrum Guide is perfect. But we can additionaly create short version. It can fit in 5 pages I bielive. Then it can be printed on wall of every scrum room (we can even send a nice printed copy for free) in the world. And 2nd benefit - it can be memorized by every Scrum master.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    hold  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Can you please have a separate section for Scrum Master role and responsibility? Other than facilitating what are other responsibilities.

    Is Scrum master just facilitating and coaching. Just like project manager has bigger role in PMP methodology. Can you clarify Scrum master role. I don't see much value given in scrum world.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    hold  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. List the techniques are used in Scrum by the scrum team (for eg techniques used in arranging the product back log)

    If this includes the tools and techniques used by the scrum master and product owner will be helpful.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    hold  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Improve Flow of Sprint Planning

    In the PSM and PSPO there are great flow diagrams for the Sprint Planning, where Definition of Done and Retrospective Commitments are part of the input for the Sprint Planning. This is inconsistent with the way it is now described in the Scrum Guide.

    From Scrum Guide, section Sprint Planning, subsection Topic One: What can be done this Sprint?
    "The input to this meeting is the Product Backlog, the latest product Increment, projected capacity of the Development Team during the Sprint, and past performance of the Development Team."

    Suggestion: remove "the latest product Increment" (btw: in the rest of the…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    hold  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Tracking business value

    Scrum master role should be ensuring the Product Owner knows how to arrange the Product Backlog to maximize value as well as track planned vs actual business value delivered to business.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    hold  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. appoint successors for Ken and Jeff, who should further adapt the Scrum Guide

    I know it's a creepy thought, but we all know life is short, and all sorts of things can happen.

    In the future those people who will be new to Scrum, will find it reassuring to know that the responsibility for further advancing the Scrum Guide was granted jointly and personally by both Jeff and Ken to certain individuals, who will be the new Scrum Leaders in the absence of the founding fathers.

    In other words, putting Ken' and Jeff's successors name in the Scrum Guide will make it clear who picks up the torch and takes Scrum further.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    hold  ·  4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. elaborate on risks of applying a "Ready" state

    applying the "Ready" state brings a strong risk of entering a Contract Game between Dev Team and stakeholders.
    a "Definition of Ready" accelerates the risk.
    some sort of "footnote" might help people to understand this and avoid entering into the trap.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    hold  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. make Scrum Guide publicly annotatable

    from my point of view, a Web based version of the (English) Scrum Guide that is annotatable and allows for such discussions that are going on here would boost common understanding and contribute to eliminate misconceptions. scrum.org, Scrum Alliance and scruminc should sponsor this collectively.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    hold  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Agile for individual work

    The Guidebook says the agile framework is effective for appropriate number of team members, but I think the principle, such as putting emphasis on transparency or priority, also will be effective for the tiny team or even for the person working individually.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    hold  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Scrum Master should understand the domain or product on which team is working

    I have been observing in one of the Scrum teams that they tried introducing a new Scrum Master who is unaware of the technology and product on which the team is working. Scrum Master contributes only by asking team members to put comments on their user stories, estimate them and sending mails and calendar invites. After 3 months of waiting (where I assumed that Scrum Master will be able to develop product understanding and contribute to team), I see team is still not able to get even a single benefit from Scrum Master. Due to this, even some team members…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    hold  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Introduce the concept for non IT systems to use Scrum

    For now it very focused on building complex products. However, based on the framework best practices how it can used for non IT industries can be a good starting point.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    hold  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Introduce the concept of Sprint 0 for teams to get started

    1. There is a minimal time which is needed for teams to develop an outline of their product backlog, basic infrastructure and technical setup. Also, defining team norms, agreeing of certain degree of preparation for teams to start delivering any increment. Thus, the sprint 0 should have defined checklist and activities done for getting teams to get started.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    hold  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  15. Discuss the objective of the sprint before forecasting work to be done

    Scrum Guide 2017, in section Sprint Planning, states:

    The Development Team works to forecast the functionality that will be developed during the Sprint. The Product Owner discusses the objective that the Sprint should achieve and the Product Backlog items that, if completed in the Sprint, would achieve the Sprint Goal.

    I would suggest to interchange the sentences to:

    The Product Owner discusses the objective that the Sprint should achieve and the Product Backlog items that, if completed in the Sprint, would achieve the Sprint Goal.
    The Development Team works to forecast the functionality that will be developed during the Sprint.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    hold  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Product Backlog definition: change “known to be needed” to better reflect empiricism and uncertainty

    Consider changing the first sentence of the definition of the Product Backlog to better reflect empiricism and the uncertainty of complex product development.

    The current sentence is as follows: "The Product Backlog is an ordered list of everything that is known to be needed in the product."

    Consider changing the word "known" to "believed," "anticipated," or "hypothesized" - or some other way of conveying that the Product Backlog contains planned experiments to be validated through delivery of "Done" Increments and subsequent market feedback (if and when released). We don't know up front for certain what is needed.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    hold  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. describe how line management should support the Scrum implementation

    Mostly all Scrum implementations will fail, if management doesn't support them.
    So what is the role of management in Scrum?

    - Management is responsible to create the right (what's that again) environment so that people can self manage, to sponsor the Scrum team

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    hold  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  18. Two topics in Sprint review (clarify purpose)

    As the Sprint review is described in the Scrum Guide there are two distinct topics.
    1) Inspect the Increment
    2) Adapt Product Backlog

    Inspecting the Increment is looking backwards at what happened during the Sprint, while Adapt the Product Backlog is future looking given the status of the Increment, market, competitors etc.

    This distinction will clarify the purpose of the Sprint review.

    It will also help differentiate the Sprint Review topic 2 from the Product Backlog Refinement activity.

    8 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    hold  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Mention the Sprint Goal in the Sprint Review

    The Sprint Goal is mentioned 26 times in the Scrum Guide, including in the descriptions of Sprint Planning and the Daily Scrum, yet is entirely absent from the Sprint Review.

    A good place to add it might be by changing the following statement

    FROM:

    The Product Owner explains what Product Backlog items have been “Done” and what has not been “Done”;

    TO:

    The Product Owner describes the Sprint Goal and explains what Product Backlog items have been “Done” and what has not been “Done”;

    12 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    hold  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  20. to correct the faulty Sprint Goal's objective set description

    At Section "Sprint Goal" of Scrum Guide, correct the 1st sentence:
    "...through the implementation of Product Backlog." faulty
    "...through the implementation of Sprint Backlog." correct

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    hold  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →

General

Categories

Feedback and Knowledge Base