Back to Forum

Questions on Scrum Guide

Last post 11:55 pm January 11, 2017 by Sujith Gokuladas
2 replies
Hermes Tanhueco II
08:22 am January 8, 2017

Hi Scrum Masters,

I need some help to clarify some topics in the Scrum Guide

Sprint Planning
- Why the Sprint Goal is defined after DT finishes the forecast for PBI? Would it be better if the Sprint Goal is defined prior to selecting the PBI to be delivered in the Sprint?
- On page 9 of the guide, it states that "Work planned for the first days of the Sprint by the DT is decomposed by the end of this meeting, often to units of one day or less"? Does this mean that beyond the first days, the work becomes longer or harder in more than a day? Does it mean that easy PBI being worked on first before the harder ones?
- What is the difference between the Sprint Goal and objective set by PO during Topic One?

Daily Scrum
- Is it mandatory for SM to attend the Daily Scrum? Can he/she attends only if there are impediments that will be highlighted by DT?
- Does DT need to use yesterday Sprint Backlog as input to the meeting?
- Does the output of the meeting require updating the Sprint Backlog, to mark those completed items and log the identified impediments?

Sprint Review
- In this event, you will need both PB and SB isn't? The expected output will be a revised PB to indicate the probable PBI for the next sprint?
- Is there a rule when a Sprint Review must take place in relation to production release?

Sprint Retrospective
- What are the responsibilities of the PO in this event?
- Where do you "create a plan for improvements to be enacted during the next Sprint"? Is this broken down as PBI and added to the PB?

Scrum Artifacts
- At which event does the Product Backlog is created?
- In the Sprint Backlog, does DT need to indicate the estimate of each task for all selected PBIs?
- Can I say that the Increment is not a document but rather a product version that can be released to production?

Sanjay Saini
03:43 am January 10, 2017


Do you mind posting your questions in the following forum as a separate post per question?

https://www.scrum.org/Forums/aff/1

Sujith Gokuladas
11:55 pm January 11, 2017

On page 9 of the guide, it states that "Work planned for the first days of the Sprint by the DT is decomposed by the end of this meeting, often to units of one day or less"? Does this mean that beyond the first days, the work becomes longer or harder in more than a day? Does it mean that easy PBI being worked on first before the harder ones?

'Decomposed' is the key word there. You don't have to decompose all the items in the sprint backlog during the sprint planning. However, when you decompose the items, it is ideal to keep it to 'units of one day or less'



- What is the difference between the Sprint Goal and objective set by PO during Topic One?

You might not be able to achieve the objective set by the PO in a single sprint.

Daily Scrum
- Is it mandatory for SM to attend the Daily Scrum? Can he/she attends only if there are impediments that will be highlighted by DT? - No. Only the development team needs to attend the Daily Scrum. However, it is the Scrum Master's responsibility to make sure that the development team knows how to do the Daily Scrum and keep it under 15 minute. As long as there is proper communication between the development team and the Scrum Master, it is not mandatory for the Scrum Master to attend the Daily Scrum. Now that being said, personally, I would encourage the Scrum Master to attend the Daily Scrum
- Does DT need to use yesterday Sprint Backlog as input to the meeting? - Development teams do Daily Scrums at different times (especially if the development team is across different time zones). 'Yesterday' is defined by the last time you had the daily scrum.

- Does the output of the meeting require updating the Sprint Backlog, to mark those completed items and log the identified impediments? - This should be done throughout the Sprint. No need to wait till the daily scrum. Daily Scrum is a place to communicate the progress and impediments.

Sprint Review
- In this event, you will need both PB and SB isn't? The expected output will be a revised PB to indicate the probable PBI for the next sprint?
- Is there a rule when a Sprint Review must take place in relation to production release? - No. A Sprint Review is held at the end of the Sprint. A product release is done whenever the Product Owner decides to do it.

Sprint Retrospective
- What are the responsibilities of the PO in this event? - participate & learn from experience
- Where do you "create a plan for improvements to be enacted during the next Sprint"? Is this broken down as PBI and added to the PB?

Scrum Artifacts
- At which event does the Product Backlog is created? - 'Product Backlog is a living artifact'. It is not created during a specific event
- In the Sprint Backlog, does DT need to indicate the estimate of each task for all selected PBIs? - It is not a rule for Scrum.
- Can I say that the Increment is not a document but rather a product version that can be released to production? - An Increment is very clearly defined in the Scrum Guide - http://scrumguides.org/scrum-guide.html#artifacts-increment

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.