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. revise one word in the Sprint Planning section

    I see what I believe as an incorrect word in the Topic One subsection of Sprint Planning. The last sentence has "The Sprint Goal is an objective that will be met within the Sprint through the implementation of the PRODUCT Backlog", when PRODUCT should be SPRINT. Agree or disagree?

    6 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 intention behind the Scrum Master responsibility of "ensuring that goals, scope, and product domain are understood"

      The November 2017 update to the Scrum Guide added a responsibility to the Scrum Master: "Ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possible;"

      I don't think this is as clear as it could be.

      First, it's placed in the section for Product Owner. This is really a service that the Scrum Master provides to the Scrum Team. However, there isn't a section for services provided to the Scrum Team as a whole. Perhaps this would be a valuable addition. To this end, the service about helping the Scrum Team…

      6 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 →
      • Two topics in Sprint review (clarify purpose)

        As the Sprint review is described in the Scrum Guide there are two distinct topics.
        1) Inspect the Increment
        2) Adapt Product Backlog

        Inspecting the Increment is looking backwards at what happened during the Sprint, while Adapt the Product Backlog is future looking given the status of the Increment, market, competitors etc.

        This distinction will clarify the purpose of the Sprint review.

        It will also help differentiate the Sprint Review topic 2 from the Product Backlog Refinement activity.

        6 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 an Impediment List as an artifact

          The SM must work on impediments, helping the team become more productive and more happy, etc. The SM needs a list of the top X (20?) things that he/she needs to work on.
          This will lead to greater focus on removing impediments, and greater success.
          How can you build a product without a Prod Bklog (list)? How can you have continuous improvement without an Impediment List?

          Everything that can be improved (in any way) might go on the list. (There are many types of impediments.) In theory that could be lots of things (just as the PB could also be…

          5 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 →
          • Build a RACI (or RASCI) for Scrum - as a snapshot in an appendix of the Scrum Guide?

            Do you see any value in a one-page RACI addition to the Scrum Guide?

            I've been learning all about Scaled Agile Framework (SAFe), and proposed the need for a RACI. It was actually on their list for 4.0 considerations, which was nice to know. SAFe has additional roles and teams identified at the program and portfolio levels.

            Also, I had weeks of agile-based training thru ThoughtWorks back in 2010, and their training materials had so many responsibilities embedded throughout that I saw value in creating my own RACI.

            5 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 →
            • Keep it simple

              Keep it as simple as possible.

              5 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 →
              • Allow released features to be part of the increment

                It should be possible to have released (into production) be reviewed during the Sprint Review. Currently the Scrum Guide mentions that the development team delivers "a potentially releasable Increment", which might get people confused. This could indeed be understood that the increment can only be put into production when the Sprint is finished, so after the Sprint Review.
                In order to change this, I suggest to use the following: "deliver a potentially releasable or released Increment".

                5 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 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"?

                  5 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 →
                  • Change the short definition of Scrum in the guide to tell the reader what Scrum is, not its benefits

                    The beginning of the guide currently reads "Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value."

                    This tells me the benefits of Scrum, not what Scrum is, and thus is less meaningful. I would propose changing it to:

                    "Scrum is a framework where products are developed by a self-organizing team, in multiple fixed-length sprints, in full collaboration with a product owner, using Agile values and principles throughout."

                    5 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 Agile Manifesto and Explain definition of Done more clearly in the last part of scrum guide

                      Add Agile Manifesto and Explain definition of Done more clearly in the last part of scrum guide.

                      Add situation based example. like the one we have in the last part of the Management Plaza Guide

                      5 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 →
                      • Change "one calendar month" to "four weeks"

                        The text "one calendar month" implies starting on the 1st of the month and finishing on the last day of the month. It also implies 12 Sprints per year instead of 13.

                        I make this suggestion under the assumption that the intent of the phrase "one calendar month" was indeed 4 weeks.

                        5 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 →
                        • 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…

                          5 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 →
                          • 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…

                            4 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 some diagrams for the visual thinkers out there.

                              While reviewing the Guide I decided to try to organize the material into tables as a learning exercise. I mapped Team and Events, then I mapped Events and Artifacts. It was an interesting exercise deconstructing the Guide. I think having a RACI for the Team members, and some swim lanes for the Artifacts and Events might be useful.

                              4 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 →
                              • Documentation in Scrum

                                What all documentation can be done as part of Scrum? Like Design documentation, Requirement design documents..

                                We must have a some guidance from Scrum Guide on this.

                                4 votes
                                Vote
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  Signed in as (Sign out)
                                  You have left! (?) (thinking…)
                                  5 comments  ·  Flag idea as inappropriate…  ·  Admin →
                                • Use examples along with the theory to clarify the concepts.

                                  It would be nice to clearly understand the different concepts illustrated in the Scrum guide through giving examples from real-life experiences gained while implementing Scrum.

                                  4 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 →
                                  • A wrong backlog name used in Cancelling a Sprint

                                    It is in the chapter "Cancelling a Sprint":
                                    All incomplete Product Backlog Items are re-estimated and put back on the Product Backlog.

                                    Here should be:
                                    All incomplete Sprint Backlog Items are re-estimated and put back on the Product Backlog.

                                    p/s
                                    To re-estimate all incomplete Product Backlog Items looks like a huge job which does not have a big sense for a Sprint Cancelation. To re-estimate Sprint Backlog will be enough.

                                    4 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 →
                                    • Adding a 13th Principle to Agile

                                      Following reading Steve Dennings ‘Forbe’s article there appears to be a subtlety around individual mindsets that isn’t explicitly covered by Agile, perhaps the adoption of an Agile mindset is the 13th principle.
                                      The problem being that if you have your backs to the wall, you tend to adopt your ‘fight or flight’ behaviours and reset your gears, if you have adopted an underlying Agile mindset this would strengthen the resolve to stay Agile and stay embedded in Scrum.
                                      This ‘mindset’ is to believe that the Scrum Team can stay Agile, doesn’t need to send stuff up the line but can…

                                      4 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 →
                                      • Replace the word "framework" by "method" in the very first sentence of the guide.

                                        The word framework implies, that you first have to insatiate it, before you can use it. While this is formally true on an absolute scale, a big advantage of Scrum (and maybe even one of the major reasons for its success) is, that it is much more ready to use, when compared to, e.g., RUP or most other agile methods.

                                        Using the word "method" instead may also reduce the danger of Scrum being too much and too often adapted by unexperienced teams.

                                        4 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 →
                                        • Remove development team and put everyone in Scrum team

                                          Hi everyone,

                                          The current Scrum Guide says: The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master.

                                          and it also says: Scrum recognizes no sub-teams in the Development Team.

                                          So if it says no sub-teams in the development team, then why there is a development team inside Scrum team?

                                          I think remove the development team and put everyone in one team called Scrum team (which includes Scrum Master, Product Owner, and team members) would be a good idea.

                                          Thanks,

                                          Andrew

                                          4 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