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. Plan for implementing improvements visible in the forthcoming sprint

    Last paragraph of section "Sprint Retrospective" says: "By the end of the Sprint Retrospective, the Scrum Team should have identified improvements that it will implement in the next Sprint."

    Change to: "By the end of the Sprint Retrospective, the Scrum Team should have identified improvements that it will implement in the next Sprint. Improvements should be added to the Sprint Backlog"

    And

    the first paragraph of section “Product Backlog” says: “The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.

    Change to: “The…

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Improve the 3 suggested questions for the Daily Scrum

    I will just start by saying that I don't like the 3 questions being present on the Scrum Guide.
    That being said, as a PST, I've been focusing on how to move people away from the status report mindset since they are so attached to the questions.
    Here is my take:

    Currently the questions are:
    What did I do yesterday that helped the Development Team meet the Sprint Goal?
    What will I do today to help the Development Team meet the Sprint Goal?
    Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Include an easy signup for people to get notifications when the Scrum Guide changes

    I had someone in a Scrum class ask me if there was a way for her to get notifications of when the Scrum Guide changes. I thought it was an interesting idea for consideration.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Move "Each increment is additive" from "Definition of Done" to "Increment"

    The section "Definition of Done" includes the following paragraph:

    "Each Increment is additive to all prior Increments and thoroughly tested, ensuring that all Increments work together."

    Looking at the text preceding and following it, this paragraph looks a bit out of place. Also, unlike the other bits related to the Increment in this section, it does not refer to "Done" at all.

    I propose moving it to the "Increment" section because it is part of the definition of what an Increment is.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add Learning as a Scrum value

    The lifeblood of Scrum are the Scrum values and they are critical to the success of Scrum. The lacking value is is that of Learning. As a value one can say

    Learning Scrum, agile and other practices
    Learning to work as self-organising team
    Learning other peoples views in conversations and events
    Learning ways to plan the sprint in Sprint Planning
    Learning better ways to plan then next 24 hours in Daily Scrums
    Learning to create better products increments during the sprint
    Learning from feedback during Sprint Review
    Learning new ways in Sprint Retrospect

    Learning enhances every other Scrum value, for…

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Keep it simple

    Keep it as simple as possible.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

General

Feedback and Knowledge Base