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. Don't prescribe exactly when the sprint goal is set during sprint planning

    Last paragraph of section "Topic One: What can be done this Sprint?" says: "After the Development Team forecasts the Product Backlog items it will deliver in the Sprint, the Scrum Team crafts a Sprint Goal. "

    Change to: "During Sprint Planning, the Scrum Team also crafts a Sprint Goal."

    Rationale for the change: No need to prescribe that the goal should be set AFTER deciding which PBIs to deliver. In many cases it will make sense to set the goal first, and then decide which PBIs make sense to achieve that goal. And that's even implied at the beginning of…

    112 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Clarify what the primary function of the Product Owner role is to avoid unintended proxies

    Clarify what the primary function of the Product Owner role is to avoid unconscious proxies

    Clarify: "The Product Owner is responsible for maximizing the value of the product and the work of the Development Team."

    This sentence appears to skim over the primary function of the PO role in six words combined with a secondary, more tactical concern that mixes messages.

    Suggest: "The Product Owner is a business decision making role responsible for maximizing the value of the product being developed using Scrum. At a tactical level, the Product Owner may seek to maximise the value of the Development Team's…

    87 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Publish an epub and mobi (Kindle) version of the guide

    For ebook readers, pdf is not convenient, as it is a non-scaling format. Please make the Scrum Guide available for ebook readers (in my case the Kindle)

    77 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Like 'Commitment' changed to 'Forecast' can 'Estimate' change to 'Size'?

    First let me be clear, I'm not a fan of #NoEstimates. I see a lot of value in teams Estimating product backlog items. When size comes into play, they will find they do not all have the same perspective on the scope and complexity of the product backlog item.

    However often teams are not comfortable providing estimates because other parts of the organization are considering them as given planning.

    The word estimates has a historic meaning in waterfall projects, and is part of project management methods like Prince2 and PMI. Historically it is considered something you can and should get…

    32 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 →
  5. Elevate the status of agreements in Scrum

    Core Scrum introduced the idea that the Definition of Done is not an artifact, but an agreement among the stakeholders, which can change (become robuster) over the course of development. There are other agreements in Scrum, for example the selected product backlog is the result of sequencing by the PO and the Dev Teams forecast of what it can accomplish. Or if the team cannot meet its forecast, it should fail on scope (deliver less than forecast), rather than do overtime or prolong the sprint.

    Other agreements are not core to scrum, serve to improve the performance of the team,…

    29 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 →
  6. 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?

    27 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 →
    started  ·  Ken Schwaber responded

    When you find 10,000 other Scrum practitioners (should have passed PSM I) who agree with you, then we give you permission to use it in your version of Scrum.
    Call it “Unquestionably Scrum”

  7. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Clarify what "all" means wrt to making the PBL transparent to "all"

    Is this "all in the world"? "all" in the organization? "all" in the universe?

    Idea brought on by (likely) Shu level read of the guide, and I assume that the primary target audience of the SG is Shu.

    Here is the discussion:
    https://www.scrum.org/Forums/aft/1139#4899

    My guess is "all" was intended to be "Scrum Team and stakeholders"

    16 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. Mention the Sprint Goal in the Sprint Review

    The Sprint Goal is mentioned 26 times in the Scrum Guide, including in the descriptions of Sprint Planning and the Daily Scrum, yet is entirely absent from the Sprint Review.

    A good place to add it might be by changing the following statement

    FROM:

    The Product Owner explains what Product Backlog items have been “Done” and what has not been “Done”;

    TO:

    The Product Owner describes the Sprint Goal and explains what Product Backlog items have been “Done” and what has not been “Done”;

    14 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. 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.

    13 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 →
  11. Include the Sprint Goal in the Scrum Artifacts section

    The Sprint Goal adheres to the definition of artifact (work or value to provide transparency and opportunities for inspection and adaptation.) Promoting it to artifact would make the guide tidier (presenting everything as a role/artifact/event,) facilitate the understanding and make it more difficult to forget it.

    12 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 →
  12. describe how line management should support the Scrum implementation

    Mostly all Scrum implementations will fail, if management doesn't support them.
    So what is the role of management in Scrum?

    - Management is responsible to create the right (what's that again) environment so that people can self manage, to sponsor the Scrum team

    12 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 →
  13. Provide more open assesments as free of cost

    Please provide E- tutorials and open assessments as free of cost . Because people with lot of scum knowledge hungry , but not have enough money to learn can benefit

    12 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 →
  14. Change Scrum Master to Scrum Guide...or something...

    Wanted' Scrum Master to lead our Three Ring Circus, or, Is the term “Scrum Master” a Misnomer that needs to be updated?
    Edit article
    Published on May 9, 2017
    LikeWanted' Scrum Master to lead our Three Ring Circus, or, Is the term “Scrum Master” a Misnomer that needs to be updated?0Comment0ShareShare Wanted' Scrum Master to lead our Three Ring Circus, or, Is the term “Scrum Master” a Misnomer that needs to be updated?0
    Douglas Bock
    Douglas Bock
    Agile Business Analyst / Product Owner
    "The Show Must Go On"...must it, really? Let's save our servant leaders! If you visit http://www.indeed.com/ today…

    10 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 →
  15. Additions to Sprint Retrospectives... borrowed from the Nexus Guide

    Often retrospectives in Scrum teams are not deep enough and focused enough. One of the tools I use is elements of the Nexus guide to facilitate the scope of retrospectives even in one-team Scrum. I just the following be added to the Scrum Guide in the Sprint Retrospectives section (wordings completely borrowed from the Nexus Guide)

    Every Retrospective should address the following
    subjects:
    • Was any work left undone? Did the Sprint generate technical debt?
    • Were all artifacts, particularly code, frequently (as often as every day) successfully integrated?
    • Was the software successfully built, tested, and deployed often enough…

    9 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 →
  16. 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"?

    8 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 →
  17. Rewrite the phrase "various projective practices upon trending" to something more understandable

    This sentence is not understandable:
    "Various projective practices upon trending have been used to forecast progress, like burn- downs, burn-ups, or cumulative flows."

    Upon consulting the dictionary, "projective" is a psychology term meaning “relating to the unconscious transfer of one's own desires or emotions to another person.”

    And, "projective practices" seems to be an architecture term (as in buildings) having something to do with the theory of planning.

    Further, “...upon trending” is an odd construction that places a context in which other actions appear to be happening but I don’t understand what this means in this context. For example. “Upon…

    8 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 →
  18. Clarify relation between Product Backlog and Sprint Backlog

    "All incomplete Product Backlog Items are re-estimated and put back on the Product Backlog."
    How can you put a Product Backlog Item "back" on the Product Backlog? By definition it is already on the Product Backlog.
    My interpretation: They are put back from the Sprint Backlog to the Product Backlog. This would mean these sets are disjoint.
    Which seems unlogical, because per definition the product backlog consists of all things that "constitute the changes to be made to the product in future releases" which includes the Sprint Backlog.

    8 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 →
  19. 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…

    8 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 →
  20. Scrum process diagram

    SCRUM PROCESS DIAGRAM: There is a version of the scrum guide converted to a process diagram in http://www.processon.com . Access is free! Discover and enjoy!

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

General

Feedback and Knowledge Base