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. Link to all headings

    I believe it would be very helpful for those of us who are referencing the scrum guide to be able to send links to our colleagues to section of the scrum guide.

    I have observed that currently many h2 and h3 heading elements have html id attributes and are referable by appending the id as the fragment in the URL (http://www.scrumguides.org/scrum-guide.html#theory).
    However some are missing and I think any section worthy of a heading should be referable (all heading elements - h1-h6).
    So what I am proposing is to ensure that all heading elements have an html id…

    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 →
  2. Move "writing PBIs" from PO to Team

    The Scrum Guide lists as one of the responsibilities of the PO:
    "Clearly expressing Product Backlog items"

    And then adds:
    The Product Owner may do the above work, or have the Development Team do it. However, the Product Owner remains accountable.

    In my experience one of the biggest problems with the PO role is that POs tend to become backlog managers, mainly writing User Stories.

    Customer contact and prioritization/ordering of PBIs isn't done properly.

    In most cases it turned out to be a good idea to involve the team in creating User Stories or even delegate it to the team.…

    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 →
  3. Scrum Master service to the Scrum Team

    Suggestion: add one more section "Scrum Master service to the Scrum Team"

    There are some items in "Scrum Master service to the Product Owner" that should belong in "Scrum Master service to the Scrum Team".

    - Helping the Scrum Team understand the need for clear and concise Product Backlog items;
    - Understanding and practicing agility; and,
    - Facilitating Scrum events as requested or needed.
    Ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possible;

    It does not make sense to put these items under "Scrum Master service to the Product Owner"…

    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 →
  4. Publish change summary from previous version of guide

    Please publish a summary of changes from one version to the next at the end of the guide or as a companion.

    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 →
  5. Change wording of increment definition

    "The Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints."

    I think this counts things from previous increments multiple times.

    If sprint 1 has value 5, the increment has value 5. Then if sprint 2 has value 4, then the increment has value 4+5=9. Then if sprint 3 has value 6, the increment has value 5+9+6=20. We've counted the value from sprint 1 twice.

    I think a better wording would be "The Increment is the sum of all the Product Backlog items completed during a…

    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. Business loyalty to the authors of the Scrum Guide

    Dear Jeff and Ken,
    Please find for your review and possible comments another graphical representation of the content of the Scrum Guide.

    As per CC BY SA, your names have been mentionned and the graphic placed under CC BY SA.

    For business loyalty, your respective companies ScrumInc and Scrum.org are mentionned with links to them.

    http://mutation-moa-moe.blogspot.fr/2017/12/infograhie-scrum-guide.html

    Best regards
    Tru

    Tru Do-Khac; Paris, France

    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. Consistently capitalize the words "Increment" and "Increments"

    The Increment is the only artifact that isn't consistently capitalized in the Scrum Guide (i.e., it appears sometimes as "Increment" and other times as "increment"). (Note that this is an issue for the plural form too.)

    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 →
  8. explicitly add that Scrum is an agile framework

    change definition of Scrum adding it is an agile framework

    Scrum (n): A(n agile) framework within which people...

    0 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 →
  9. Scrum Master is not only a servant leader for the Scrum Team

    Scrum Guide says: The Scrum Master is a servant-leader for the Scrum Team.

    Proposed change: The Scrum Master is a servant-leader for the Scrum Team and the whole organisation.

    Rationale: for the Scrum Team to be able to deliver and work effectively, the Scrum Master can not just serve the Scrum Team in isolation. The Scrum Master needs to spend his time serving others outside of the Scrum Team too. Changing this will also make many Scrum Masters who is only focused serving the Scrum Team to think that others outside of the Scrum Team need to be served too…

    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 →
  10. Add Risk Management in the Scrum Guide

    Risk Management is inherent to Scrum, but there isn't much information about it. Guidance is needed on when and how to detail and manage risks throughout a Scrum project. I have some ideas about how risk management should be incorporated in Scrum, as a risk management SME and Agile generalist.

    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. What vs How

    Should you add words describing a Separation of Concerns for team members? Should it state that a Product Owner should focus their concerns on "What" needs to be delivered while the Development Team should focus on "How?" Would this make it easier to understand roles?

    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. They are self-organizing. No one tells the Development Team how to turn (X) Product Backlog (X) into Increments of poten

    Hello

    I keep reading this sentence in the guide and wonder if the word "the" or "item" or "items" is missing either side of "Product Backlog". Please advise?

    wit thanks

    They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn [THE] Product Backlog ITEM/S] into Increments of potentially releasable functionality;

    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. Daily Scrum

    In the Nov 2017 edition under Daily Scrum chapter Page:12, it is mentioned: Daily Scrum is held everyday and the team plans activity for next 24 HRS. Was the author referring to 8 working HRS when he said 24 HRS? Can any one throw some light on this, if I am missing something.
    If not, since Agile is very critical to time the Author would have had some idea in specifying 24 HRS

    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. Advocate smaller and more frequent retrospectives, to ephasize the value of continuous improvemenent

    In dysfunctional teams, a strong emphasis is placed on the daily stand-up, because it is a window through which management can micromanage. There is a tendency to plan to full capacity, with no slack, a tendency to apply pressure to the team to deliver, and hence a tendency for the team to fall behind. In many teams, to "save time", the retrospective is held infrequently or dropped, or has no useful outcome because problems are able to go unchecked and grow, becoming harder to get traction on solving.

    If scrum were to advocate making retrospectives smaller, and more frequent, it…

    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. Release Planning - Which can help us to predict the time taken to release the Minimum Viable Product

    It would be great if we can define some guidelines on how to do the release planning which helps us to predict the product delivery timelines.
    At the end of the day, product delivery matters the most.

    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. Clarify the idea of continuous improvement as part of the Sprint Backlog

    In the section on the Product Backlog, it says that the Product Backlog "lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases". It also says that Product Backlog Items (which are presumed to be the only content of the Product Backlog) "have the attributes of a description, order, estimate, and value". The section on the Sprint Backlog says "the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal".

    The November 2017 updated modified this paragraph…

    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. Add Scrum Team pattern(s) for successful scaling

    In an ideal world, a team owns it dependencies. As a larger organization adopts Scrum and leverages across a complex product / services environment where many products are leveraging 10's to 100's of services, describe pattern(s) for how teams can effectively organize to ensure their service can scale to meet the need of its users. We have some complex services that require many Scrum teams to deliver the service. Complicating matters, there are many products consuming this service and the service teams delivering the service are always a bottleneck. We've tried various patterns and have one that works now, but…

    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 →
  18. What prequalufications can be added as must for a CSM? It’s a lack of this that has devalued what it could bring!

    If anyone can get it in 2 days it is cheap and allows quality to dilute.
    If it needs a pre qualification and rigor in auditing it then maybe you can save the demise

    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. All Scrum Team members should be allowed to answer in the Daily Scrum

    Near the end of the "Daily Scrum" sections it says: "The Scrum Master enforces the rule that only Development Team members participate in the Daily Scrum."

    This implies that the PO and the SM can NOT be transparent (in the DS) about what they did, and what problems they had.

    This implies (to many) that the Doers are giving a status update to the PO and SM.

    It is better for overall Team chemistry that the PO and SM are also transparent.

    It is also necessary that they ALL realize that only when all pull together will they have 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  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  20. Break up the "Increment" paragraph to make it more skimmable.

    The paragraph on Increment discusses backlog items completed.
    And that it must be "done"
    And that the PO decides whether to release.

    This would stand out better as three small paragraphs than one big one. The typographical change would help prevent people from missing the point about doneness and the point about release.

    The text doesn't need to change other than to break into paragraphs for easier consumption.

    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 →

General

Categories

Feedback and Knowledge Base