Please enable JavaScript.
Coggle requires JavaScript to display documents.
Scrum Events, Daily Scrum Meeting, Cancelling Sprint, Dev Team, PO …
Scrum Events
Sprint
-
-
-
Sprint has TimeBox
In timebox, a potentially shippable Product Increment is created.
If Duration of sprint is too long, the complexity and the risk may increase.
-
-
-
-
-
-
Sprint Planning Meeting
Who
-
-
-
The Stakeholder, The management or any other people external to the Scrum Team should NOT attend this meeting :!!:
-
-
-
Dev Team :silhouettes:
Now , Dev Team know the Goal, then Dev Team decide what/how they can reach (maybe a part of Goal)
Which part they can reach, is decide by Dev Team, not PO :!:
-
Second part of Sprint Planning meeting:How the functionality will be build into a Production Increment
output
Sprint backlog
-
Once there are enough detail for team to start work immediately, then Dev Team can start.
-
-
-
-
-
-
-
Daily Scrum Meeting
-
-
-
-
The question used in our current Daily Scrum meeting is a "example" from Scrum Guideline. E.g. What I done, What I will do, what I help team ....
重要的, 需要改变的地方：
1）What DID I DO YESTERDAY to meet Sprint Goal.
2）What will do today to meet Sprint Goal.
3） Do I see any impediment block us to meet Sprint Goal.
-
-
Timeboxed, should finish in 15 minutes.
-
This is a KEY, "inspection and adapt" meeting in Scrum.
-
Meeting is totally up to the Dev Team, how the meeting is conducted. There is no rule for how the meeting should be conducted.
Daily Scrum improve the information exchange within the team and reduce the need for additional meetings.
-
Dev Team
Dev team need explain to PO and Scrum Master how they plan to accomplish a Sprint Goal and to create forecasted Increment.
-
-
-
-
-
-
-
-
PO :silhouette:
First part of sprint planning meeting, SET Sprint Goal (Define What to implement)
-
Others, outside of Scrum Team
-