General

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. 3 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  Flag idea as inappropriate…  ·  Admin →
    • Align the description of the scrum master role and the description of the retrospective

      When reading the description of the SM role, the SM is responsible for causing change to improve the productivity of the team. However when reading the english description of the retrospective, there's a broken sentence that can be read as if the scrum team is accountable for the process. Having the SM responsible for causing change to the process, while the scrum team is accountable for the process itself seems to create unwanted tension. If the SM is responsible for causing the change, why shouldn't the SM be accountable for the process?

      3 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        0 comments  ·  Flag idea as inappropriate…  ·  Admin →
      • 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…

        3 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          1 comment  ·  Flag idea as inappropriate…  ·  Admin →
        • Replace "a Sprint goal" with "a Goal" in a sentence

          Hello,

          I am referring to Scrum guide november 2017

          In section "Monitoring Progress Toward Goals" of Scrum guide (page 16), following is mentioned :
          "The Product Owner tracks this total work remaining at least every Sprint Review."

          In section "Monitoring Sprint Progress" of Scrum guide (page 17), following is mentioned :
          "The Development Team tracks this total work remaining at least for every Daily Scrum to project the likelihood of achieving the Sprint Goal."

          In section "The Sprint" of Scrum guide (page 9), following is mentioned :
          "Sprints enable predictability by ensuring inspection and adaptation of progress toward a Sprint…

          3 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            0 comments  ·  Flag idea as inappropriate…  ·  Admin →
          • 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.”

            3 votes
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              0 comments  ·  Flag idea as inappropriate…  ·  Admin →
            • 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…

              3 votes
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)
                You have left! (?) (thinking…)
                0 comments  ·  Flag idea as inappropriate…  ·  Admin →
              • Bring back the "Commitment" for Sprint Planning Topic 1, or at least after SP Topic 2.

                Forecasting is not strong enough for the creation of a plan for a Sprint. Commitment is one of the Scrum values, so it would be good to see this rather enthusiatic drive to complete a Sprint as the forecast suggests, to everybody's best knowledge and abilities, again. It was a big difference psychologically in recent Scrum Guides, and was well accepted.

                3 votes
                Vote
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)
                  You have left! (?) (thinking…)
                  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
                • 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
                  Vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)
                    You have left! (?) (thinking…)
                    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
                  • Daily Scrum: misleading sentence

                    NOV 2017 version of Scrum Guide

                    The Daily Scrum Section has the following sentence:

                    "If others are present, the Scrum Master ensures that they do not disrupt the meeting."

                    My Concerns:

                    1) Per the Scrum Guide, in the section about the Scrum Master role, the SM is NOT required to attend the Daily Scrum. So, how can the SM be responsible for non-Dev Team members speaking at Daily Scrum if the SM does not need to be present?

                    2) Per the Scrum Guide, in the section about the Scrum Master role, the SM is responsible to help the Dev Team…

                    3 votes
                    Vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      Signed in as (Sign out)
                      You have left! (?) (thinking…)
                      1 comment  ·  Flag idea as inappropriate…  ·  Admin →
                    • Add an explicit WIP limit to a sprint

                      Multitasking kills productivity and in some bad cases causes a mini waterfall in a Sprint. The best Scrum teams know they should limit the amount of stories they work on at one time. Many teams don't explicitly understand this. I propose adding an explicit WIP limit to help flow in a sprint.

                      3 votes
                      Vote
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        Signed in as (Sign out)
                        You have left! (?) (thinking…)
                        2 comments  ·  Flag idea as inappropriate…  ·  Admin →
                      • 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…

                        3 votes
                        Vote
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          Signed in as (Sign out)
                          You have left! (?) (thinking…)
                          1 comment  ·  Flag idea as inappropriate…  ·  Admin →
                        • 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.

                          3 votes
                          Vote
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            Signed in as (Sign out)
                            You have left! (?) (thinking…)
                            0 comments  ·  Flag idea as inappropriate…  ·  Admin →
                          • 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;

                            3 votes
                            Vote
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              Signed in as (Sign out)
                              You have left! (?) (thinking…)
                              0 comments  ·  Flag idea as inappropriate…  ·  Admin →
                            • Why we plan for next 24 hours in daily scrum?

                              In Daily Scrum, more precisely, plan should be for next 8 or 9 working hours and not for 24 hours.

                              3 votes
                              Vote
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                Signed in as (Sign out)
                                You have left! (?) (thinking…)
                                2 comments  ·  Flag idea as inappropriate…  ·  Admin →
                              • Clarify whether in-sprint change is OK, or verboten - and effect on acceptance criteria

                                Guide says that "Sprint Goal gives the Development Team SOME FLEXIBILITY regarding the functionality implemented within the Sprint" and "if the work turns out to be different than the Development Team expected, they collaborate with the Product Owner to negotiate the scope of Sprint Backlog within the Sprint."

                                This change seems pretty significant but wasn’t addressed in the webinar or summaries of the 2017 guide changes. It seems a reversal of traditional guidance to minimize or eliminate changes to functionality during the sprint, to expose improvement areas and encourage transparency.

                                Also, does the “work” –refer to tasks, or the actual…

                                3 votes
                                Vote
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  Signed in as (Sign out)
                                  You have left! (?) (thinking…)
                                  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
                                • Clarify optional participants of Daily Scrum

                                  When I read the Scrum Guide last time I got a bit confused, because I read "The Scrum Master enforces the rule that only Development Team members participate in the Daily Scrum.". So strictly speaking even the Scrum Master himself could not participate. I think the German version is more precise because it talks about "active participation". Maybe this is misleading especially for foreign speakers.

                                  2 votes
                                  Vote
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    Signed in as (Sign out)
                                    You have left! (?) (thinking…)
                                    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
                                  • clarify the "Scrum Master Service to the Product Owner" section

                                    It is not clear who the "target" of individual activities is in this section ("service to the development team" is much clearer). For example, should the SM or the PM understand product planning in an empirical environment. Should "helping the Scrum Team understand the need for clear and concise product backlog items" read "helping the Product Owner understand..."?

                                    2 votes
                                    Vote
                                    Sign in
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      Signed in as (Sign out)
                                      You have left! (?) (thinking…)
                                      1 comment  ·  Flag idea as inappropriate…  ·  Admin →
                                    • 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.

                                      2 votes
                                      Vote
                                      Sign in
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        Signed in as (Sign out)
                                        You have left! (?) (thinking…)
                                        1 comment  ·  Flag idea as inappropriate…  ·  Admin →
                                      • Improve readibility by removing "he or she" when talking about PO

                                        When talking about Scrum Master "he or she" is not used. If gender is an important issue you could add a section about why using just male form as used often in books to improve readibility of the descriptive text.

                                        2 votes
                                        Vote
                                        Sign in
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          Signed in as (Sign out)
                                          You have left! (?) (thinking…)
                                          0 comments  ·  Flag idea as inappropriate…  ·  Admin →
                                        • 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.

                                          2 votes
                                          Vote
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            Signed in as (Sign out)
                                            You have left! (?) (thinking…)
                                            0 comments  ·  Flag idea as inappropriate…  ·  Admin →
                                          • Don't see your idea?

                                          General

                                          Feedback and Knowledge Base