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. How inclusive is a "Scrum Master"?

    8 March 2019, as we celebrate International Women's Day today, a thought comes to my mind with the term "Scrum Master" and how inclusive it is? Before I proceed, it makes sense to clarify that the term Master utilised by the Scrum Guide addresses a skilled practitioner of a particular art or activity.

    Sadly, our search engines and dictionaries don't do enough justice to this term. The most widely accepted meaning for the word Master as per our favourite search engines and dictionaries still call it "a man who has people working for him, especially servants or slaves"; other meanings…

    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 →
  2. Replace the word "framework" by "method" in the very first sentence of the guide.

    The word framework implies, that you first have to insatiate it, before you can use it. While this is formally true on an absolute scale, a big advantage of Scrum (and maybe even one of the major reasons for its success) is, that it is much more ready to use, when compared to, e.g., RUP or most other agile methods.

    Using the word "method" instead may also reduce the danger of Scrum being too much and too often adapted by unexperienced teams.

    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 →
  3. remove the notion of the PO accepting PBI's

    In the section on cancelling a sprint there is the text " If part of the work is potentially releasable, the Product Owner typically accepts it".
    This suggests that the PO is the person accepting the work done in the sprint.
    Doing so implicitly makes the PO the Boss of the team. If I can accept or reject your work, I am clearly in a power position towards you. This is not in line with the description of the team and the roles, where the PO is *part of* the Scrum Team.
    In the rest of the Scrum Guide there…

    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 →
  4. Scrum Master service to the Scrum Team

    Suggestion: add one more section "Scrum Master service to the Scrum Team"

    There are some items in "Scrum Master service to the Product Owner" that should belong in "Scrum Master service to the Scrum Team".

    - Helping the Scrum Team understand the need for clear and concise Product Backlog items;
    - Understanding and practicing agility; and,
    - Facilitating Scrum events as requested or needed.
    Ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possible;

    It does not make sense to put these items under "Scrum Master service to the Product Owner"…

    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 →
  5. Retrospectives should not be about individual people

    The Sprint Retrospective section says (July 2013):

    "Inspect how the last Sprint went with regards to people, relationships, process, and tools"

    From a humanistic / servant-leader / Deming perspective, I feel "people" is not a good word to use here, since it can easily be misunderstood or misconstrued. "Relationships" probably already covers the associated issues.

    But if we want to discuss people issues explicitly here (rather than out-of-band), then I would hesitantly suggest "behaviours" as a replacement. And I would put it last, not first.

    [Aside: When articulating such a Retrospective list, I usually also call out "policies" explicitly. Although,…

    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 →
  6. Consistently capitalize the words "Increment" and "Increments"

    The Increment is the only artifact that isn't consistently capitalized in the Scrum Guide (i.e., it appears sometimes as "Increment" and other times as "increment"). (Note that this is an issue for the plural form 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 →
  7. improve the daily scrum questions to support "best effort" in the sprit of continuous improvement

    Human behavior is established when you focus on "doing your best" every day according to Marshall Goldsmith "Triggers" being one of the sources.

    I suggest that the three questions be changed to exhibit that ask (just like we have moved commitment to forecast of Sprint goals

    What best effort did I do yesterday that helped the Development Team meet the Sprint Goal?
    What best effort 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 our best effort towards meeting the Sprint Goal?

    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 →
  8. Release Planning - Which can help us to predict the time taken to release the Minimum Viable Product

    It would be great if we can define some guidelines on how to do the release planning which helps us to predict the product delivery timelines.
    At the end of the day, product delivery matters the most.

    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. Add below brief video as an introduction

    We tend to read less and watch more movies instead.
    With that in mind I created this video which you could consider adding as an alternative or first introduction.
    https://m.youtube.com/watch?v=tr7ODpD8f8o

    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 →
  10. Concept of "The Sprint"

    Questionable in the ScrumGuide.

    I am not sure when Jeff & Ken decided "The Sprint" would include all meetings. Maybe when you decided sprints (iterations) should run back to back? Remember those discussions and my first sprints as a Scrum Master had gaps between sprints where we would work on the Product Backlog and get PBI's "Ready".

    However, when I hear your talks, read articles, read the ScrumGuide, there is plenty of hints that the Sprint is after sprint planning and before sprint review.

    Sprint planning: As the words say you plan the work for the sprint. How can you…

    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 →
  11. Retrospective Board

    Dedicate part of the team board to share areas of improvement to the process instantly to that board. This will minimize retrospective meeting time as it will be just a review to items already posted to that board

    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 →
  12. Change the term "Backlog Refinement" to "Sprint Lookahead"

    I realize that this term has just changed in the last version of the Scrum Guide, and is an improvement over the previous term used (grooming). However, with new teams, one of the frequently asked questions (and sometimes misinterpretation) is that the "Backlog Refinement" is an activity that the PO should do alone, in isolation. Changing the title to "Sprint Lookahead" communicates the idea that this is an activity for the entire Scrum Team, and that this is an opportunity to "Plan Ahead", for future Sprint(s).

    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. Put http://scrumguides.org/scrum-guide.html on GitHub to allow proper discussion

    I suggest moving the scrum guide to a format like Markdown, and to put that text and human friendly format into GitHub or Bitbucket. Then we can actually send proper pull requests, have those reviewed and discussed _with context_.
    In this User Voice forum, there is no context and it's hard to reason about the actual suggestion that people make.

    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. Product Backlogs are actually prioritised not ordered.

    The change of Product Backlog from prioritised to ordered is actually an error. Priority means "the fact or condition of being regarded or treated as more important than others."

    This is what we do with PBs. Whether because of risk, or value, or technology - We always work on the most important first.

    Ordered just means "has an order" - In that way we could use scrum and legitimately work on the meaningless nice to haves rather than the key aspects of the product.

    This also over empowers the PO role as it means they can decide in totality without…

    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 →
  15. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. add a section for well known and proven practices that support the application of Scrum

    The Scrum Guide is not very specific about what tools can be used to support your Scrum implementation. I guess there are a few well known and proven practices out there like story points, velocity, DoR, and many more.

    I think it would be great, if the guide would provide some hints on the proven practices to provide guidance for the individual Scrum implementation. Please state as well, that those practices have proven to be helpful for a lot of people, but that does not automatically mean they will work for you.

    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 →
  18. Change wording of increment definition

    "The Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints."

    I think this counts things from previous increments multiple times.

    If sprint 1 has value 5, the increment has value 5. Then if sprint 2 has value 4, then the increment has value 4+5=9. Then if sprint 3 has value 6, the increment has value 5+9+6=20. We've counted the value from sprint 1 twice.

    I think a better wording would be "The Increment is the sum of all the Product Backlog items completed during a…

    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 →
  19. Improve Flow of Sprint Planning

    In the PSM and PSPO there are great flow diagrams for the Sprint Planning, where Definition of Done and Retrospective Commitments are part of the input for the Sprint Planning. This is inconsistent with the way it is now described in the Scrum Guide.

    From Scrum Guide, section Sprint Planning, subsection Topic One: What can be done this Sprint?
    "The input to this meeting is the Product Backlog, the latest product Increment, projected capacity of the Development Team during the Sprint, and past performance of the Development Team."

    Suggestion: remove "the latest product Increment" (btw: in the rest of the…

    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. make Scrum Guide publicly annotatable

    from my point of view, a Web based version of the (English) Scrum Guide that is annotatable and allows for such discussions that are going on here would boost common understanding and contribute to eliminate misconceptions. scrum.org, Scrum Alliance and scruminc should sponsor this collectively.

    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