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. Agile for individual work

    The Guidebook says the agile framework is effective for appropriate number of team members, but I think the principle, such as putting emphasis on transparency or priority, also will be effective for the tiny team or even for the person working individually.

    1 vote
    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 →
    • Scrum Master should understand the domain or product on which team is working

      I have been observing in one of the Scrum teams that they tried introducing a new Scrum Master who is unaware of the technology and product on which the team is working. Scrum Master contributes only by asking team members to put comments on their user stories, estimate them and sending mails and calendar invites. After 3 months of waiting (where I assumed that Scrum Master will be able to develop product understanding and contribute to team), I see team is still not able to get even a single benefit from Scrum Master. Due to this, even some team members…

      1 vote
      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: Replace 3 questions, even when they are optional

        Even when Nov 2017 version made the "3 questions" optional, they are still used by new practitioners, and most of the time, contributes to the micromanagement feeling toward Daily Scrum. Following https://medium.com/@i_2412/daily-standup-most-misunderstood-events-of-scrum-2562a9b3a1d8 , I suggest we drop them all together, or if mentioned, should focus on the Goal and the work, no "who does what"

        (z.) What is our (Sprint) Goal?
        a. What was done to this SBI since the last Daily Scrum?
        b. What will be done to this SBI after this Daily Scrum?
        c. Is there any impediment that prevents this SBI from being completed?

        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 →
        • Honour Mike Beedle

          It would nice if the history section of the Scrum Guide made mention of Mike B.

          13 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 →
          • Why Sprint Goal inspection at least monthly?

            When we read (in the section Sprint) that “Sprints enable predictability by ensuring inspection and adaptation of progress toward a Sprint Goal at least every calendar month.” it simply says to us that the progress toward a Sprint Goal is inspected/adapted at least monthly. However, we know that on a daily basis the same is done in the Daily Scrum event: “The Development Team uses the Daily Scrum to inspect progress toward the Sprint Goal”. As a result, these two may look mutually contradicting. Suggest correct the first one.

            1 vote
            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 "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".…

              1 vote
              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 →
              • Discuss the objective of the sprint before forecasting work to be done

                Scrum Guide 2017, in section Sprint Planning, states:

                The Development Team works to forecast the functionality that will be developed during the Sprint. The Product Owner discusses the objective that the Sprint should achieve and the Product Backlog items that, if completed in the Sprint, would achieve the Sprint Goal.

                I would suggest to interchange the sentences to:

                The Product Owner discusses the objective that the Sprint should achieve and the Product Backlog items that, if completed in the Sprint, would achieve the Sprint Goal.
                The Development Team works to forecast the functionality that will be developed during the Sprint.

                1 vote
                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 →
                • Introduce the concept for non IT systems to use Scrum

                  For now it very focused on building complex products. However, based on the framework best practices how it can used for non IT industries can be a good starting point.

                  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 →
                  • Introduce the concept of Sprint 0 for teams to get started

                    1. There is a minimal time which is needed for teams to develop an outline of their product backlog, basic infrastructure and technical setup. Also, defining team norms, agreeing of certain degree of preparation for teams to start delivering any increment. Thus, the sprint 0 should have defined checklist and activities done for getting teams to get started.

                    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 →
                    • You don't turn the Product Backlog into Increments, but the items on the Product Backlog

                      On pag 7, at the first bullet of the paragraph "The Development Team" the text says "...how to turn Product Backlog into Increments...".
                      I suggest the word "items" is added to the text. So then it would be "...how to turn Product Backlog items into Increments..."

                      Paragraph "Product Backlog" teaches us that "The Product Backlog is an ordered list of everything that is known to be needed in the product." So the Product Backlog is a list with items, and the items are turned into the increment. The list itself is not turned into an increment, but remains a list.

                      1 vote
                      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 →
                      • Suggestion for improving the way information about Scrum is presented

                        It would be great if there was a graphic summary of the Scrum roles, artifacts, events,etc. to supplement the text.

                        1 vote
                        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 who can add to the Product Backlog

                          Is the Product Backlog a transparency, inspect and adapt opportunity? If yes, can anyone add to the Product Backlog? Ideally it would be yes so that the Product Owner is not see as an administrative assistant. If someone adds, ideally it triggers a conversation with the PO for their inspection and adaptation. A clarification would be helpful as many interpret "manage" to mean the PO is the only one who can add.

                          18 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 identification with Team and Sprint Goal in Daily Scrum questions

                            Adapt the 'Three Questions' in Daily Scrum to make things clearer:

                            • What did I do yesterday that helped my team meet our Sprint Goal?
                            • What will I do today to help my team meet our Sprint Goal?
                            • Do I see any impediment that prevents me or my team from meeting our Sprint Goal?

                            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 →
                            • 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 →
                              • Change word "priority" to "order"

                                Product Owner is responsible for...Ordering the items in the Product Backlog to best achieve goals and missions;

                                Later in the following sentence word "priority" is used. Can this be changed to order?

                                Existing:
                                The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item’s priority must address the Product Owner.

                                Proposed:
                                The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item’s order must address the Product Owner.

                                1 vote
                                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 →
                                • 1 vote
                                  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 →
                                  • appoint successors for Ken and Jeff, who should further adapt the Scrum Guide

                                    I know it's a creepy thought, but we all know life is short, and all sorts of things can happen.

                                    In the future those people who will be new to Scrum, will find it reassuring to know that the responsibility for further advancing the Scrum Guide was granted jointly and personally by both Jeff and Ken to certain individuals, who will be the new Scrum Leaders in the absence of the founding fathers.

                                    In other words, putting Ken' and Jeff's successors name in the Scrum Guide will make it clear who picks up the torch and takes Scrum further.

                                    1 vote
                                    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 the team-in-a-team working.

                                      To me, there is only one team, made up of an SM, PO, and developers. Right now, the SG says that the "Scrum Team" contains an SM, PO, and a separate "Dev... team." That statement is interpreted by many as meaning that the SM and PO are not really part of the team, and that any tension of conflict between (most often) the PO and the "team" is deliberate and useful. Is that the intent of using the team-in-team structure? If not, then I'd get rid of it and just say that the Scrum Team is made up of a…

                                      1 vote
                                      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 →
                                        • 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 →
                                          ← Previous 1 3 4 5 8 9
                                          • Don't see your idea?

                                          General

                                          Feedback and Knowledge Base