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. 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 →
  2. 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 →
  3. 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. Add a paragraph break between 2 logically distinct topics in the Definition of "Done" section

    The 2nd paragraph in the section on the Definition of "Done" is somewhat long and contains 2 logically distinct topics. Below is the current text followed by the proposed text with added paragraph break where I think it would be helpful:

    CURRENT TEXT:

    The same definition guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning. The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team’s current definition of “Done.” Development Teams deliver an Increment of product functionality every Sprint. This Increment is…

    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 →
  5. 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 →
  6. Fix typo and revise wording for: “Fewer than three Development Team members decrease interaction and results in smaller productivity gains.”

    There is a typo in the statement: “Fewer than three Development Team members decrease interaction and results in smaller productivity gains.” Instead of “decrease” it should say “decreases.”
    I think it also would be slightly clearer to start the sentence with “Having”, i.e.: “Having fewer than three Development Team members decreases interaction and results in smaller productivity gains.”

    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 →
  7. The PO can do the above work or have the Team do it... Seems an excuse for the PO to do nothing, even if he/she remains accountable.

    The PO can ask the Team to help him/her to do the above things. How can you manage your backlog if you're allowed no not even touch 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  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Remove estimating and re-estimating from Sprint Cancellation section

    In the 3rd paragraph of the section "Cancelling a Sprint" is stated:

    "When a Sprint is cancelled, any completed and “Done” Product Backlog items are reviewed. If part of the work is potentially releasable, the Product Owner typically accepts it. All incomplete Product Backlog Items are re-estimated and put back on the Product Backlog. The work done on them depreciates quickly and must be frequently re-estimated."

    Estimating half complete work and putting it back on the backlog is a bad practice, which is seen in immature Scrum teams who struggle to complete items within the Sprint timebox. So let's not…

    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 →
  9. Prescribe a productivity model that is not just Velocity or Story Point based but focused on timely delivery of tasks *within* the Sprint.

    That is, give priirity to delivering tasks as per estimate over tasks delivered per Sprint as measure of high productivity.

    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 →
  10. change the name and content of the "Sprint Backlog" as it is not the same sort of thing as the "Product Backlog"

    As someone new to Scrum I find the naming of the Sprint Backlog is very confusing.

    Comparing it to the Product Backlog, I initially expected it to consist of a list of Sprint Backlog items: i.e. Product Backlog Items which were to be "done" during the Sprint.

    However it also contains the plan for delivering the Product Increment and realising the Sprint Goal. This does not seem to be reflected in the word "Backlog" at all.

    There is also the SPRINT GOAL which is an important part of the Sprint, but is NOT included in the Sprint Backlog. In fact…

    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. clarify/remove "Monitoring Progress Toward a Goal" (page 14 - Scrum Artifacts)

    This is obviously an important function of a Project Manager (or Product Owner?), however it does not sit well here.

    Goal (as used here) is not a Scrum artifact.

    This is obviously not the Sprint Goal as it is only tracked at the Sprint Review. In fact, having goals within Scrum which are longer than a Sprint seems to work against the Agile nature of the development. At the beginning of each Sprint you look at what the market and technological conditions are and what you want to achieve.

    Longer term goals should be defined by the stakeholders and, if…

    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. Concept of "The Sprint"

    Questionable in the ScrumGuide.

    I am not sure when Jeff & Ken decided "The Sprint" would include all meetings. Maybe when you decided sprints (iterations) should run back to back? Remember those discussions and my first sprints as a Scrum Master had gaps between sprints where we would work on the Product Backlog and get PBI's "Ready".

    However, when I hear your talks, read articles, read the ScrumGuide, there is plenty of hints that the Sprint is after sprint planning and before sprint review.

    Sprint planning: As the words say you plan the work for the sprint. How can you…

    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 →
  13. Change Scrum Master to Scrum Guide...or something...

    Wanted' Scrum Master to lead our Three Ring Circus, or, Is the term “Scrum Master” a Misnomer that needs to be updated?
    Edit article
    Published on May 9, 2017
    LikeWanted' Scrum Master to lead our Three Ring Circus, or, Is the term “Scrum Master” a Misnomer that needs to be updated?0Comment0ShareShare Wanted' Scrum Master to lead our Three Ring Circus, or, Is the term “Scrum Master” a Misnomer that needs to be updated?0
    Douglas Bock
    Douglas Bock
    Agile Business Analyst / Product Owner
    "The Show Must Go On"...must it, really? Let's save our servant leaders! If you visit http://www.indeed.com/ today…

    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 →
  14. Call out the Scrum rules

    "This Guide contains the definition of Scrum. This definition consists of Scrum’s roles, events, artifacts, and the *rules* that bind them together."

    Roles, events, and artifacts are explicitly identified in the Scrum Guide, but the "rules" are not. Is any paragraph in the Scrum Guide containing words like "must", "only", "no one", "not allowed" a rule?

    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. Review paragraph on Inspection (page 4)

    " Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances. Their inspection should not be so frequent that inspection gets in the way of the work. Inspections are most beneficial when diligently performed by skilled inspectors at the point of work."

    (1) Who are the Scrum *users*? This isn't defined in the guide. This is the only occurrence of the word "users" in the Scrum Guide. Shouldn't be changed to Scrum Teams?

    (2) "inspect Scrum artifacts and progress toward a Sprint Goal..." seems insufficient. How about processes, practices, interactions, etc? Shouldn't be…

    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. Fix apparent typo on page 8

    It says: "Sprints enable predictability by ensuring inspection and adaptation of progress toward a *Sprint Goal* at least every *calendar month*."

    inspection and adaptation toward a Sprint Goal happens every day during the Daily Scrum. I guess the intent was to reference a longer-term *goal* (e.g., release), not 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  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Remove process discussion from Sprint Review

    The Scrum Guide contains a long list of topics that should be addressed in the Sprint Review. One of them is: "The Development Team discusses what went well during the Sprint what problems it ran into, and how those problems were solved". This should be done in the Retrospective.

    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. implementing scrum

    Implementing and practising scrum in an organisation that breathes and lives traditional methodologies (PRINCE etc) - this cannot be done with the ongoing blessing of the 'Management' - Managers, Directors etc.

    For a successful SCRUM implementation and practice, I suggest that scrum guide includes a dedicated chapter for this to clearly make a statement about the needed powers and influence to be bestowed upon the scrum master and product owner, how this can/should be done, when and how frequently this should be reinforced...

    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 →
  19. Add Goal? to the first sentence (a.), it is a typo.

    a.What did I do yesterday that helped the Development Team meet the Sprint
    b.What will I do today to help the Development Team meet the Sprint Goal?
    c.Do I see any impediment that prevents me or the Development Team from 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  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  20. Clarify the Scrum Master role in the Sprint Retrospective

    In the section on the "Sprint Retrospective", the last sentence appears to be grammatically incomplete. It reads...."The Scrum Master participates as a peer team member in the meeting from the accountability over the Scrum process". Were some words accidentally left out? Should it have read like this....."from the perspective of accountability over the Scrum process"?

    4 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 →

General

Categories

Feedback and Knowledge Base