Scrum Events
Sprint
Container of All prescribed Events
NO gaps between Sprints
Everything must happen within Sprint
All Events are time-boxed
All Events are intended to enable transparency and inspection
All meetings represent an excellent opportunity to get feedback.
and take action based on the feedback received, to achieve the desired results.
Sprint planning where the work to be performed
Sprint Review which is held at the end of the Sprint to review the increment.
Sprint Retrospective which is an opportunity to improve the process.
All events that are the formal opportunity to inspect and adapt.
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.
make the timebox shorter will easier to plan what is being build and to get early feedback
No changes should be made that would endanger the Sprint Goal
While the Product Increment is created new things are learned
When necessary the scope of the Sprint may be clarified and renegotiated between Dev Team and PO
No Gap between Sprint.
Nothing happened between Sprint
Cancelling Sprint
When
Who
Only PO has authority to make decision to cancel a Sprint ❤
Product is no longer needed
Sprint Goal becomes obsolete
Some significant or sudden changes on the market.
Company change direction.
Stakeholder or Dev Team or Scrum Master can advise cancel Sprint.
What
Complete items will be reviewed.
Incomplete Items will be re-estimated and put back to Product Backlog
Sprint Planning Meeting
Who
How long
Time boxed: 8 hours for One month meeting
PO
Scrum Master
Dev Team
What to do?
Scrum Master ensure that the meeting takes place and that it is kept with in the time box.
Scrum Master Coach the rest of the Scrum team on the purpose and importance of this meeting.
The Stakeholder, The management or any other people external to the Scrum Team should NOT attend this meeting ‼
What
When
Scrum meeting is the first activity of this sprint
Start from end of previous sprint.
outcome
(Scrum Team) To understand WHAT to be delivered in the sprint(this is Sprint Goal).
How to make this happen by creating plan
PO 👤
PO's action in scrum planning meeting
PO present the objective that a sprint should achieve and negotiate with team
The result of negotiation between the Product Owner and the Dev team is Sprint Goal
PO present the backlog items that, if complated in the sprint, would help to meet the objective
Negotiate with Scurm Team
The Sprint Goal should be specific and measurable.
Sprint Goal gives Dev Team some flexibility regarding the functionality implemented
Sprint Goal guides the Dev Team on WHY it is building increment and promotes effectives teamwork. (SMART 中的 R，为什么，这样形成一种自下而上的动力）
Daily Scrum Meeting
Intended (and only for) Dev Team
Timeboxed, should finish in 15 minutes.
It is crucial (关键）
This is a KEY, "inspection and adapt" meeting in Scrum.
Team use this meeting to plan the works in next 24 hours.
Help Dev Team Check progress
Meeting is totally up to the Dev Team, how the meeting is conducted. There is no rule for how the meeting should be conducted.
Finally, help team contemplating Sprint Backlog and reach the Sprint Goal.
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.
target
Dev team should improve communication
Identify impediments
Promote quick decision-makeing
Know-how transfer
Sprint Goal
Scrum master 👤
Make sure the Dev team has the meeting
keep it within Time-box
Scrum mast mot need to be present, but it may choose to do so
In any case, the Scrum Master will not lead a meeting or direct it in any way
Scrum make sure chicken will not disturb meeting
Some others chicken are allowed to join
This is a Internal meeting for Dev Team
Daily Scrum is not a reporting for progress toward PO or Stakeholders
Daily Scrum improve the information exchange within the team and reduce the need for additional meetings.
问题： 通常 Scrum Master 和 PO都不是专职的，是兼职的Dev Team 的一员，在实践中还是会出现 Scrum master or PO lead Scrum meeting and Dev Team report progress to Scrum Master and PO
Dev Team 👥
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 ❗
Sprint Goal
Latest Product Increment
Definition of Done
Projected capacity of team
Past Performance of Dev Team(caculated how many point can be finished in previous Sprint.
Guide team in known how many backlog items can be selected.
Input of Sprint Planning meeting
Product Backlog
PO 👤
First part of sprint planning meeting, SET Sprint Goal (Define What to implement)
Output
Second part of Sprint Planning meeting:How the functionality will be build into a Production Increment
output
Sprint backlog
The PLAN for delivering the Increment
Others, outside of Scrum Team
Provide technical or domain advice
If Sprint backlog is too much or too little
Renigotiate with PO
PO 👤
click to edit
Dev Team
can not forecast everything at beginning
Dev team can add new items or redefine or refinement Sprint backlog at any time.
Once there are enough detail for team to start work immediately, then Dev Team can start.
Dev team need explain to PO and Scrum Master how they plan to accomplish a Sprint Goal and to create forecasted Increment.
PO and SMaster 👤
这个很象”有效的布置任务“ 中， “你自己复述一下目标是什么， 你如何完成这项工作”