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. 1 vote
    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 →
  2. Responsible or accountable for managing Product Backlog

    According to some definitions, de person who is responsible will do the actual work. In de section of 'The Product Owner' first it is stated that the Product Owner is responsible for managing the Product Backlog and after the bullets it is stated that the Development Team may do the above work but the Product Owner remains accountable. I would say that it had to be; 'The Product Owner is the sole person accountable for managing the Product Backlog.'

    1 vote
    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. Add Definition of Ready to Scrum guide

    Ready has been emphasized in the 2013 Scrum Guide update and we need to emphasize it further.

    1 vote
    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. Make Grooming an official Scrum Event

    Hi guys,

    We've been spending quite much time for pre-planning or Grooming. That's why I'm suggesting to make this event an official scrum event. I always set up a separate meetings for my teams called Groomings, and I noticed that my colleagues are doing the same essentially. Thanks in advance!

    1 vote
    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. Revise the character "informal" from the sprint review meeting.

    First the description then a suggestion below it.
    Description:
    In the Scrum guide v. Nov-2017. In Scrum Review section the text contains: "This is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration."

    I can't experience any practical effect of the word 'informa meeting'. As English is not my native language, I am not sure if 'informal meeting' has any effect on others. I also asked some coaches,trainers,other scrum masters about what is ment by it. I know the translation of the word, but does it affect our…

    1 vote
    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 →
  6. implementing scrum

    Implementing and practising scrum in an organisation that breathes and lives traditional methodologies (PRINCE etc) - this cannot be done with the ongoing blessing of the 'Management' - Managers, Directors etc.

    For a successful SCRUM implementation and practice, I suggest that scrum guide includes a dedicated chapter for this to clearly make a statement about the needed powers and influence to be bestowed upon the scrum master and product owner, how this can/should be done, when and how frequently this should be reinforced...

    1 vote
    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. A fourth Daily Scrum question

    One of my Scrum Master mentors, or some Scrum article from the distant past recommended this 4th Daily Scrum question (that I now always use):

    Did I discover any requirements (new or existing) that the Scrum Team should be made aware of?

    Sometimes a developer may realize when looking at a particular item in the Sprint Backlog that they could knock off another item in the Product Backlog that is not in the Sprint if they spent an incrementally small amount of additional time. There is a natural tendency to not want to mention it because of perceived (and real)…

    1 vote
    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 →
  8. Move "writing PBIs" from PO to Team

    The Scrum Guide lists as one of the responsibilities of the PO:
    "Clearly expressing Product Backlog items"

    And then adds:
    The Product Owner may do the above work, or have the Development Team do it. However, the Product Owner remains accountable.

    In my experience one of the biggest problems with the PO role is that POs tend to become backlog managers, mainly writing User Stories.

    Customer contact and prioritization/ordering of PBIs isn't done properly.

    In most cases it turned out to be a good idea to involve the team in creating User Stories or even delegate it to the team.…

    1 vote
    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. Add opportunity enabler verbiage to last question of Daily Standup

    Add this verbiage to the last question of the Daily Standup: "..., or see any opportunity enablers that if implemented can improve team performance to meet the Sprint Goal"

    1 vote
    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. 1 vote
    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. What vs How

    Should you add words describing a Separation of Concerns for team members? Should it state that a Product Owner should focus their concerns on "What" needs to be delivered while the Development Team should focus on "How?" Would this make it easier to understand roles?

    1 vote
    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. One improvement item per sprint

    In the new (2017) Scrum Guide revision history it says:
    "7. Added to the Sprint Backlog section:

    To ensure continuous improvement, it includes at least one high priority way in which the team works, identified in the previous Retrospective meeting."
    A sentence that is not clear enough (at least from my perspective).

    In the 2017 Scrum Guide itself it is described differently:
    "To ensure continuous improvement, it includes at least one high priority process improvement identified in the previous Retrospective meeting."
    This I can clearly understand.

    I would like to have this statement unified, what do you think?

    1 vote
    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. Please help me find the audio for "The Scrum Guide"/I had it before

    Please help me find the audio for "The Scrum Guide"/I had it before, and now I cannot locate the aduio.

    1 vote
    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 →
  14. Make explicit how many Events there are in Scrum. Is it 4, 5, (or 6 or even 7)?

    Please can we make it clearer how many Events there are in Scrum?

    Four formal events are listed: (page 5)
    - Sprint Planning
    - Daily Scrum
    - Sprint Review
    - Sprint Retrospective

    Then another event is defined (page 9)
    - The Sprint (although not as an inspect and adapt event)

    Then under the same Scrum Events heading (page 10) we meet:
    - Cancelling a Sprint (could it be meant to be seen as an Event?)

    Then I have read the argument in this area for one other:
    - Product Backlog refinement. Here PBIs are "reviewed and revised" (inspection and adaptation)

    1 vote
    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. Change scrum master task from enforcing task to supporting task

    Described in "Scrum Master Service to the Product Owner":

    The Scrum Master serves the Product Owner in several ways, including:
    * Finding techniques for effective Product Backlog management;
    * ...
    * ...

    Can be changed to:
    The Scrum Master serves the Product Owner in several ways, including:
    * Helping the product owner find techniques for effective Product Backlog management;
    * ...
    * ...

    This small change makes the task a supporting task.

    1 vote
    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. Fix apparent typo on page 8

    It says: "Sprints enable predictability by ensuring inspection and adaptation of progress toward a *Sprint Goal* at least every *calendar month*."

    inspection and adaptation toward a Sprint Goal happens every day during the Daily Scrum. I guess the intent was to reference a longer-term *goal* (e.g., release), not the Sprint Goal.

    1 vote
    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. What prequalufications can be added as must for a CSM? It’s a lack of this that has devalued what it could bring!

    If anyone can get it in 2 days it is cheap and allows quality to dilute.
    If it needs a pre qualification and rigor in auditing it then maybe you can save the demise

    1 vote
    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 →
  18. Since Scrum is a framework, why is the Stand-Up/Scrum event so specifically prescribed as a "Daily Scrum?"

    I understand daily is the overwhelming frequency and also a good practice for the overwhelming majority of scrum projects. Don't misunderstand - I'm a big believer in daily scrums.

    However, especially as Scrum is used for more and more non-IT projects of all types, couldn't the scrum frequency be more or less frequent that daily? It seems that the frequency might also be correlated to the sprint duration.

    I submit this suggestion more in the spirit of keeping Scrum at the level of a framework and not a methodology or set of rules than I do to try to change…

    1 vote
    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 →
  19. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. All the scrum starters might find it difficult to digest all the information. May be a small problem can be presented with examples

    All the scrum starters might find it difficult to digest all the information. May be a small problem can be presented with examples and templates. For e.g. after daily scrum calls how and where the daily standup notes are published. How they are tracked to closure. May be scrum experts can record a video of various events and compile them and present it. This will be very specific and after understanding the overall framework if anyone watches this then they can easily relate things. This will help people to quickly adopt and expertise scrum.

    1 vote
    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