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. Daily Scrum: Replace 3 questions, even when they are optional

    Even when Nov 2017 version made the "3 questions" optional, they are still used by new practitioners, and most of the time, contributes to the micromanagement feeling toward Daily Scrum. Following https://medium.com/@i_2412/daily-standup-most-misunderstood-events-of-scrum-2562a9b3a1d8 , I suggest we drop them all together, or if mentioned, should focus on the Goal and the work, no "who does what"

    (z.) What is our (Sprint) Goal?
    a. What was done to this SBI since the last Daily Scrum?
    b. What will be done to this SBI after this Daily Scrum?
    c. Is there any impediment that prevents this SBI from being completed?

    13 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 →
  2. remove the notion of the PO accepting PBI's

    In the section on cancelling a sprint there is the text " If part of the work is potentially releasable, the Product Owner typically accepts it".
    This suggests that the PO is the person accepting the work done in the sprint.
    Doing so implicitly makes the PO the Boss of the team. If I can accept or reject your work, I am clearly in a power position towards you. This is not in line with the description of the team and the roles, where the PO is *part of* the Scrum Team.
    In the rest of the Scrum Guide there…

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

    We’ll send you updates on this idea

    hold  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Additions to Sprint Retrospectives... borrowed from the Nexus Guide

    Often retrospectives in Scrum teams are not deep enough and focused enough. One of the tools I use is elements of the Nexus guide to facilitate the scope of retrospectives even in one-team Scrum. I just the following be added to the Scrum Guide in the Sprint Retrospectives section (wordings completely borrowed from the Nexus Guide)

    Every Retrospective should address the following
    subjects:
    • Was any work left undone? Did the Sprint generate technical debt?
    • Were all artifacts, particularly code, frequently (as often as every day) successfully integrated?
    • Was the software successfully built, tested, and deployed often enough…

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

    We’ll send you updates on this idea

    hold  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Clarify why the wording "no exceptions to this rule" is not in the Revision history of latest guide

    Can anyone clarify why the sentence "there are no exceptions to this rule" has been removed under the section of the Development Team where it states that Scrum recognizes no sub-teams or titles. This is not there under the revision history as well.

    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. Improve the 3 suggested questions for the Daily Scrum

    I will just start by saying that I don't like the 3 questions being present on the Scrum Guide.
    That being said, as a PST, I've been focusing on how to move people away from the status report mindset since they are so attached to the questions.
    Here is my take:

    Currently the questions are:
    What did I do yesterday that helped the Development Team meet the Sprint Goal?
    What will I do today to help the Development Team meet the Sprint Goal?
    Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?

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

    We’ll send you updates on this idea

    hold  ·  3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. How inclusive is a "Scrum Master"?

    8 March 2019, as we celebrate International Women's Day today, a thought comes to my mind with the term "Scrum Master" and how inclusive it is? Before I proceed, it makes sense to clarify that the term Master utilised by the Scrum Guide addresses a skilled practitioner of a particular art or activity.

    Sadly, our search engines and dictionaries don't do enough justice to this term. The most widely accepted meaning for the word Master as per our favourite search engines and dictionaries still call it "a man who has people working for him, especially servants or slaves"; other meanings…

    3 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 →
  7. Make explicit how many Events there are in Scrum. Is it 4, 5, (or 6 or even 7)?

    Please can we make it clearer how many Events there are in Scrum?

    Four formal events are listed: (page 5)
    - Sprint Planning
    - Daily Scrum
    - Sprint Review
    - Sprint Retrospective

    Then another event is defined (page 9)
    - The Sprint (although not as an inspect and adapt event)

    Then under the same Scrum Events heading (page 10) we meet:
    - Cancelling a Sprint (could it be meant to be seen as an Event?)

    Then I have read the argument in this area for one other:
    - Product Backlog refinement. Here PBIs are "reviewed and revised" (inspection and adaptation)

    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 →
  8. All the scrum starters might find it difficult to digest all the information. May be a small problem can be presented with examples

    All the scrum starters might find it difficult to digest all the information. May be a small problem can be presented with examples and templates. For e.g. after daily scrum calls how and where the daily standup notes are published. How they are tracked to closure. May be scrum experts can record a video of various events and compile them and present it. This will be very specific and after understanding the overall framework if anyone watches this then they can easily relate things. This will help people to quickly adopt and expertise scrum.

    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 →
  9. Re-estimate incomplete Sprint goals... in Sprint Review

    The Scrum guide talks about the cancellation of a Sprint. In that context it asks to "All incomplete Product Backlog Items are re-estimated and put back on the Product Backlog."

    Would this not be true for items not completed in a Sprint as well? So I suggest that this be added to the Sprint Review as well so that the Product Backlog is accurate at the end of the Sprint (since in most cases refinement should be already completed).

    Optionally, this can be added in Sprint Planning as a step for items not completed in a previous Sprint (though this…

    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 →
  10. Change "Backlog" To "Options"

    Definition of "Backlog" is:

    an accumulation of uncompleted work or matters needing to be dealt with

    Backlog implies work is uncompleted. Whereas we should encourage the idea and mindset that it is an "option".

    Product Backlog changed to Product Options:

    Options of feature or capability to be added to product which are to be tested in market.

    Sprint Backlog changed to Sprint Options:

    Options that teams will try to work on in this sprint.

    Improvements Backlog to Improvement Options:

    Improvements options identified during retrospectives which can be experimented by the team during the coming 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  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  11. Clarify who can add to the Product Backlog

    Is the Product Backlog a transparency, inspect and adapt opportunity? If yes, can anyone add to the Product Backlog? Ideally it would be yes so that the Product Owner is not see as an administrative assistant. If someone adds, ideally it triggers a conversation with the PO for their inspection and adaptation. A clarification would be helpful as many interpret "manage" to mean the PO is the only one who can add.

    9 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 →
  12. Retrospective Board

    Dedicate part of the team board to share areas of improvement to the process instantly to that board. This will minimize retrospective meeting time as it will be just a review to items already posted to that board

    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 →
  13. Please help me find the audio for "The Scrum Guide"/I had it before

    Please help me find the audio for "The Scrum Guide"/I had it before, and now I cannot locate the aduio.

    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 →
  14. Empathy should be one of the values of the scrum beyond those already existing

    Empathy is an important value to build high performance teams once individuals aren't machines

    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 →
  15. improve the daily scrum questions to support "best effort" in the sprit of continuous improvement

    Human behavior is established when you focus on "doing your best" every day according to Marshall Goldsmith "Triggers" being one of the sources.

    I suggest that the three questions be changed to exhibit that ask (just like we have moved commitment to forecast of Sprint goals

    What best effort did I do yesterday that helped the Development Team meet the Sprint Goal?
    What best effort will I do today to help the Development Team meet the Sprint Goal?
    Do I see any impediment that prevents me or the Development Team from our best effort towards meeting the Sprint Goal?

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

    We’ll send you updates on this idea

    hold  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Change "if appropriate and not in conflict with product or organizational standards."

    In the Sprint Retrospective section of the Scrum Guide it says "During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of "Done", if appropriate and not in conflict with product or organizational standards."

    I feel that the words "if appropriate and not in conflict with product or organizational standards." are driven by corporate bureaucracy thinking and pressures from corporates on Scrum.

    What happens if those "standards" are the essence of what is destroying Scrum? If those standards are the things that are impeding the team, surely they should…

    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 →
  17. Revise the character "informal" from the sprint review meeting.

    First the description then a suggestion below it.
    Description:
    In the Scrum guide v. Nov-2017. In Scrum Review section the text contains: "This is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration."

    I can't experience any practical effect of the word 'informa meeting'. As English is not my native language, I am not sure if 'informal meeting' has any effect on others. I also asked some coaches,trainers,other scrum masters about what is ment by it. I know the translation of the word, but does it affect our…

    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 →
  18. Product Backlogs are actually prioritised not ordered.

    The change of Product Backlog from prioritised to ordered is actually an error. Priority means "the fact or condition of being regarded or treated as more important than others."

    This is what we do with PBs. Whether because of risk, or value, or technology - We always work on the most important first.

    Ordered just means "has an order" - In that way we could use scrum and legitimately work on the meaningless nice to haves rather than the key aspects of the product.

    This also over empowers the PO role as it means they can decide in totality without…

    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 →
  19. Revise some statements about DoD to make clear who owns it

    I was having a discussion today with some students and they were confused by some wording used on the Scrum Guide.
    There is two sections on the scrum guide that uses "Scrum Team’s current definition of "Done"" and "Scrum Team’s definition of "Done"" and then we go on about the Development team defining de DoD at the end of the guide.
    The student seemed very confused by it, because both cases come before the clarification that the DoD is defined by the Dev Team.

    Even though I get what we meant by "scrum team's definition of done" I suggest rewording…

    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 →
  20. Correct user guide?

    In the guide, under "Scrum events" it says "Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process."
    I believe it should say "whenever the purpose of the sprint is achieved". Should this be corrected?

    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 →
← Previous 1 3 4 5 6 7 8

General

Feedback and Knowledge Base