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. add some recommendations for the daily scrum - using a timer fixed to a holder on the scrum board

    Fixing the timer on the scrumboard so that everybody in the team can see the time one is allowed to speak has different advantages:
    - the speaker can move cards free hand
    - listeners don't get nervous if they think somebody talks too long, they see and know if somebody has the right to speak
    - the speaker also can see the time and can speed up etc

    I think the aim of having the daily scrum timeboxed but still all people in the team could tell their status is easier to reach if you use such a timer and…

    3 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. Small clarification regarding to "Product Backlog"

    In the "The Scrum Team" chapter, in the "The Product Owner" sub-chapter we can read: "The Product Owner is the sole person responsible for managing the Product Backlog <...>"

    But the definition of the "Product Backlog" comes much later.

    I would suggest to add some note in brackets like: "(see the "Scrum Artifacts" chapter)"

    3 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 →
  3. The PO can do the above work or have the Team do it... Seems an excuse for the PO to do nothing, even if he/she remains accountable.

    The PO can ask the Team to help him/her to do the above things. How can you manage your backlog if you're allowed no not even touch it?

    3 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 →
  4. Re-estimate incomplete Sprint goals... in Sprint Review

    The Scrum guide talks about the cancellation of a Sprint. In that context it asks to "All incomplete Product Backlog Items are re-estimated and put back on the Product Backlog."

    Would this not be true for items not completed in a Sprint as well? So I suggest that this be added to the Sprint Review as well so that the Product Backlog is accurate at the end of the Sprint (since in most cases refinement should be already completed).

    Optionally, this can be added in Sprint Planning as a step for items not completed in a previous Sprint (though this…

    3 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 →
  5. Daily Scrum

    In the Nov 2017 edition under Daily Scrum chapter Page:12, it is mentioned: Daily Scrum is held everyday and the team plans activity for next 24 HRS. Was the author referring to 8 working HRS when he said 24 HRS? Can any one throw some light on this, if I am missing something.
    If not, since Agile is very critical to time the Author would have had some idea in specifying 24 HRS

    3 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 →
  6. Tracking business value

    Scrum master role should be ensuring the Product Owner knows how to arrange the Product Backlog to maximize value as well as track planned vs actual business value delivered to business.

    3 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 →
  7. 3 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. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Empathy should be one of the values of the scrum beyond those already existing

    Empathy is an important value to build high performance teams once individuals aren't machines

    3 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. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  19. Change "Backlog" To "Options"

    Definition of "Backlog" is:

    an accumulation of uncompleted work or matters needing to be dealt with

    Backlog implies work is uncompleted. Whereas we should encourage the idea and mindset that it is an "option".

    Product Backlog changed to Product Options:

    Options of feature or capability to be added to product which are to be tested in market.

    Sprint Backlog changed to Sprint Options:

    Options that teams will try to work on in this sprint.

    Improvements Backlog to Improvement Options:

    Improvements options identified during retrospectives which can be experimented by the team during the coming sprint.

    3 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 →
  20. 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
    (thinking…)
    Sign in with: facebook google
    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