1. "Formal opportunity to inspect and adapt".
As per scrum guide “Scrum prescribes four formal events for inspection and adaptation, as described in the Scrum Events section of this document”
• Sprint Planning
• Daily Scrum
• Sprint Review
• Sprint Retrospective
Scrum Guide also states: “Although improvements may be implemented at any time, the Sprint Retrospective provides a formal opportunity to focus on inspection and adaptation.”
Why scrum guide again says “Sprint Retrospective provides a formal opportunity to focus on inspection and adaptation.” ? The same should hold true for other 3 events.
2. Can the development team composition can change during a Sprint?
As per Scrum Guide: During Sprint
• No changes are made that would endanger the Sprint Goal;
• Quality goals do not decrease; and,
• Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.
Hence it’s allowed although it will affect the productivity or it will come under "endanger the Sprint Goal" category? I am not sure here.
3. “The Product Owner may be present during the second part of the Sprint Planning Meeting to clarify the selected Product Backlog items and to help make trade-offs”
I came across above line while taking some online assessments.
As per Scrum Guide: Scrum Guide: By the end of the Sprint Planning, the Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment.
So my understanding is the PO should be present throughout the Sprint planning. Please correct me.
4. “How the work is planned at the sprint Review?”
My understanding from the scrum guide is: Enough work is planned for the entire Sprint by PO and DT. But DT decomposes the planned Sprint work only for first day or less.
Work is planned by both DT and PO or DT only?
As per scrum guide “Scrum prescribes four formal events for inspection and adaptation, as described in the Scrum Events section of this document”
• Sprint Planning
• Daily Scrum
• Sprint Review
• Sprint Retrospective
Scrum Guide also states: “Although improvements may be implemented at any time, the Sprint Retrospective provides a formal opportunity to focus on inspection and adaptation.”
Why scrum guide again says “Sprint Retrospective provides a formal opportunity to focus on inspection and adaptation.” ? The same should hold true for other 3 events.
2. Can the development team composition can change during a Sprint?
As per Scrum Guide: During Sprint
• No changes are made that would endanger the Sprint Goal;
• Quality goals do not decrease; and,
• Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.
Hence it’s allowed although it will affect the productivity or it will come under "endanger the Sprint Goal" category? I am not sure here.
3. “The Product Owner may be present during the second part of the Sprint Planning Meeting to clarify the selected Product Backlog items and to help make trade-offs”
I came across above line while taking some online assessments.
As per Scrum Guide: Scrum Guide: By the end of the Sprint Planning, the Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment.
So my understanding is the PO should be present throughout the Sprint planning. Please correct me.
4. “How the work is planned at the sprint Review?”
My understanding from the scrum guide is: Enough work is planned for the entire Sprint by PO and DT. But DT decomposes the planned Sprint work only for first day or less.
Work is planned by both DT and PO or DT only?