The Daily Scrum meeting is a short,
time-boxed meeting (generally 15 minutes) for the team members to communicate
their work statuses and their plans for the next 24 hours to the rest of the
team. This is done by inspecting the work completed since the last Daily
Stand-up Meeting and forecasting the work that could be done before the next
one.
One by one, each member of the team reports
three (and only three) things to the other members of the team:
1. What did I
complete yesterday?
2. What will I
complete today?
3. Am I facing any impediments?
The Scrum Master helps team members resolve
issues or impediments. The Scrum Master is only a facilitator. The Scrum Master
does not run the meeting. The Daily Stand-up Meeting is a forum for information
exchange only. Any discussion or issue resolution, if required, takes place
after the meeting.
Scrum Ceremony: Sprint
Review Meeting
·
At the end of the Sprint, a Sprint Review
Meeting is held to review the work completed during the Sprint.
·
The purpose of the Sprint review
is for the team to present the Product Owner with the end-deliverable of the
Sprint.
·
This is done to demonstrate and
validate that the deliverable is done (according to the defined acceptance
criteria).
·
It also helps the team get
feedback from stakeholders.
·
The outcome of the Sprint review
is either the acceptance or rejection of done backlog items by the Product
Owner.
·
Items not accepted remain in the
Product Backlog.
·
It is the responsibility of the
Scrum Master to ensure that the Product Owner does not change requirements or
acceptance criteria during the Sprint review and reject a done backlog item
because it does not meet the changed requirements. If the requirements have
changed, a Product Backlog item needs to be created to address the changed
requirements in a future Sprint.
·
Only the product
functionalities that adhere to the definition of done can be presented, and WIP
functionalities are included in a future Sprint. Team members present the work
completed during the Sprint, answer stakeholder questions, and note their
suggested changes.
No comments:
Post a Comment