General
User Voice
User Voice is read-only while new Scrum Guide is under development
-
2 votes
-
2 votes
-
Clarify why the wording "no exceptions to this rule" is not in the Revision history of latest guide
Can anyone clarify why the sentence "there are no exceptions to this rule" has been removed under the section of the Development Team where it states that Scrum recognizes no sub-teams or titles. This is not there under the revision history as well.
1 vote -
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 -
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
1 vote -
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 RetrospectiveThen 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 -
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 -
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.
1 vote -
Correct user guide?
In the guide, under "Scrum events" it says "Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process."
I believe it should say "whenever the purpose of the sprint is achieved". Should this be corrected?1 vote -
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
1 vote -
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 -
Short version of Scrum Guide. 5 pages, not 17. It can be printed on every wall, even memorized.
Current version of Scrum Guide is perfect. But we can additionaly create short version. It can fit in 5 pages I bielive. Then it can be printed on wall of every scrum room (we can even send a nice printed copy for free) in the world. And 2nd benefit - it can be memorized by every Scrum master.
1 vote -
Can you please have a separate section for Scrum Master role and responsibility? Other than facilitating what are other responsibilities.
Is Scrum master just facilitating and coaching. Just like project manager has bigger role in PMP methodology. Can you clarify Scrum master role. I don't see much value given in scrum world.
1 vote -
List the techniques are used in Scrum by the scrum team (for eg techniques used in arranging the product back log)
If this includes the tools and techniques used by the scrum master and product owner will be helpful.
1 vote -
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…
1 vote -
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…
1 vote -
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?1 vote -
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.
1 vote -
elaborate on risks of applying a "Ready" state
applying the "Ready" state brings a strong risk of entering a Contract Game between Dev Team and stakeholders.
a "Definition of Ready" accelerates the risk.
some sort of "footnote" might help people to understand this and avoid entering into the trap.1 vote -
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.
1 vote