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. 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. Correct the 3 questions in the Daily Scrum

    Usually the Daily Scrum meeting is held around the beginning of the day, but that's not a rule, and in many cases (because of time zones) it is not even true.

    The Scrum Guide doesn't state that when the Daily Scrum should be done, it only suggests to have it in the same time (and place) every day: "The Daily Scrum is held at the same time and place each day to reduce complexity."

    Then, right after this, the 3 questions (I'm quoting the first 2) are mentioned:
    "What did I do yesterday that helped the Development Team meet 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. A fourth Daily Scrum question

    One of my Scrum Master mentors, or some Scrum article from the distant past recommended this 4th Daily Scrum question (that I now always use):

    Did I discover any requirements (new or existing) that the Scrum Team should be made aware of?

    Sometimes a developer may realize when looking at a particular item in the Sprint Backlog that they could knock off another item in the Product Backlog that is not in the Sprint if they spent an incrementally small amount of additional time. There is a natural tendency to not want to mention it because of perceived (and real)…

    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 →
  4. 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. 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. Sentence in Scrum Guide requires multiple increments for each Sprint

    "The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team’s current definition of “Done.” "

    Suggest instead:
    "The purpose of each Sprint is to deliver one or more Increments of potentially releasable functionality that adhere to the Scrum Team’s current definition of “Done.”

    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. Add below brief video as an introduction

    We tend to read less and watch more movies instead.
    With that in mind I created this video which you could consider adding as an alternative or first introduction.
    https://m.youtube.com/watch?v=tr7ODpD8f8o

    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. Using Scrum for data mining/analytics projects

    It would be extremely useful to post some tips on how to successfully implement Scrum on data mining/analytics projects, particularly for those that follow a data mining framework like CRISP-DM.

    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 →
  9. Hindi translation of Scrum Guide

    I am doing Hindi translation of Scrum Guide. What is the process to make it avialble on scrumguide.org

    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. Tighten up "Helping the Development Team to create high-value products;"

    "Helping the Development Team to create high-value products;" is a phrase ascribed as a task for the SM. It seems a bit vague in it's context. If what you mean is that the SM does this when he encourages and teaches all the Scrum rules, then I understand. But in it's current context it seems like another action to perform but an action that isn't really defined.

    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. Add opportunity enabler verbiage to last question of Daily Standup

    Add this verbiage to the last question of the Daily Standup: "..., or see any opportunity enablers that if implemented can improve team performance to meet 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 →
  12. Add Definition of Ready to Scrum guide

    Ready has been emphasized in the 2013 Scrum Guide update and we need to emphasize it further.

    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. add some recommendations for the daily scrum - using a timer fixed to a holder on the scrum board

    Fixing the timer on the scrumboard so that everybody in the team can see the time one is allowed to speak has different advantages:
    - the speaker can move cards free hand
    - listeners don't get nervous if they think somebody talks too long, they see and know if somebody has the right to speak
    - the speaker also can see the time and can speed up etc

    I think the aim of having the daily scrum timeboxed but still all people in the team could tell their status is easier to reach if you use such a timer and…

    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 →
  14. Alternative less dogmatic scrum

    Developing software is hard and requires much critical thought and analysis of the problem.

    Another massive problem is the outside world expecting predictions about when something will be done and how much it will cost. The 'lets just start and see where we end up' model is so much better. They don't understand such predictions are always lies and are shocked when something goes over budget or takes more time.

    But people always want to avoid facing the hard problems. It seems Scrum has become very rigid to force them to face those problems. Even though dogma's don't actually work…

    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. 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 →
  16. Retrospectives should not be about individual people

    The Sprint Retrospective section says (July 2013):

    "Inspect how the last Sprint went with regards to people, relationships, process, and tools"

    From a humanistic / servant-leader / Deming perspective, I feel "people" is not a good word to use here, since it can easily be misunderstood or misconstrued. "Relationships" probably already covers the associated issues.

    But if we want to discuss people issues explicitly here (rather than out-of-band), then I would hesitantly suggest "behaviours" as a replacement. And I would put it last, not first.

    [Aside: When articulating such a Retrospective list, I usually also call out "policies" explicitly. Although,…

    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 →
  17. Change the term "Backlog Refinement" to "Sprint Lookahead"

    I realize that this term has just changed in the last version of the Scrum Guide, and is an improvement over the previous term used (grooming). However, with new teams, one of the frequently asked questions (and sometimes misinterpretation) is that the "Backlog Refinement" is an activity that the PO should do alone, in isolation. Changing the title to "Sprint Lookahead" communicates the idea that this is an activity for the entire Scrum Team, and that this is an opportunity to "Plan Ahead", for future Sprint(s).

    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. SCRUM has two different types of retrospective

    We found our retrospectives only skimmed the surface of our our issues where so we did a retrospective that looked at what our principles should be for our Scrum team we discovered some deep niggly interteam problems that infact were easily solved once we identified them. We has a session in three parts: theoretical review of the SCRUM guide (avoiding discussions about how we do it) while at the same time people noted themes and issues on postis, then we grouped our postits into the themes and for each wrote down problems and solutions, then we summarised it in 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 →
  19. 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 →
1 2 3 4 5 6 8 Next →

General

Categories

Feedback and Knowledge Base